> > *g* - that stuff is dangerous; after i wrote this code, i asked Palm if > > they would allow us to create read-only windows (ie: not on heap), or, at > > least let us move stuff around after we have created them.. oh well :) > > I'm practically positive that if you're using the > high-density-capable version of the window manager, you can indeed > pass a read-only bitmap to WinCreateBitmapWindow.
possibly - but, if you want pre high-density-capable :) when i was doing so, it would give me a FATAL telling me that the window was read only (i think this was OS4), didn't try it on OS5. will be able to remove the tweaking if it runs on OS5+ (simple if-then) > Changing to do that, instead of tweaking the structs, would > significantly improve your chances of running on future OS releases. of course, known that - and, if needed, small update to fix. so far, we have been lucky that the bitmap/window structures have not changed too much to cause headaches.. migration to 3.0 was bad enough :) > Watch out, though, that you never try drawing into a read-only > bitmap: the blitter will crash since it doesn't undo the memory > protection. :) thats the fun stuff. --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
