userforgroups@[EMAIL PROTECTED]
wrote:
> I've modified what I can, to remove the second buffer completely. It's
> a little slower now, but I'll have to see how it fares on the slower
> devices.
Well, it's going to be slow on the slow devices, because they're slow.
The question is whether it'll be too slow, of course. :-)
> Now in my hi-res version I'm using under 256k dynamic heap memory. Do
> you think that is fine then?
That's probably OK. There have devices with less than 256K of dynamic
heap, but not any recent devices, and I don't think any devices that
have 320x320 screens have this little heap. (Except maybe some old
Sony devices that had hi-res before Palm devices did, but those use a
different API for hi-res than regular Palm devices, so I would ignore
those personally, and treat them as 160x160 devices.)
> (I know that my Treo 650 seems to have way more available than the
> Tungsten E. Many thanks goes out to Palm for keeping this stuff
> standard :( )
Well, there is a certain amount of leeway they need to increase memory
over time. The bottom line is that Palms have always had a relatively
small amount of memory available, and developers have always been
expected to just deal with it and develop a programming style that
can work in that environment. It makes development painful, but it
is nice for the end user in that it forces apps not to have too much
bloat, which means that the device can do more with less. On the
other hand, it does make certain things (like double-buffering the
display) really impractical and painful.
- Logan
|
