1. Win32Lib 2nd bug

Win32Lib developers take note:

  quoted from Win32Lib:

>>
if onEvent[ id ] > 0 then
        -- call routine
        call_proc( onEvent[ id ], {iMsg, wParam, lParam} )
<<

The problem:

Since onEvent doesnt pass the id from WndProc, there is no way
for the user to create his own message map.  This is important
with some controls.

Declaring a global atom such as:
  global atom myId

and then loading it as soon as windows calls WndProc:
  myId=find(hwnd,window_handle)

clears that problem up.  The user can then use getHandle(myId) to get
the actual hwnd if needed.

I'll have to update my copy in any case.

--Al

new topic     » topic index » view message » categorize

2. Re: Win32Lib 2nd bug

This is fixed in v0.52, and will be uploaded to sourceforge in a few
minutes.

----- Original Message -----
From: "Al Getz" <xaxo at AOL.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Wednesday, September 13, 2000 7:05 AM
Subject: Win32Lib 2nd bug


> Win32Lib developers take note:
>
>   quoted from Win32Lib:
>
> >>
> if onEvent[ id ] > 0 then
>         -- call routine
>         call_proc( onEvent[ id ], {iMsg, wParam, lParam} )
> <<
>
> The problem:
>
> Since onEvent doesnt pass the id from WndProc, there is no way
> for the user to create his own message map.  This is important
> with some controls.
>
> Declaring a global atom such as:
>   global atom myId
>
> and then loading it as soon as windows calls WndProc:
>   myId=find(hwnd,window_handle)
>
> clears that problem up.  The user can then use getHandle(myId) to get
> the actual hwnd if needed.
>
> I'll have to update my copy in any case.
>
> --Al

new topic     » goto parent     » topic index » view message » categorize

3. Re: Win32Lib 2nd bug

> -----Original Message-----
> From: Al Getz
> Sent: Tuesday, September 12, 2000 1:05 PM
> To: EUPHORIA at LISTSERV.MUOHIO.EDU
> Subject: Win32Lib 2nd bug
>
>
> Win32Lib developers take note:
>
>   quoted from Win32Lib:
>
> >>
> if onEvent[ id ] > 0 then
>         -- call routine
>         call_proc( onEvent[ id ], {iMsg, wParam, lParam} )
> <<
>
> The problem:
>
> Since onEvent doesnt pass the id from WndProc, there is no way
> for the user to create his own message map.  This is important
> with some controls.
>
> Declaring a global atom such as:
>   global atom myId
>

Actually, you don't need to do this.  Use the undocumented getSelf()
function, and you'll get your id.

Matt Lewis

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu