|
Have you looked here yet?
http://partners.adobe.com/asn/developer/acrosdk/docs.html
Cheers,
Tom Archer
Author, Inside C#
Please note that the opinions expressed in this correspondence do not necessarily reflect the views of the author.
|
|
|
|
|
You might want to check out CLIBPDF from www.fastio.com.
|
|
|
|
|
In my program I need to test if the Selected Item in a tree control is at the end of a root. I'm guessing that I can get the info out of an HTREEITEM but I dont konw how to get the info. How can I get it?
Thanks in advance.
-Raffi
|
|
|
|
|
Hi Raffi,
Do you mean testing if an item is at the end of a branch ? In that case, you
could simply test to see if it has any child items with GetChildItem(hItemSelected),
which will return NULL if no children exist.
Alwin
|
|
|
|
|
Thanks alot 
-Raffi
|
|
|
|
|
Dear all,
Anybody knows a fastest file read/write method?
It is because i am doing a program and need to read/write a same file many many times, using CFile to read/write is very very slow.
Any suggest method?
Andy
|
|
|
|
|
There is also FILE structure for doing that but I don't know if it is faster than CFile.
Mazy
"The path you tread is narrow and the drop is shear and very high,
The ravens all are watching from a vantage point near by,
Apprehension creeping like a choo-train uo your spine,
Will the tightrope reach the end;will the final cuplet rhyme?"Cymbaline-Pink Floyd
|
|
|
|
|
An alternative is to use memory-mapped files, for which
some examples can be found on the Microsoft knowledge base. There
also exists a sample called ProcessWalker.
The downside is that it only works on NT or higher (I believe).
Alwin
|
|
|
|
|
Memory mapped files work for all Win32 operating systems.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
why don't you try this in pure c?
e.g.:
FILE *fp1;
char word[100];
char c;
fp1 = fopen("yourfile.txt", "r");
do
{
c = fscanf(fp1, "%s", word);
DoSomethingWith(word);
}while (c != EOF);
fclose(fp1);
Bunburry
|
|
|
|
|
A memory mapped file will still be faster because you will be accessing the file directly in memory.
You will have a pointer that points directly to the buffer that contains the file.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
I believe the multi-media IO functions provide the fastest file read/write performance on windows. Check out the mmioOpen function and all of its associated functions.
In an app I developed a couple of years ago, my tests showed that mmio outperformed every other method. I don't have the stats for just how much, but it was enough to make a difference.
My 2 cents.
Matt Gullett
|
|
|
|
|
Please some body explain me why is this coming
warning LNK4089: all references to "OLEAUT32.dll" discarded by /OPT:REF
LINK : warning LNK4089: all references to "SHELL32.dll" discarded by /OPT:REF
LINK : warning LNK4089: all references to "comdlg32.dll" discarded by /OPT:REF
LINK : warning LNK4089: all references to "ole32.dll" discarded by /OPT:REF
Thank
Gaurika.;P  
Gaurika Wijeratne , www.gaurika.com
|
|
|
|
|
The linker discarded the dll:s, as it found them unneccisary (probably the functions were packaged into COMDATs). If you want to link them in regardless, use /OPT:NOREF instead - or use /VERBOSE to see what was removed.
/moliate
|
|
|
|
|
How can I use /OPT:NOREF instead - or use /VERBOSE
I mean were to put it.
Thanks
Gaurika..
Gaurika Wijerante
|
|
|
|
|
Project -> Settings -> [Settings for Win32 Release*] -> Link -> Add to project options (add /verbose here)
* I assume you are doing a release build here, as the default for a debug build is /OPT:NOREF
You should now get a lot of information from the linker what is done in each pass.
An introduction to some optimizations the linker does can be found at: http://www.iecc.com/linker/linker11.html
/moliate
|
|
|
|
|
Dear moliate
Thanks I will Try it.
Gaurika..
|
|
|
|
|
Why in the world would you want to link in DLLs that you aren't using. If you want to get rid of the errors, then remove those DLLs from the link list. Or add them to the exclude list.
Tim Smith
I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
|
|
|
|
|
Hi.
I am stuck in the design process of a small program I am working on. Here is the scenario.
-----
- user select an option in the menu
- main thread creates a dialog box w/ process bar
- dialog box's OnInitDialog() sends a message to main frame
- main frame redirects to view
- view creates a worker thread
- worker thread goes through a for loop // (i = 0, 1 < 10000; ++i);
- worker thread posts a message to main frame on every iteration
- main frame redirects message to view
- view calls a function in dialog box to update process bar
-----
Okay. The design above works fine. Here is one drawback. Even though the worker thread does all the processing (for loop), the main thread is *inaccessible* as it calls the function in the dialog box to update the process bar.
I would like to redesign that part of the program so that even as the worker thread is processing the for loop and as *some thread* updates the process bar, the user can still navigate the program.
Do I need to create a worker thread to update the progress bar? Do I need a UI thread? The reason I kept the dialog box as part of main thread is because according to Prosise, it is best to keep UI related objects in main thread.
Thanks,
Kuphryn
|
|
|
|
|
How long does it take your dialog box to update the progress bar? Is that a long complicated process? Is your dialog box modeless?
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
Okay. First, I will answer questions.
1) The interval of the progress bar varies from data to data. Consider, for example, the process of zipping data. Zipping varies from data to data.
2) The dialog box is modeless. The dialog box is a private member in view.
-----
I want to clarify the actual problem. I saw a response from a member that implied that my description was not easy to understand.
The design works fine.
- worker thread handles data processing
- main thread (view) sends messages to dialog box
- dialog box updates the progress bar
The problem is that I believe the process of updating the progress bar is *considered* as part of the main thread. I think the reason is because the dialog box itself is declared in view (main thread).
I need three *independent* processes.
1) data processing
2) dialog box/progress bar updating
3) main thread is idling thus keeps the program from "locking."
Problem: Program seems to "lock" even though the data processing is done in the worker thread.
Question: I believe the reason it seems to "lock" is because as main thread sends message to dialog box to update the progress bar and as the dialog box update the progress bar, the frame considers the entire process (message + updating) as being in the main thread. I need to know a way to make everything separate.
Kuphryn
|
|
|
|
|
I would change your update mechanism to be more passive. If you are sending a message to the main thread, then the main thread is calling the update function 10000 times, like you described in your worker thread, that would be a drain on the system.
Have you considered using a timer on the main thread, set to say 1/10th of a second. The timer handler would call the update function of the dialog, and the dialog could use a thread synchronized varaible that indicates the current iteration of your worker loop thread?
Otherwise if your dialog update function depends on processing the data for every iteration, maybe your worker thread could create a report or cache all of the data for the main thread, then the dialog would just have to update a few times a second.
Good Luck!
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
|
Okay.
I have consider several different design schemes. One of which is passing a pointer of a dialog box created in view into the worker thread. There, the worker thread can update the dialog box's progress bar. However, I do not think that will solve the problem of "locking." The reason is the dialog box belongs to view, thus it is still apart of view and the main thread. That leaves me with two alternatives opposites of one another.
Alternative #1
- create the dialog box first
- message view after InitDialog()
- view active a function inside of the dialog box
- function instantiate a worker thread that is *part of dialog box*
- worker thread will update the progress bar directly
Alternative #2 (opposite #1)
- create a worker thread
- create a dialog box w/ progress bar *inside of worker thread*
- update the progress bar directly
From the two alternatives, which one do you think is best? I want to make the design as "safe" as possible i.e, non-volatile.
Please mention any ideas you may have.
Thanks,
Kuphryn
|
|
|
|
|
I've tried to trap the WM_CTLCOLOREDIT and used SetBkMode(TRANSPARENT), but this only worked for static control, not edit control.
Now I wonder if there's any easy way I can achieve the desired result (that is, no text background) without using any text output function. Please help me!
Uzi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
