Astan Chee wrote: > I've used ScrollCanvas before and it was awfully slow. My attempt at > doing it manually (sticking scrollbars to a frame) was even slower.
That's one of the reasons I didn't do it in the first place! The problem with using scroll bars is that they ask the window to re-draw itself constantly as you scroll. I think things could be sped up a lot if you used a method similar to what is in place for re-sizing events -- set a up a timer, so that the re-draw only happens after a small delay -- that way if the user scrolls lot, they will only get the re-draw when they are done, rather than a whole bunch of re-draws. Ideally you'd re-blit hte image in the right location as you scrolled, so you'd see it move up and down, leaving a blank spot, then the blank spot would fill in when the scrolling stopped, much like how panning works now. > So its basically changing the BoundingBox size/limit whenever a > scrollbar event is triggered? No, the other way around -- when the Bounding Box changes, the scroll limits would have to change -- that only happens when objects are added to or removed from the canvas. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ FloatCanvas mailing list [email protected] http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas
