Thanks, lots of help in that one so I can't answer it well till I've tried enough, which will take time (got to go out to do stuff now).
One thing I did notice was BITMAP:GetSubBitmap() exists, so I'll try that first, as I'm so far not using any intervening wxImage stuff. As you say, it operates in memory so it ought to be fast enough. If this is valid simplification, I prefer to stay with it. If the grabbing and showing of sub-bitmaps will work fast enough not to interfere with realtime scrolling, I think it will answer my need. Carving into binary subdivisions for scaling and joining is also a nice idea, and if I were writing for a small screen I'd do it anyway, though I'd earlier decided to avoid multiple scales in favour of a small enlargement window shown on demand. But if such slicings can help solve my other problem of image render failures after a couple of program loads, I'll do it anyway. But I want to avoid complexity where possible. Actually your sub-image idea can probably be adapted for multi-scaling purely by changing grab size and scaling the subimage, so long as wxLua will render a screen right if the entire chart is loaded in memory somewhere to be grabbed from. Though I'd probably best introduce grabbing and scaling only for significant closeups if I did it this way. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
