Thanks Mark, I'll study the killActive method. I've already implemented a
queryCancel method.
However, this statement of yours:
>
> And leaving doesn't allow one to save the current state in a database,
> probably because of thread issues.
>
> doesn't make any sense to me. The leaving() method is the natural place to
> have your code:
>
> ::method leaving
> pos = self~propSheet~windowRect
> say 'PropSheet page leaving. Window postion / size:' pos
>
> which gives:
>
> C:\work.ooRexx\staffan\propSheetPos>test
> PropSheet page leaving. Window postion / size: a Rect (50, 50, 427, 506)
>
> There is no reason I can see why that won't work
>
>
Well, it works fine the way you have coded it but when I try to save the
size and location of the window in an SQL database using an active ooSQLite
connection things no longer seem to work that well. If I trace it the trace
stops the moment I call the method to initiate the save and the database is
never updated. I've so far been unable to track down what happens because
my code looses control. I've tried running leaving without UNGUARDED but
all in vain. Maybe killActive/queryCancel is the way forward in this case.
I'll see if I can write a small sample program that illustrates what
(doesn't) happen(s).
Staffan
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
