Re: getSelf( )
Matthew W Lewis
KAPCO
> -----Original Message-----
> From: Cuny, David@DSS
> > What are the consequences of that problem if it does occur?
>
> It's only an issue if you call getSelf() after a callback invokes
> sendMessage. For example:
>
> procedure onSomeEvent( ... )
> integer self
> self = getSelf()
> sendMessage( ... )
> end procedure
>
> won't cause any problems, because the correct value of self
> was retrieved
> before SubProc/WndProc replaced it. If you instead wrote:
>
> procedure onSomeEvent( ... )
> integer self
> sendMessage( ... )
> self = getSelf()
> end procedure
>
> then self will contain the wrong value, because it was called after
> sendMessage.
>
I don't think that's correct, because windows (and win32lib) will handle
that message before returning to onSomeEvent(). So the stack should be
popped by then, right?
Matt Lewis
|
Not Categorized, Please Help
|
|