|
Mark Salsbery wrote: If you must use PreTranslateMessage(), then return non-zero to discontinue any further processing of
the message. Return zero to let the message be dispatched/processed normally.
I agree but it has no effect on the second message getting processed in the message loop of the MessageBox right?
led mike
|
|
|
|
|
I believe so. I would expect the modal message loop of the first dialog to eat the message
that's still in the queue.
That's what happens in my sample code - it appears the messages get processed in revere order, but actually
the modal processing of the first dialog makes the second queued message get processed, popping up the second
message box first. Once that's dismissed, the first dialog continues processing.
I think that should have happened in the OP's code too...something was wrong somewhere else IMO.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
Mark Salsbery wrote: I think that should have happened in the OP's code too...something was wrong somewhere else IMO.
I don't think so, I just reproduced it in an SDI app. Returning 1 or 0 has no effect on the behavior, the MessageBox appears to process the message in either case which makes sense since my return does not happen until after the MessageBox is destroyed.
I think in your case you are not using PreTranslate and so MFC CommandTarget or something is getting hold of it then who knows what is happening.
led mike
|
|
|
|
|
Interesting... I'm also already in a modal loop in my main window - I wonder how different that makes things.
Are you using an app class PreTranslateMessage() override or main window class override?
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark Salsbery wrote: Are you using an app class PreTranslateMessage() override or main window class override?
My CFrameWnd derivation
led mike
|
|
|
|
|
hmm....
I can't figure out where that second message goes...
It never gets routed through PreTranslateMessage, but gets dispatched through the message map of the
destination window just fine.
Moral: PreTranslateMessage() is a bad place to do message boxes from LOL
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I would guess the answer is the code of the main MFC message loop 
led mike
|
|
|
|
|
hehe yeah I just can't find it. Thankfully I'm unwilling to try any further because it's never
going to be an issue that affects ME, and I'm selfish like that LOL
Cheers man! ![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif)
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark Salsbery wrote: Moral: PreTranslateMessage() is a bad place to do message boxes from
That's a given. I wonder if the issue has anything to do with the message box being a modeless dialog in disguise.
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
I couldn't get that far to find out. I was unable to step into the source code for
the innards of the AfxMessageBox on VS 2008 (the trail ended at a call to an imported library
function which wasn't debuggable), so I couldn't even see what "modal" loop it was using.
That's why I was unable to find where that second message gets eaten.
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark and Mike.
FYI check
Microsoft Systems Journal June 1996
There is some info on modal dialogs message behavior which may explain things.
PS I am still working on my solution to this dilema. Making some progress.
Vaclav
|
|
|
|
|
Hey guys,
I have an application where I need to keep the UI responsive while background tasks are running.
I currently have worker thread that does a PostMessage to a handler that does my GDI drawing, but the problem is that if too many things are happening the message pump gets held up and therefor my UI drawing is not smooth at times. If there was some way I could just do my GDI or GDI+ drawing directly from the worker thread I know that would solve my problems and my UI would be responsive.
Is there anyway I can do my drawing directly from a woker thread safely using either GDI, GDI+, or even DirectX? any way at all?
|
|
|
|
|
You can do your drawing into off screen buffers in the worker thread then signal the main thread to update the display and all it has to do is draw the buffer(s) making it much faster. But you haven't indicated what you are actually doing so I don't know if that is helpful.
led mike
|
|
|
|
|
Oh cool, so I can actually safely use GDI calls to draw on an offscreen device context from directly within the thread so long as I dont do anything with an actual windows control? Then just update the actual windows control from the main thread?
modified on Wednesday, February 27, 2008 11:41 AM
|
|
|
|
|
Greg Ellis wrote: so I can actually safely use GDI calls to draw on the device context from directly within the thread
Safely? Not without synchronization. You have to insure the user can't do anything to cause
GDI ops - like dragging a window across your windows, etc.
It is possible, but safely takes some work
If you use regular thread synchronization to control all thread access to GDI then it will work pretty well.
I've been doing it for a lot of years, including rendering video and graphics on windows of another process, and I've not
seen or heard of any problems yet.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I have the following declaration in my code;
struct DTC{<br />
TCHAR *Code;<br />
TCHAR *Description;<br />
TCHAR *Defined;<br />
int nDefined;<br />
int nIndex;<br />
};<br />
<br />
struct DTC DTCodes[0x4000];<br />
The declaratiom appears before the code using the struct, I am reading a file into the array, it seems that as my file size grows my debugger gives me the following error message.
Breakpoint Found in Code + Address 0x7c901230.
I have verified there are no breakpoint set, my debugger usually stops at the line that is marked as a breakpoit.
I am using Lcc-Win32.
I think my problem is memory allocation, so I need to know how properly allocate memory for an array, the allocation must allow for expansion.
Thank in advance for your help.
|
|
|
|
|
You're allocating statically the array hence it can't grow. You need to dynamically allocate memory, have a look at malloc and free documentation.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
Wow! that was fast, god I love this site.
The file I am reading contains 2632 records, I allocated 0x4000 in anticapation of future expansion. My debugger is acting weird, and my first inclination is I am overwritting code with data, although the program seems to work OK in the runtime. I will investigate using malloc.
Thanks
|
|
|
|
|
jonsey29847 wrote: so I need to know how properly allocate memory for an array, the allocation must allow for expansion.
I agree. Is this a school project? If so the text provided should cover both of those aspects.
led mike
|
|
|
|
|
Thanks for fast reply, I will try to use malloc. This is not a school project, it is a keep this old brain working project, I am learning C programming and Win32APIs in my off time.
Thanks
|
|
|
|
|
jonsey29847 wrote: I am learning C programming and Win32APIs in my off time.
How? I mean what learning materials are you using? Did you check out the Book Review Section and Tutorials here on CodeProject?
led mike
|
|
|
|
|
I have early experience with Turbo C, I have read a few books, I travel a lot so carrying reference books is almost out of the question, I really need a a good Win32 book (Peitzold?) electronically would be ideal. I have checked out the tutorials section, the confusion I seem to have here is allocating memory for a struct. I have found this site to be particularly valuable as I get quick replys and for the most part I can work things through once I have an idea what I need to do.
I am working on a application to communicate with the OBDII controllers in an automobile, I am on V3 (alpha?) if that tells you anything.
The first computer I programed was an IBM 1620 using Fortran II.
I loved assembly, but finally faced up to using C, I will tackle OOP (C++) next.
Tom
|
|
|
|
|
jonsey29847 wrote: I really need a a good Win32 book (Peitzold?)
I learned Windows 3.? from Petzold book. It certainly covered the fundamental topics. I have not read his Win32 book, when I started Win32 development I just used the SDK books.
jonsey29847 wrote: the confusion I seem to have here is allocating memory for a struct.
That's not really a specific topic. Depending on the definition of the struct the allocation issues can be quite different.
IMHO here is a short list of C/C++ issues that one needs a firm grasp of before continuing with the language.
* Heap vs Stack memory
* Memory Addressing / Pointers / Arrays
* Memory allocation and freeing
* Initialization of memory and ramifications of not initializing memory.
* Function execution, i.e., pushing the parameters onto the stack and then jumping and how they return
led mike
|
|
|
|
|
led mike wrote: That's not really a specific topic. Depending on the definition of the struct the allocation issues can be quite different.
Can you cite some examples, my struct is simple 3 pointers to TCHARs and 2 ints.
led mike wrote: * Heap vs Stack memory
* Memory Addressing / Pointers / Arrays
* Memory allocation and freeing
* Initialization of memory and ramifications of not initializing memory.
* Function execution, i.e., pushing the parameters onto the stack and then jumping and how they return
My score is about 3 for 5 here, I think I am getting a lesson on Heap/Stack and Allocation and freeing.
Tom
|
|
|
|
|
jonsey29847 wrote: my struct is simple 3 pointers to TCHARs
That is a perfect example of "not simple".
TCHAR * is an address in memory to a block of TCHAR where the length of the block is undefined in your structure, which Mark Salsbery has pointed out.
Therefore when you allocate the memory for the struct on the stack only the 4 byte address member is allocated, not the space you need to hold the string you want that to point to.
Even if you calculate the space required and allocate on the heap you still don't have the memory structure you think you do in the struct and you would have to use math to address the starting points in memory to all the space you allocated for those strings. That is not advisable or Best Practice by the way.
jonsey29847 wrote: My score is about 3 for 5 here
It's possible you may not have accurately assessed your situation.
led mike
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
