1. Re: Compilers for translation
> From: Derek Parnell
>
> The main problem with Visual C++ is that it's expensive
> whereas the other's
> are free.
For what it's worth, I'd love to see Eu for VC++, since I got an inexpensive
copy through school, but it's way too expensive for anyone other than
students and companies.
On a related issue, I've learned some more about compiled win32lib crashes
(at least with LCC--I haven't had a chance to try Borland). It turns out
that you can't create any controls in between creating the rebar and its
bands, or the program will crash. It runs fine when interpreted.
I think someone may have mentioned this already, but ChildWindowFromPoint()
(called from within createEx() )seems to always fail when win32lib is
compiled. I tested v053 and v054. It works OK under v053 as long as no
memory has been allocated but not freed, and as long as the trace window
hasn't come up (consoles used by the program to puts() etc don't seem to
make any difference). Derek, I couldn't find that any memory had been
allocated in v054. Since you're more familiar with your changes than I am,
can you tell me if you did anything like that?
Rob, I'm sure you haven't had any time to do anything to figure out why
ChildWindowFromPoint() is failing, but just to refresh, safe.e offers no
help in debugging this (I believe it allocates some memory on its own), and
will crash when Eu uses memory allocated by a DLL (ie, some Windows
messages). The only things that seem to cause the bug are allocating memory
(but not freeing it before ChildWindowFromPoint() is called) or calling up
the trace screen.
Matt Lewis
http://www.realftp.com/matthewlewis
