1. Old win32lib and win95 issue
This was an old issue that has come back to me again since converting to
win32lib 59.1. It is an Error Code 464 - couldn't link to C function
getwindowinfo when running a shrouded prog on win95.
There is no getwindowinfo command in my prog and I don't have the
problem with win32lib 57.9.
I know, I know. Win95 is ancient history but there are some dinosaurs
around and I'd also still like to know the cause.
Best
Rangi
2. Re: Old win32lib and win95 issue
GetWindowInfo is called internally by win32lib when calling the setIndex on a
ListBox control. It does this to find out if this is a single-line or multi-line
listbox, as Windows needs different commands to set the index for these.
----- Original Message -----
From: "Rangi" <totorangi at hotmail.com>
To: "EUforum" <EUforum at topica.com>
Subject: Old win32lib and win95 issue
>
>
> This was an old issue that has come back to me again since converting to
> win32lib 59.1. It is an Error Code 464 - couldn't link to C function
> getwindowinfo when running a shrouded prog on win95.
>
> There is no getwindowinfo command in my prog and I don't have the
> problem with win32lib 57.9.
>
> I know, I know. Win95 is ancient history but there are some dinosaurs
> around and I'd also still like to know the cause.
>
> Best
> Rangi
>
> --^----------------------------------------------------------------
> This email was sent to: ddparnell at bigpond.com
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
