Posted for Chris..
Jason,
I too experienced problems. They may be similar to yours. Could I get
you to post this email to the palm-dev-forum given that I'm having
difficulties doing that right now?
The WinEnterEvent problem was the one that initially prevented by apps
from launching correctly.
'hope this helps.
Kind regards,
Christopher
-------- Original Message --------
From: Christopher Hunt <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Organization: Class Action P/L
To: Palm Dev Forum <[EMAIL PROTECTED]>
Hi there,
I've bitten the bullet and decided to give 3.5 a run. I've also just
re-joined this forum so please forgive anything that has been asked
before. Things that I've noticed so far:
* WinEnterEvent does not appear to be queued as a consequence of
calling FrmSetActiveForm. Previous OSs called WinSetActiveWindow
which would cause the queuing of WinEnterEvent and WinExitEvent. Is
the apparent lack of WinEnterEvent via FrmSetActiveForm a glitch in
3.5?
* Black screen on launching an application. Is this going to be in
the final build of 3.5?
* Why the need for 'form must be full width' in forms with text
fields? If its something to do with enforcing guidelines then maybe
we should call the guidelines standards! ;-)
Other than the above, I do like the changes; particularly the build of
Rooms such that old palms 2 based devices are supported. Well done Palm.
Kind regards,
--
Christopher Hunt
Class Action PTA. Ltd.
Complete time zone management for the Palm(tm) connected organizer.
Check out http://www.classactionpl.com/
