Interesting, it is ONLY happening on the 300.
here are the launch codes we support:
case sysAppLaunchCmdCardLaunch:
case sysAppLaunchCmdNormalLaunch:
case sysAppLaunchCmdNotify:
{
case sysNotifyVolumeUnmountedEvent:
case sysNotifyVolumeMountedEvent:
}// end of sysAppLaunchCmdNotify
case sysAppLaunchCmdFind:
case sysAppLaunchCmdGoTo:
I also handle the sysNotifyDisplayChangeEvent notification.
Hope this gives you enough info,
Thanks for the help.
bill
"Steve Mann" <[EMAIL PROTECTED]> wrote in message
news:111833@palm-dev-forum...
>
> >the first error happens just by launching into our application AND
> >wireless mode
> >is on, otherwise if wireless mode is off, all works well. (the user can
> >perform all appliation functions with the exception of dialing a number).
> >
> >So I haven't been able to narrow down way this happens, and this happens
> >ONLY on the treo devices. All other phone applications for any version
work
> >fine.
>
> Sounds like it might be related to PhoneLib launch codes that only
> happen if wireless mode is on. Is it happening on all Treos or just
> some? The 180/270 and the same, but the 300 is different. They have
> related but different launch codes. What launch codes are you
> intercepting if any?
>
> Regards,
> Steve Mann
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
