MonkeyK
01-07-2004, 03:49 PM
On the Pimlico DateBk yahoo group
http://groups.yahoo.com/group/pimlicodatebk/message/40001
-------message body-----------
Just a note for those of you that are experiencing unusual delays when
launching DateBk5 on a Tungsten T3 or E.
I was able to reproduce this delay in the T3 simulator and sent off the
entire package to the PalmOne programmer who has found the problem and a fix
for it and so it should make it into the next Ram update that PalmOne
releases - hopefully we won't have to wait too long for it. It was just
missing a necessray optimization (routines were being called for each record
in the database instead of being called just once for the entire database).
The PalmOne programmer has been tremendously responsive to all the issues
we've been finding and I think we'll see a significant improvement when that
update appears.
Unfortunately, there is no simple workaround at Datebk5's end for this
delay - the only remote possibility is to use some internal OS functions in
ARM mode (it's not available in 68k), but at this point it's not even clear
that would work.
So for now, it looks like something to just live with until the next Ram
update for these devices.
Cheers!
CESD, Pimlico Software, Inc.
==========================================
http://groups.yahoo.com/group/pimlicodatebk/message/40001
-------message body-----------
Just a note for those of you that are experiencing unusual delays when
launching DateBk5 on a Tungsten T3 or E.
I was able to reproduce this delay in the T3 simulator and sent off the
entire package to the PalmOne programmer who has found the problem and a fix
for it and so it should make it into the next Ram update that PalmOne
releases - hopefully we won't have to wait too long for it. It was just
missing a necessray optimization (routines were being called for each record
in the database instead of being called just once for the entire database).
The PalmOne programmer has been tremendously responsive to all the issues
we've been finding and I think we'll see a significant improvement when that
update appears.
Unfortunately, there is no simple workaround at Datebk5's end for this
delay - the only remote possibility is to use some internal OS functions in
ARM mode (it's not available in 68k), but at this point it's not even clear
that would work.
So for now, it looks like something to just live with until the next Ram
update for these devices.
Cheers!
CESD, Pimlico Software, Inc.
==========================================