Paul
Mon Sep 22 12:28:52 CDT 2003
Yaroslav,
Many thanks, that has got me headed in the right direction.
Do you by any chance recall a similar document or discussion outlining the
best way to handle (and ignore) the receipt of a WM_CLOSE and/or
WM_HIBERNATE message in a Compact Framework VB.Net or C# application.
I've googled to no avail.
Regards
Paul K.
"Yaroslav Goncharov" <yaroslav@softspb.com> wrote in message
news:Oq0z1ESgDHA.988@TK2MSFTNGP10.phx.gbl...
> Hi
>
> An application can attempt to release as many resources as possible in
> response to the WM_HIBERNATE message. It should exist in response to the
> WM_CLOSE message.
>
> See "Responding to Low Memory States" article in the PPC 2002 SDK
> documentation for details.
>
> --
> Yaroslav Goncharov
> Microsoft MVP - Mobile Devices
> Smartphone Developer Network
> www.smartphonedn.com
>
>
> "Paul Kay" <p.kay@tesco.net> wrote in message
> news:eWM8dzRgDHA.2328@TK2MSFTNGP09.phx.gbl...
> > I'm guessing that when the PocketPC OS needs to close a running
> application
> > to free memory for a new application, that it sends a Close Message of
> some
> > sort to the application it wishes to close.
> >
> > Could someone point me in the right direction as to what message is sent
> (or
> > if I've got it wrong, what the actual mechanics of this process are) and
> > advise me as to how to capture this message (or whatever) in order to
> > prevent a particular application from being closed by the OS.
> >
> > If such a refusal to close were to be coded within an application, would
> the
> > OS then select a different application to close or would it continue
> trying
> > to close the first application it selected for closing?
> >
> > Regards
> >
> > Paul K.
> >
> >
>
>