1. RE: win32lib V57.5 - Derek
Jonas Temple wrote:
>
> 1. Noticed that the library does not have my implementation of
> DrawTextEx in the library. Any plans to add it?
Yes. It is on the TODO list. I've been focusing on bugs but I could
squeeze it in next weekend.
> 2. I also sent you a minor change you gave me for handling changes to a
> calendar control date selection for possible inclusion as well.
Ooops. I forgot about it. I'll did it out of my archive and have a look
at it. I guess it wouldn't be too hard to put in.
> 3. Does win32lib no longer use LPSTR_TEXTCALLBACK for the text parm when
>
> adding items to a list view? That seems to be the case to me (I checked
>
> it out today) but I thought I would doube check.
That's right. Win32lib no longer stores the ListView data internally. It
lets Windows do all that, which I think is the faster way to go.
> 4. I'm getting sporadic win32lib fatal error: Error code 497;getHandle:
> Object is destroyed. when my main window closes. Has anyone else
> pointed this one out? The app I'm getting this on is not easily
> distributable as it uses dlls from an IBM product called Client Access
> (it connects to an iSeries database) so it will be hard to provide an
> example unless you have access to an IBM iSeries (also known as AS/400)
> and the Client Access Express dlls.
I've worked with Client Access about 6 or 7 years ago when I was working
for Cargill. Congrats if you are getting Euphoria to interface with it
Anyhow, this message comes about when win32lib is trying to get the
handle of a control that has been destroyed already. This might happen
if you are explictly destroying some controls during an onClose or
onDestroy event handler.
Anyhow, try this idea:
In the routine called 'fDoClose' you should find some code near the end,
like:
-- Destroy it and end the program.
destroy(id)
--Was this successful?
if window_destroyed[id] = -1 then
mainWindow = 0
window_closed[id] = 1
end if
change this to :
mainWindow = 0
window_closed[id] = 1
and see if that helps. I've been a bit suspicious of why the library is
destroying controls when it is just about to close the application
anyway. The only reason I can think of why it might want to do this is
to invoke some Destroy handlers to clean up application defined things.
---------
Derek.
2. RE: win32lib V57.5 - Derek
> -----Original Message-----
> From: Jonas Temple [mailto:jktemple at yhti.net]
> 4. I'm getting sporadic win32lib fatal error: Error code
> 497;getHandle:
> Object is destroyed. when my main window closes. Has anyone else
> pointed this one out? The app I'm getting this on is not easily
> distributable as it uses dlls from an IBM product called
> Client Access
> (it connects to an iSeries database) so it will be hard to provide an
> example unless you have access to an IBM iSeries (also known
> as AS/400)
> and the Client Access Express dlls.
Are you using any TabControls? There seem to be some messages that they
can't handle when things shut down. There could be similar problems with
other controls as well. Maybe you could pare things down to just the
interface...
Matt Lewis
3. RE: win32lib V57.5 - Derek
Matt,
No, unfortunately not. The one thing I failed to mention is that I am
coding the inserts into the list view myself (not using addlvitem)
although I am creating the list view with win32lib. I'm doing this
because I want to tweak the LV_COLUMN structure based on the type of
data being displayed.
I'm seeing this problem on Win2000 Pro. I'll try to either narrow it
down or get a small example of the problem.
Jonas
Matthew Lewis wrote:
> Are you using any TabControls? There seem to be some messages that they
> can't handle when things shut down. There could be similar problems
> with
> other controls as well. Maybe you could pare things down to just the
> interface...
