1. RE: broken buttons
George,
I ran into this as well. If you're coming from a somewhat older version
of Win32Lib then the problem might be that somewhere else in your code
setHandler() was called, which turns off the old onXXX() event
methodology.
Now might be a good time to go through your code and migrate the onXXX
to setHandler().
HTH,
Jonas
George Walters wrote:
>
>
> I just upgraded to the latest win32 for come listView functions and most
> of
> my buttons are now broken. Here's some code snipits.. (I'm using EU 2.3
> if
> that might make a difference). The "exit" seems quite simple but it does
> not
> work any more..... Any Ideas on what changed?
>
> sequence leftButtonText,leftButtonProcess
>
> leftButtonText = {"E&XIT","&NEXT","&PREV","&FIND","&ADD"}
> leftButtonProcess = {"processExit","processNext","processPrev",
> "processFind","processAdd"}
> .
> .
> .
> ------------------------------------ Setup process
> control --------------------------
> for i = 1 to length(lbt) do
> onClick[lbt[i]] = routine_id(leftButtonProcess[i])
> end for
> for i = 1 to length(rbt) do
> onClick[rbt[i]] = routine_id(rightButtonProcess[i])
> end for
> .
> .
> ----------------------------------- Exit
> Button -------------------------------------
> procedure processExit()
> closeWindow(Main)
> end procedure
>
>
> thanks for a hint...
> george
>
>
2. RE: broken buttons
George,
Yep, you're right. I also remembered the following "fix" if you don't
want to go through converting to setHandler. Add this line of code
right before WinMain():
void = onXXX(True)
HTH,
Jonas
George Walters wrote:
>
>
> OHHH, you're right and this is a big impact on my programs..... I have
> routines which I branch to with buttons, but I also call them directly
> and
> now have no 3 arguments to pass since they don't need any input.....
>
> george
>
