Luc Le Blanc wrote:
Ton van Overbeek wrote:
On 2006-08-02, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
My app takes advantage of devices with a Dynamic Input Area to
automatically expand some display forms. So far, I had used the
following code to determine whether the device had a DIA (as found in
DIA docs):
error = FtrGet( pinCreator, pinFtrAPIVersion, &version );
if ( ( error == errNone ) && ( version != 0 ) )
// device has a DIA
but I see the Zire 22 Simulator passes the test, although this device
does not really have a DIA. What would be a more discriminating test?
Sorry for not giving you a direct answer.
But if your app is written properly it should not be a problem because
the resize notifications will never be sent.
My DIA aware apps run fine on the Z22 debug simulator without ever
getting
a resize notification.
I do not have access to a real Z22, so I cannot tell you if this also
happens on the real device. Heck, I do not even know if 68k debugging
via USB is possible on a Z22.
I don't have a Zire 22 either, and its mini-USB connector does not allow
for on-device debugging, but I don't think this is a Zire 22-specific
issue. I just realize this documented test is insufficient; the DIA
library may exist in the OS, but it's unuseable, so I'd like to know.
I suspect things work fine on the Zire 22, my app never gets any window
resize event, but I'd be happy to set the flag for sure, and then I
don't have to worry I do something that cannot work on that device.
Luc Le Blanc wrote:
Ton van Overbeek wrote:
On 2006-08-02, Luc Le Blanc <[EMAIL PROTECTED]> wrote:
My app takes advantage of devices with a Dynamic Input Area to
automatically expand some display forms. So far, I had used the
following code to determine whether the device had a DIA (as found in
DIA docs):
error = FtrGet( pinCreator, pinFtrAPIVersion, &version );
if ( ( error == errNone ) && ( version != 0 ) )
// device has a DIA
but I see the Zire 22 Simulator passes the test, although this device
does not really have a DIA. What would be a more discriminating test?
Sorry for not giving you a direct answer.
But if your app is written properly it should not be a problem because
the resize notifications will never be sent.
My DIA aware apps run fine on the Z22 debug simulator without ever
getting
a resize notification.
I do not have access to a real Z22, so I cannot tell you if this also
happens on the real device. Heck, I do not even know if 68k debugging
via USB is possible on a Z22.
I don't have a Zire 22 either, and its mini-USB connector does not allow
for on-device debugging, but I don't think this is a Zire 22-specific
issue. I just realize this documented test is insufficient; the DIA
library may exist in the OS, but it's unuseable, so I'd like to know.
I suspect things work fine on the Zire 22, my app never gets any window
resize event, but I'd be happy to set the flag for sure, and then I
don't have to worry I do something that cannot work on that device.
I just checked my code. When I enter the cave map form, I do:
if ( gDevice & DynamicInputArea )
{
gReOpenDIA = PINGetInputAreaState() == pinInputAreaClosed;
PINSetInputAreaState( pinInputAreaClosed );
}
else
gReOpenDIA = false;
but who knows if this does not crash on a DIA-less device that my app
thinks has DIA? Hence the interest of a discriminating detection...
--
Luc Le Blanc
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
