1. Win32Lib changes
A couple of notes about the next (unreleased) version of Win32Lib
[Opening and Closing Windows]
After talking to Einar, I've decide to make a number of changes to Win32Lib
routines that open and close windows.
I initially used the names onLoad/onUnload from VB. The problem is that
when a window is "closed", Win32Lib doesn't actually destroy (unload) it.
Instead, the window is hidden. Windows are not destroyed (unloaded) until
the main window is closed.
Plenty of room for confusion. As a result, I'm going to make the following
changes, which should better reflect the intent:
[Opening Windows]
loadWindow becomes openWindow
onLoad becomes onOpen
[Closing Windows]
unloadWindow becomes closeWindow
add new event: onClose
[Closing the Application]
onUnload becomes onDestroy
[Memory Leaks?]
Einar is roporting memory leaks with v0.15a, but I can't duplicate them on
my machine. If anyone else is encountering these types of problems, *please*
send me the code.
Thanks!
-- David Cuny
2. Re: Win32Lib changes
- Posted by Ralf Nieuwenhuijsen <nieuwen at XS4ALL.NL>
Dec 07, 1998
-
Last edited Dec 08, 1998
>[Memory Leaks?]
>
>Einar is roporting memory leaks with v0.15a, but I can't duplicate them on
>my machine. If anyone else is encountering these types of problems,
*please*
>send me the code.
I dont think many people fixed allocate_string and those routines.
They contain leaks, something that should be fixed for ver2.1 but Robert
already knows about it, Im sure. However, this could cause a memory leak as
well as the page fault.. however im not that sure the page fault would occur
in exw itself.. hmm, I sure hope it isnt a bug in exw itself..
Ralf
3. Re: Win32Lib changes
On Mon, 7 Dec 1998 23:17:25 +0100, Ralf Nieuwenhuijsen wrote:
>>[Memory Leaks?]
>I dont think many people fixed allocate_string and those routines.
>They contain leaks, something that should be fixed for ver2.1 but Robert
>already knows about it, Im sure. However, this could cause a memory leak as
>well as the page fault.. however im not that sure the page fault would occur
>in exw itself.. hmm, I sure hope it isnt a bug in exw itself..
There is a potential bug in Win32lib similar to the allocate_string bug:
Currently:
global function allocate_struct( integer size)
-- allocate space for a structure
-- and initialize to zero
atom at
at = allocate( size )
mem_set( at, 0, size )
return at
end function
Should(?) change to:
global function allocate_struct( integer size)
-- allocate space for a structure
-- and initialize to zero
atom at
at = allocate( size )
if at != 0 then
mem_set( at, 0, size )
return at
end if
return 0
end function
Greg Harris
HHS
