Win32Lib bug
- Posted by Michael Sabal <mjs at OSA.ATT.NE.JP> Nov 14, 1998
- 738 views
I don't know if this is what's causing the crash, but there is a problem = with the program ex06.exw shared earlier today. In the show_it() = procedure, list1 changes its state with the setText(..) procedure. This = triggers and onChange event which calls show_it() looping continuously. = Now, by my logic, this problem would cause a memory overflow or infinite = loop and would thus be easy to track down. However, there is a problem = with setText as reported in the documentation. The list is a sequence = (thus in C, a structure). Because structures are sent to Windows = manually, and not by Euphoria with a list box, there are a few = possibilities I can see (but I'm sure they've already been tried): 1. The new structure is not being set on a 4-byte boundary (Windows = law). 2. The new structure IS being set on a 4-byte boundary that's already = occupied. 3. The list structure is exceeding the size of a page (usually 64K) by = starting in the middle of it. 4. The new structure is longer than the allocated space for this = structure. With all the other structures used in Win32Lib, I think they are pretty = static (watch me put my foot in my mouth :)), but to define the contents = of a list box/combo box, we need a dynamic structure. Does this have = anything to do with it? Michael J. Sabal mjs at osa.att.ne.jp http://home.att.ne.jp/gold/mjs/index.html