Oleg Kobchenko wrote: > Regarding both proposals for stretching and formats, > I think it would complicate things both for J implementation > and for users, while introducing artificial limits. > > Stretch (in GDI terms) is a very primitive and outdated > operation. Nowadays, to say stretch is to > say too little, because there are many other factors like > smoothing or dithering method, what operation you want > with the replaced image (XOR, masked etc.), compositing > issues like transparency, etc. And it's better done in the code, > where you have full control. > > Formats is too specialized area, which is best handled > by a separate format-reading library. The same is in > other graphics systems like GDI+ and Java: you create > a bitmap (loading from a format possibly), then the > bitmat is always a rectangle of pixels, and only bitmap > is applied to the screen. > > To make it easier to use in the code a wrapper code > can be created with simple interface, like you suggest. > But it's important to maintain separation of > responsibilities between the gl2 engine and > the external stuff.
Thank you for information, I didn't realize bitblt family is outdated. I'm not an expert on graphic, I just want to display pictures in window easily. Isipicture is decommitted, and image addon not yet updated for J601, there is no simple way to display a bitmap picture file. My quick-and-dirt solution is to use owner-drawn button as an isipicture control. Hope this situation will improve. image addon has a limitation that file format cannot be converted in memory. It always requires writing to a file and then read that file again. This is inconvenient and has a problem of how to get a temporary file. -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
