OpenEuphoria

Win32Lib Bugs

• Posted by Ad Rienks <Ad_Rienks at COMPUSERVE.COM> Nov 13, 1998
• 507 views

To David, Daniel, Robert and all others interested in Win32 programming:

The 'invalid page default' that David is talking about, can also appear
using Visual Euphoria (version 0.02) by Daniel Berstein. If I define the
following:

cbJaar =3D NewControl(COMBOBOX, Form2)
SetAttribute(cbJaar, {
           {LEFT, 100},
                      {TOP, 140},
                      {WIDTH, 50},
                      {COMBOSTYLE, DROPDOWNLIST}})
--                      {MAXLENGTH, 5}})
The fault came up when the MAXLENGTH attribute was set. Running the progr=
am
right after that immediately crashes the program, so without adding
something to the combo or clicking it or something. When I comment out th=
e
MAXLENGTH line there's no problem.

My 2 eurocents opinion on this:
-- Possibly the fault is not in Win32Lib or VE, but in EXW.EXE.
-- If the fault is not in EXW.EXE, then I guess there can be (a) wrongly
defined message(s) in both libraries. Strangely, in the first case it is =
in
a listbox, and it only comes up on certain occasions, and in the second
case it is in a combo box.
-- Can there be any relation with the strange behavior of scroll controls=
?
After all, lists and combo's both are scrollable.
Is there anyone here that can shed a light on these strange X-file like
behavior?

BTW(17.5% here): Thanks go out to David Cuny for his excellent explanatio=
n
and example of onEvent[] programming.

Thanks
Ad Rienks

Original message: (partially)
>>Greetings.

I've been working on trying to fix some Win32Lib bugs, and I thought I'd
post them here, so others can take a shot at them. I'm stumped!

They are ordered by most to least critical.

Bug #1: Memory Errors in Lists

Win32Lib seems to barf when you click certain list items several times. T=
he
common key seems to be a length of 12, such as "Robert Craig" or "orange
juice". The error is an invalid page default from EXW.EXE.

What's especially perplexing about this bug is that you sometimes have to=

click the item several times to get it to fail. (Maybe it's triggering a
double-click behavior?)<<