Re: m100 clock -- internals
At 4:08 PM +0800 8/16/01, [EMAIL PROTECTED] wrote: > >Now, my problem is when the clock popup is dismissed, my screen is not >restore from memory and not receive frmUpdateEvent, and the clock popup >form remain there in non-active state. Anyone know why? There are problems with the clock popup. I don't know exactly what they are, but problems similar to what you describe have (as you noted) appeared in many different applications. I was sent notification that the problem was finally tracked down on 6/14/01. So hopefully the fix will appear in some future Palm OS version. -- -- Keith Rollin -- Palm OS Emulator engineer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: m100 clock -- internals
<[EMAIL PROTECTED]> wrote in message news:60013@palm-dev-forum... > > > This problem only occured when I performing the Gremlin Test. Is it > posisble because the screen cannot update itself so fast and on time? While I know it shouldn't be happening, I have seen screen update problems with POSE from time to time, even with the current 3.2 version. The actual screen in memory is correct, but what gets displayed by the emulator is a stale image. When you see this corruption, try minimizing the emulator then restoring it and see if the screen is now OK. If so, the emulated Palm is working correctly, but it just hasn't updated its visual image. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: m100 clock -- internals
I try to run Palm application: memo pad. It also have this problem. Regards Yen This problem only occured when I performing the Gremlin Test. Is it posisble because the screen cannot update itself so fast and on time? Regards Yen At 4:08 PM +0800 2001/08/16, [EMAIL PROTECTED] wrote: >Now, my problem is when the clock popup is dismissed, my screen is not >restore from memory and not receive frmUpdateEvent, and the clock popup >form remain there in non-active state. Anyone know why? Looking at the clock and clock popup sources, I'm reasonably certain the save behind flag *is* set for the clock popup dialog, and a frmUpdateEvent *is* sent to the underlying form when the clock popup is dismissed if there was insufficient memory available to store the bits behind the clock popup dialog. Yours is the first application I've heard of that has an update problem like this. Double-check that your form event handler is correctly set and handling update events. Are you doing anything "funny" with the FrmXXX APIs? Regards, Jim Schram Palm Incorporated Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: m100 clock -- internals
This problem only occured when I performing the Gremlin Test. Is it posisble because the screen cannot update itself so fast and on time? Regards Yen At 4:08 PM +0800 2001/08/16, [EMAIL PROTECTED] wrote: >Now, my problem is when the clock popup is dismissed, my screen is not >restore from memory and not receive frmUpdateEvent, and the clock popup >form remain there in non-active state. Anyone know why? Looking at the clock and clock popup sources, I'm reasonably certain the save behind flag *is* set for the clock popup dialog, and a frmUpdateEvent *is* sent to the underlying form when the clock popup is dismissed if there was insufficient memory available to store the bits behind the clock popup dialog. Yours is the first application I've heard of that has an update problem like this. Double-check that your form event handler is correctly set and handling update events. Are you doing anything "funny" with the FrmXXX APIs? Regards, Jim Schram Palm Incorporated Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: m100 clock -- internals
At 4:08 PM +0800 2001/08/16, [EMAIL PROTECTED] wrote: >Now, my problem is when the clock popup is dismissed, my screen is not >restore from memory and not receive frmUpdateEvent, and the clock popup >form remain there in non-active state. Anyone know why? Looking at the clock and clock popup sources, I'm reasonably certain the save behind flag *is* set for the clock popup dialog, and a frmUpdateEvent *is* sent to the underlying form when the clock popup is dismissed if there was insufficient memory available to store the bits behind the clock popup dialog. Yours is the first application I've heard of that has an update problem like this. Double-check that your form event handler is correctly set and handling update events. Are you doing anything "funny" with the FrmXXX APIs? Regards, Jim Schram Palm Incorporated Partner Engineering -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
Re: m100 clock -- internals
Now, my problem is when the clock popup is dismissed, my screen is not restore from memory and not receive frmUpdateEvent, and the clock popup form remain there in non-active state. Anyone know why? > Is system clock's form a popup form? As best I can tell, the clock application on the m100 is composed of two parts. The first part is a real Palm OS application called Clock -- actually, the database name for this is "cclkPalmClock", but the icon name comes from the attached overlay resource. This is the application that is activated when you tap "Clock" in the launcher. There is also a system extension named "clkp". The icon name associated with it says its the "Clock Popup". However, it doesn't have an associated form resource -- it looks like the resource it uses is form 13700 in the overlay file for System. This form does have the "Save Behind" bit set, so when the clock popup is dismissed, you should either have your screen restored from memory or a frmUpdateEvent sent to your form handler. This is assuming that Palm OS is using the usual mechanisms for the popup -- something that seems likely. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
m100 clock -- internals
> Is system clock's form a popup form? As best I can tell, the clock application on the m100 is composed of two parts. The first part is a real Palm OS application called Clock -- actually, the database name for this is "cclkPalmClock", but the icon name comes from the attached overlay resource. This is the application that is activated when you tap "Clock" in the launcher. There is also a system extension named "clkp". The icon name associated with it says its the "Clock Popup". However, it doesn't have an associated form resource -- it looks like the resource it uses is form 13700 in the overlay file for System. This form does have the "Save Behind" bit set, so when the clock popup is dismissed, you should either have your screen restored from memory or a frmUpdateEvent sent to your form handler. This is assuming that Palm OS is using the usual mechanisms for the popup -- something that seems likely. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
