1. Re: Win32Lib being restrictive

Maurizio wrote:

>>I agree with Daniel for the fact that win32lib takes too much control =
and
>>doesn't leave "freedom" to use other win32 features. For example, I am =
not
>>able to process WM_SIZE message for re-dimensioning a child control =
using
>>win32lib.

*heavy sigh*=20

It would have been so much nicer to hear this directly, instead of =
"through the grapevine", as it were.

If you have problems with Win32Lib (want features, hate it, etc.) - =
PLEASE send me a note! I don't know what you need without feedback. I =
can't guarantee that it will be added, but I'll try my best to satisfy =
requests.

The missing feature is a BUG. You *should* be able to use the onResize =
event at the control level. But because the controls are subclassed, =
they use a different set of event checks, and I'd forgotton to add the =
appropriate event checks at that level. I apologize for the =
inconvenience, and will make the appropriate corrections.=20

But I wish someone had pointed it out to me first, before complaining =
about it, or deciding against the library. Come on people - it's still =
pre-alpha! I'm just learning this as I code it, the same way you are. If =
you find something you really hate, odds are it's a stupid bug on my =
part, not an intentional feature.

My goal is *not* to lock you out of Win32 functionality. You can still =
add your own system calls to Win32.  As you've noted, the most glaring =
thing missing from Win32Lib is the ability to trap events that aren't =
built into the system.

To remedy this, I've planning on adding a "user defined" event trap that =
looked something like:

  onOther( event, parm1, parm2 )

This will trap events "other" than the default events I already have =
specific handlers for (onClick, onKeyPress, etc.). So you could have set =
up an event trap like this to handle the resizing of a child window:

-- start of example ---

procedure onOtherEvent_ChildControl( atom event, atom parm1, atom parm2 =
)

   -- process resize of child event
   if event =3D WM_SIZE then
      -- handle resizing of child
   end if

end procedure

onOtherEvent[ChildControl] =3D routine_id("onOtherEvent_ChildControl")

-- end of example ---

However, I didn't think it was that high a priority item. If I knew =
people were unhappy because it wasn't there, I'd have stuck it in ASAP =
(which unfortunately is not always immediately).

So, PLEASE - if you find a bug in Win32Win, or a feature you are unhappy =
with: go ahead and complain, but send ME something first!

Thanks.

-- David Cuny

new topic     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu