Hi,
after further investigation I found out that the "SampleCollapse"
example (version 2) has the same problem.
The only change made is that I added a navigation resource for the mainform.
NAVIGATION ID MainForm
INITIALSTATE 0x00000001
INITIALOBJECTID MainGuessButton
JUMPOBJECTID MainGuessButton
BOTTOMLEFTOBJECTID MainGuessButton
NAVIGATIONMAP
ROW MainGuessButton MainNoHandlerButton MainHandlerButton
END
Starting in portrait mode, rotating to landscape. This produces the (2)
events.
Then hitting rotation trigger and going from landscape to portrait produces:
(1)
sysPenDown
sysWinExit
sysWinEnter
frmObjectFocusTakeEvent
frmObjectFocusTakeEvent
frmObjectFocusTakeEvent (3x)
winDisplayChangedEvent
frmObjectFocusTakeEvent
sysNil
and FatalAlert on T5 device. (it works fine on simulator)
Inspecting events of a buildin application (filebrowser) on T5 simulator:
(2)
sysPenDown
sysWinExit
sysWinEnter
frmObjectFocusTakeEvent (only once!)
winDisplayChangedEvent
frmObjectFocusTakeEvent
sysNil
Furthermore if the "SampleCollapse" app is in portrait mode, closing DIA
does NOT erase the focused button(at the previous position) and produces a
corrupt
focus ring at the new position...
Manually hiding the focus ring and restoring after the move does not help,
but fixes the corrupt focus ring.
Intercepting frmObjectFocusTakeEvent and always returning true eliminates
the crash
(but is of course not a solution either.)
Any ideas?
> Hi,
> I have the following problem on a T5 device (on simulator it works
> fine).
> A non-modal form is put into object focus mode
>
> FrmSetNavState( frmP, kFrmNavStateFlagsObjectFocusMode ) ;
> In the navigation resource, the initial focus is set to OK button on this
> form.
> (the blue focus ring is drawn around the button)
>
> These steps produce a fatalAlert.
> Resize the display to pinInputAreaClosed and then rotate it.
> In the response to the displayChangeEvent the form is resized, the OK
button
> is moved and FrmDrawForm() is called to redraw the form.
> FatalAlert.
> It works fine if the moving of OK button is omitted.
>
> The crash seems to happen when system is handling frmObjectFocusTakeEvent.
>
> Regards,
> Miro Pomsar
>
>
> --
> 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/
