Daniel Morais a Ãcrit:

> Le 7 avr. 05, Ã 07:02, Luc Le Blanc a Ãcrit :

> > Now that I thought I had finally managed to handle DIA stuff
> > and> resize my display form when the Graffiti area is closed,
> > I get a very annoying side effect: when I open or close the T3
> > slider, my app gets a winDisplayChangedEvent, the a 0x505
> > keyDownEvent, then a frmCloseEvent... and closes! This occurs
> > on both the T3 Simulator or an actual T3 with the DIA
> > compatibility PRC's. Suggestions welcome.

> Exact description of the problem is important, to find some work
> around:

> If your app is running fullscreen (DIA not visible, status bar
> doesn't matter here) and have disabled the trigger allowing to
> resize the DIA, 

My case. I am displaying a cave map, so the Graffiti area is irrelevant; I 
disabled it to try to limit the number of times I get a winDisplayChangedEvent 
and rearrange the form (see below).


> then if the slider is closed your app receive a vchrNavReserved0
> (0x504 - vchrNavReserved1=0x505 is sent when the slider is
> opened) then a vchrLaunch, which is why the system send you an
> appStopEvent.

> So, possible solutions could be:
> - To not have a full screen app (DIA visible).
> - To not disable the trigger: if the vchrLaunch is sent, it is
> because the system think your app can't handle a change in the
> DIA size, due to the fact you disabled the trigger allowing to
> resize it (don't ask me why :).
> - To 'eat' the vchrLaunch event if a vchrNavReserved0 was
> received just before.

> This is not an official "problem description" or work around, it
> is not even guarantee to work (but it did for me): I'm just
> sharing what I found by spending time doing tests when I got the
> problem.

> If you find something else that you can share, please don't
> hesitate.


Thanks for this excellent answer Daniel. I think I'll just not disable the DIA. 
I wanted to limit the screen bouncing it produces, but I realize it's not 
sufficient to prevent the DIA from popping back while I perform lengthy 
computations and thus show a ProgressDialog to report computation steps. BTW, 
is there a trick to prevent the DIA from showing along with a ProgressDialog?


--
Luc Le Blanc
-- 
For information on using the Palm Developer Forums, or to unsubscribe, please 
see http://www.palmos.com/dev/support/forums/

Reply via email to