David, 1. Let me explain what I'm trying to accomplish by leaving it open. Probably you would advise me some more robust way. I want my application to be able to wake up (as resident application in DOS world) through the command bar menu. So, I want (even with my application quit) to show an icon in command bar and get notifications related. The problem is that command bar icons are drawn outside the scope of my application, so I have to keep some temporal database with my icon opened even if my application is not running, otherwise OS won't find bitmap resource with my icon. This approach works for all preCobalt devices.
2. Can't argue that except the fact the error code wasn't documented. -- Konstantin "David Fedor" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > >Bugs? > > > >1. > >> DmOpenDatabase(0,lid,dmModeReadOnly | dmModeLeaveOpen); > >dmModeLeaveOpen flag - does not work anymore for me. The base will be > >closed on application exit. > > > >2. > > WinGetBounds(WinGetDisplayWindow(),&display6); > > wh6 = WinSaveBits(&display6,&winerr); > >fails for window 320x480 with undocumented error code = 0xBEA0 > > > Neither one sounds like a bug to me, though I could be wrong. > > For #1, leaving databases open doesn't really make any sense given > that your process is completely torn down when you quit, and the next > app gets a clean new one, with none of your open databases and/or > leaked memory and/or whatever else. (What are you trying to > accomplish by leaving it open?) > > For #2: reading from the screen is no longer supported, and besides, > WinGetDisplayWindow() isn't actually the display window any more but > it just sort of works like it for compatibility with apps using the > old drawing model. Plus, saving its bits is unlikely to work right > due to the multi-threading nature of drawing: you'll most likely get > into problems when someone else has a window up over you. Said > differently, you can sometimes read from the window you get when you > call WinGetDisplayWindow(), but saving its bits is unlikely to do the > right thing so I'm not surprised it fails. > > However, returning an undocumented error code would be a bug. How > about reporting it at http://www.palmos.com/dev/support/bugs/ so it > gets officially logged and addressed? > > -David Fedor > PalmSource, Inc. > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
