It helps a lot. It's depressing, but it helps. Seems after all these years, we'd be beyond the 160x160 mode. Anyway, I have one more question based on something you said. "Sony doesn't have any equivalent of OS5's high-density bitmap families, so all bitmaps drawn for you by the system are assumed to be single-density and become pixel-doubled. If you want to draw a bitmap in high-resolution, you have to do it manually by calling HRWinDrawBitmap or HRWinCopyRectangle."
Are you saying that any image that I create in an external program like Paint Shop Pro or other image program will be assumed to be low resolution and have pixel doubling performed on it? I think you are but I want to be sure. If that is the case, I might as well just stay with what I have. Mike > I'm going to (try to) answer some of your questions out-of-order: > > <[EMAIL PROTECTED]> wrote... >> >> So, let me backtrack a bit. If I were to get the Sony SCKs for the >> Clie, can they be made to work with PRC-Tools? > > Sony still hasn't fixed their header files to work with the gcc > toolchain yet, so you'll need to make some changes to them first. John > Marshall has some Perl scripts to help you out: > > http://www.falch.net/Articles/?art=294 > >> Even though the Clie N70-V has a screen resolution of 320 x 480 any >> controls that I place (button, field, lists, etc) must be placed as >> though it is in a 160x160 screen? > > Basically you have two questions: > 1) how do you deal with Sony's high-resolution implementation > 2) how do you deal with Sony's virtual silkscreen > > Despite monikers like "HiRes+" for the second case, the two are > independent. > > First, let's suppose you're dealing with a Sony 320x320 device. In > such a case, yes, you lay out everything according to a 160x160 grid. > Unfortunately, this means you don't get high-resolution precision for > widget positions for dimensions (but do you really need that much > precision for a widget?). The system assumes everything's laid out to > a single- density coordinate system, in high-resolution mode, so a > 30x40 button will occupy 60x80 pixels on the screen. > > Now, on the NR70 devices, it's the same thing, except at run-time you > can reposition objects to occupy the additional screen area. (BTW, > you're still limited to a single-density coordinate system here, so > you'll be > repositioning objects relative to a 160x240 grid...) > >> how do I use a higher resolution >> image (like the 30x40) without having the OS try to expand it, >> thinking that it might have been drawn for a 160x160 device? > > Sony doesn't have any equivalent of OS5's high-density bitmap families, > so all bitmaps drawn for you by the system are assumed to be > single-density and become pixel-doubled. If you want to draw a bitmap > in high-resolution, you have to do it manually by calling > HRWinDrawBitmap or > HRWinCopyRectangle. > >> But now on the 320 x 320 device, I want to use a higher resolution >> image for the button. I was figuring that I'd specify it to be 30 x >> 40 with upper left at 200, 200 so that it came out in the same >> relative point on the screen but with a higher resoution image. > > Because the Sony systems won't draw bitmaps in high-resolution for you, > you're kind of out of luck if you want a high-resolution graphical > button. You either have to: > > A) using the old trick of overlapping a blank button and a bitmap > B) use a gadget > > The problem with A is that you don't get to control how the button > looks when it's selected. And the problem with B, of course, is that > you'd have to recreate button behavior. > > Hope some of this made some sense... > > > > > -- > For information on using the Palm Developer Forums, or to unsubscribe, > please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
