Hello,
apparently you followed the right path as my previous mail proves.
The concerned call looks like this:
UInt32 ret ;
Err err = SysAppLaunch (
0, pluginLocalId, // which plugin
0, // launchFlags
cmd, // plugin specific
cmdBPP, // plugin specific
&ret
) ;
What does it mean exactly "UI system state changes"? Actually I have no idea
how the plugin is programmed.
Regards,
Jan Slodicka
----- Original Message -----
From: "Ben Combee" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Tuesday, May 25, 2004 10:36 PM
Subject: Re: Window68K.c, Line:92, No shadow window found
> At 02:53 PM 5/25/2004, you wrote:
> >Hi Bob,
> >
> >the calls are ok - I used the short form. I wrote the code bellow. No
other
> >part of the program can see the window handle - hence it cannot be
> >unintentionally freed.
>
> I'm concerned about your use of SysAppLaunch to call a subprogram... how
is
> that working? It's possible that the UI system state changes across the
> sublaunch, and that invalidates the WinHandle shadow structure that holds
> those bits.
>
> I'd suggest using an offscreen window and doing your own WinCopyRectangle,
> rather than use WinSaveBits/WinRestoreBits -- those APIs have had problems
> in the past.
>
>
> -- Ben Combee, DTS technical lead, PalmSource, Inc.
> Read "Combee on Palm OS" at http://palmos.combee.net/
>
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
