My program contains about 95% of its data as read only data
structures. The first thing it does when it starts is to lock down
all its records (and hold them) so that it can set up static pointers
to all the data. These records are as sequential as the PRC itself,
since they are records of
My application is a frame based app (a game).
So it peeks for any messages in its queue with a time out.
Then if there are none, it goes and does a frame and comes back.
So it relies entirely on getting messages to know when it's been
interrupted.
As mentioned, in pre-OS 5, even when it got
I just wanted to add that in many cases (e.g. an alarm going off) I
look at my event trace and can't find a single event notifying my
application that anything has happened. In other cases I might get an
event (like AutoPowerDown), but don't know what to do with it -
because instead of the power
One last comment - we ARE passing onto the system any and all events
which we don't handle ourselves. And what we do seemed to work fine
in the older OSes.
- Jeff
--- In [EMAIL PROTECTED], Jeff Diamond
[EMAIL PROTECTED] wrote:
This may sound elementary, but I'm totally stumped.
My app is
Hi Danny,
The identical code has no unbalanced lock/unlocks when used on an
independent database. Only when it's passed its own database does it
get the underlock error. And in that case, I've tried changing the
number of locks and unlocks, and it makes no difference.
I've seen this problem
Solved the issue:
The problem was that you have to call
WinSetCoordinateSystem(kCoordinatesNative);
before every single graphics call, 'cause it's always being set back
to low resolution.
In this case, I forgot to call it again right before creating my
offscreen window. So when I told it to
Ken, thanks to the very helpful ideas. A key assumption I had been
making about my problem was incorrect. Turns out this was an OS-HEAP
MEMORY limitation problem, but NOT a 64K barrier problem nor a 16-bit
color problem (both red herrings for me).
I had been trying to allocate a 320 x 320 x 16
Ken, I am getting desperate! How did you get around the 64K problem?
If I use WinCreateOffscreenWindow with native format, I get a memory
error.
In fact, every approach I have tried to create a screen buffer 64K
has failed!
Several people spoke of an example code which shows how to do this,
, use some pages for your
buffers, and no allocation or heap usage needed.
--- In [EMAIL PROTECTED], jeffreyrdiamond
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Ken, I am getting desperate! How did you get around the 64K problem?
If I use WinCreateOffscreenWindow with native format, I get a memory
BTW, I just got the official word back from Sony.
It is a bug in the Clie Simulator.
They are currently looking at options to fix the problem.
- Jeff
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
Thank, guys. I guess it's time to update my tools again. :)
BTW, for the first time, I am not rushing to CW9, because of all the
posts that make it look unfinished. (Of course I'll need it once
I'm at the point of developing Armlets, but I'm still in the PACE
stage. :)
--- In [EMAIL
--- In [EMAIL PROTECTED], Ben Combee [EMAIL PROTECTED] wrote:
BTW, I wasn't proposing you move to 9.0 -- I was just saying you
need the
Palm OS 5 SDK. You can download this and install it in older
versions of
the tools, so you don't need to do a full migration just yet.
If I risk migrating
Thanks for the 16-bit color warning!
It turns out that I have been using Sony's Clie Simulator (since all
my high res work had been for Clies), and apparently this problem is
only with Sony. When I tried the genuine PalmOS emulator, I WAS able
to access the screen. So now I'm waiting and hoping
Thanks, Ben - This is good news. I only recently migrated to the OS4
SDK, so I'm a little gun shy about these things. But mayeb this will
make some of my OS 5 compatibility problems go away.
- Jeff
--- In [EMAIL PROTECTED], Ben Combee [EMAIL PROTECTED] wrote:
At 19:12 2003-1-14 +, you
Aaron, what was the loophole you found that allowed you to create
bitmaps 64K in size? From all the documentation, I would think that
both the Palm public APIs and constructor don't allow it.
- Jeff
--- In [EMAIL PROTECTED], Aaron Ardiri [EMAIL PROTECTED]
wrote:
Under PACE, when I get the
15 matches
Mail list logo
