(no subject)
--part1_28.2a3d1cb1.2a76697b_boundary
Hi Derek,
This has happened with other win32lib progs. Judiths IDE for one (although I
havn't noticed this prob with ide for a while). It only happens when 1st
tying to open the program i.e I have exw files associated with exw.exe so I
can double click my exw file to execute and then I get the error described.
I do not destroy and re-create anything.
Its not a big problem as its happens about 1 in every 10 or 15 executions. I
reported it mainly for your benefit in making WIN32LIB as bullet proof as
possible.
Thanks
Tony
Derek Wrote:
Hi Tony,
does this only happen with one specific program or can it happen with any
win32lib program?
This error indicates that a Windows handle (hWnd) which had been associated
with a given win32lib control, is now associated with a different control.
This is not supposed to happen. When win32lib creates a control, it gets
asks Windows for a hWnd for it then sets the GWL_USERDATA for that handle to
the id..
VOID = w32Func( xSetWindowLong, { hWnd, GWL_USERDATA, id } )
This stays in effect until the control is destroyed. Both the ID and the
hWnd can then be reused. But what this error seems to be saying is that two
controls are sharing the same hWnd - which I would have thought is a no-no.
Are you destroying and recreating controls in your program?
-----------
Derek.
--part1_28.2a3d1cb1.2a76697b_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=1 FAMILY="SANSSERIF" FACE="Arial"
LANG="0">Hi Derek,<BR>
This has happened with other win32lib progs. Judiths IDE for one (although I
havn't noticed this prob with ide for a while). It only happens when 1st tying to
open the program i.e I have exw files associated with exw.exe so I can double
click my exw file to execute and then I get the error described. <BR>
<BR>
I do not destroy and re-create anything.<BR>
<BR>
Its not a big problem as its happens about 1 in every 10 or 15 executions. I
reported it mainly for your benefit in making WIN32LIB as bullet proof as
possible.<BR>
<BR>
Thanks<BR>
Tony<BR>
<BR>
Derek Wrote:<BR>
Hi Tony,<BR>
does this only happen with one specific program or can it happen with any<BR>
win32lib program? <BR>
<BR>
This error indicates that a Windows handle (hWnd) which had been associated<BR>
with a given win32lib control, is now associated with a different control.<BR>
This is not supposed to happen. When win32lib creates a control, it gets<BR>
asks Windows for a hWnd for it then sets the GWL_USERDATA for that handle to<BR>
the id..<BR>
<BR>
VOID = w32Func( xSetWindowLong, { hWnd, GWL_USERDATA, id } )<BR>
<BR>
This stays in effect until the control is destroyed. Both the ID and the<BR>
hWnd can then be reused. But what this error seems to be saying is that two<BR>
controls are sharing the same hWnd - which I would have thought is a no-no.<BR>
<BR>
Are you destroying and recreating controls in your program? <BR>
<BR>
-----------<BR>
Derek.<BR>
<BR>
</FONT><FONT COLOR="#000000" style="BACKGROUND-COLOR: #ffffff" SIZE=3
FAMILY="SANSSERIF" FACE="Arial" LANG="0"> <BR>
<BR>
--part1_28.2a3d1cb1.2a76697b_boundary--
|
Not Categorized, Please Help
|
|
