- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any difference between the emt64 and x86 compilers (ver 10.0.027) in the calling structure for the DlgSet function for setting up a tab dialog. When I compile my program using the emt64 compiler the labels on the tabs in the tab dialog are missing, every thing else seems to work. I am using the emt64 include in lib directories. Thanks
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only difference I can think of is that the hwnd argument needs to be INTEGER(HANDLE) (or INTEGER(8).) If you have not declared your dialog handle to be INTEGER(HANDLE), so that it has the right size on both platforms, I could see problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not sure exactly what has happen but my tabs labels now appear. I have made no code changes, but compiled the routines that call the qwin libraries with the optimizer turned off and things seem to work again. These routines only use a very small amount to resources compared to the rest of the code so running them less then optimized is not going to be a big deal, although I would like to know how I can track down bugs like this in my code? Is there anyway to see what the optimizer has done to the code?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Perhaps there's a bug in your code that you can't spot. You can try the Static Verifier feature to see if it works for you. Read the on-disk documentation section on using Static Verifier for details. Note that it may warn about things that are not code errors.
You can also turn on diagnostics such as array bounds and uninitialized variable checking to see if anything turns up. In many cases, code that changes behavior when optimization is enabled is doing something wrong to begin with, but the error is hidden without the memory and instruction layout changes optimization provides.
You can also turn on diagnostics such as array bounds and uninitialized variable checking to see if anything turns up. In many cases, code that changes behavior when optimization is enabled is doing something wrong to begin with, but the error is hidden without the memory and instruction layout changes optimization provides.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the tip, I did not know about this little gem before, I will be using it very often in the future. I did compile the routines with this switch set and got quite a few errors, I'm not sure if all of these are actual errors yet, or the it is just being very picky, but it is something for me to look at. If I find anything interesting I will post the results. Thanks again Ray.
PS. This forum is a great resource and greatly appreciated.
PS. This forum is a great resource and greatly appreciated.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page