On Tue, 9 Apr 2002, Daniel Morais wrote: > I have done some tests with the latest version of Palm OS Simulator ( dr9 ) > and while it seems I had no trouble to initialize a 320x320 16 bpp screen, I > was unable to do something with it, as WinCreateOffScreenWindow failed... > > First call was fine, but the second one failed with a "sysErrNoFreeResource" > error ! > > So I compared the available memory on Palm OS Simulator and on a pose session > running a Clie device using the same resolution/depth and I was surprised to > find that on the Clie there was twice more available memory ( 900 Kb against > 450 Kb ), while the RAM size parameter was set to 16 Mb in the Palm OS > Simulator session against 8 Mb on the Clie one... > > Isn't Palm OS 5 supposed to handle high density screens, with all the memory > requirements implied for their use ? > > How are we supposed to make double buffering animations if we can't allocate > 2 screens ?
maybe we are not supposed to allocate two 320x320 16bpp windows? :P there are other ways to do this if there is no memory - but, the simulator doesn't like me calling those API's *g* > I hope these troubles are just due to Palm OS Simulator / ROMs beeing in > early stage and that we will not have them with the final Palm OS 5... i believe the heap space is around 512K for the simulator.. heck, it used to be 256 at one point :P i dont know if palm or the licensee's will provide sufficient memory for double buffering like this.. have you tried using the WinScreenLock API's? these will take advantage of any VRAM if any (i dont know if the simulator emulates this).. once again, this would be a great time for palm to implement the display controller features i have been nagging about for a while :) // az [EMAIL PROTECTED] http://www.ardiri.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
