Ok, going back to my original problem. I now have access to the screen and
all my bresenham stuff works fine (in both 2 and 4-bit grey, whooho!). The
next problem that I have is draw speed. Using only my bresenham routines
with double buffering on (and performing a full screen update every tick) I
get around 40 fps on my Palm. As soon as I start to draw a bunch of bitmaps
I get taken down to between 4 and 8 depending on how many I draw (between 4
and 67 bitmaps drawn per frame).
This seems alittle stiff to me. Is there any milage in writing my own
Blitter for this? Mine could forgo any work for converting from bitmap
format to screen format (all bitmaps could be stored in screen format). The
real problem that I can see here is while the screen size will produce byte
aligned rows in both 2-bit and 4-bit screen modes (and in 1-bit and 8-bit,
good choice of screen size by palm) my bitmaps will not align so well (being
of arbitary size).
Has anyone tried anything like this?
Did you have to restrict the size of your bitmaps to get a reasonable
framerate?
Are there any fast (free) blitting libs around?
Are has anyone traded double buffering for framerate to solve this problem?
Thanx in advance,
Idries
-----Original Message-----
From: Ben Combee [mailto:[EMAIL PROTECTED]]
Sent: 28 May 2002 03:38
To: Palm Developer Forum
Subject: RE: Access screen with Palm OS 4.0
In article <87306@palm-dev-forum>, [EMAIL PROTECTED] says...
>
> Sorry, this was incorrect, I commented out the troublesome line of code,
> went to lunch, *then* touched window.h and everything was fine (on Palm OS
> 3.5).... so in fact I did not fix it at all <sigh>
>
> However, I have now fixed it by not using the
"PalmOS_Headers_Strict_Debug"
> prefix file that was in my project by default. This seems to be like a
> Precompiled header file in VC++ but I can't figure out how to rebuild it
> with ALLOW_ACCESS_TO_INTERNALS_OF_WINDOWS defined....
>
> -----Original Message-----
> From: Idries Hamadi
> Sent: 27 May 2002 14:30
> To: Idries Hamadi; 'Palm Developer Forum'
> Subject: RE: Access screen with Palm OS 4.0
>
>
> I touched the windows.h file and everything got fixed...
>
> -----Original Message-----
> From: Idries Hamadi
> Sent: 27 May 2002 12:54
> To: 'Palm Developer Forum'
> Subject: RE: Access screen with Palm OS 4.0
>
>
> Ok, the Beamer.c app compiles without a problem and it can access this
> member without any special screwing around (it doesn't even #define
> ALLOW_ACCESS_TO_INTERNALS_OF_WINDOWS).
>
> I'm starting to think that this is a problem with my project setup. I've
> tried "Remove Object Code" from the Project menu (I think that this is the
> equivilent of "Clean" or "Rebuild all" in MS Visual C++), this doesn't
help.
> The only real difference that I can see between my project and Beamer is
> that I am using C++, could this be somthing to do with it?
As I mentioned in my other message, look at the project file
BuildHeaders.mcp, which should be linked to your wizard-created project.
It builds the four standard precompiled headers we ship on V8, and you
can modify it to create other variants with looser restrictions.
Also note: with the 4.0 SDK Update 1, there really isn't a difference
between the strict and non-strict headers -- both disallow structure
access.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Get help at http://palmoswerks.com/
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
