I'm trying to bring my software up to the point that it compiles cleanly using the OS5 SDK. I've been a bad boy and have been accessing 'protected' structures like video memory and the ListType structure.
I have one screen that has a bunch of controls that I show or hide depending on what the user wants to see. I probably should have done differently but this is the way it is... In any case, one of the controls is a list. I used to disable the list with: list->attr.usable = false; And then draw over it. Then I would enable it with: list->attr.usable = true; and use WinDrawList() But now that accessing the "usable" parameter is not really allowed, I need to find an alternitve. It seems that if I use LstDrawList() and ListEraseList(), the list never shows up. If I dont modify the usable parameter, then even if I draw over the list, tapping the screen will activate the items on the list. Any ideas? As far as drawing to video memory (I simply draw some greyscale pixels), I'd like to maintain 3.1 compatibility (lots of handspring users)...would the best thing to do is check for OS 4.0 and use WinDrawPixel if its there and draw directly to the memory if its not? Any suggestions would be great. TIA, Mike -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
