>On Wednesday, September 29, 2004, at 07:22 PM, tedd wrote: > >>But, what I don't understand is all the other stuff that goes with >>it, like NewGWorld(bla, bla...), and LockPixels(fn >>GetGWorldPixMap()), and UnLockPixels(), and CopyBits(bla, bla, >>bla...), and FlushWindowBuffer. For example, when, where and why do >>you use FlushWindowBuffer? Where in the hell did that come from? >> >>You see, I find it hard to understand why all the other stuff is >>needed and when to implement it. I can't help but think that the >>process could be made much simpler. >ted wrote: > >The wisdom is plumb not available to anyone with a 'ted' in his >name... RC tried to lead me by the hand through it some time back - >in fact he wrote the code - and it still seems impenetrable. LOL Maybe, it should be called offted GWorld, or offtedd GWorld. >Dr. P., some time back, allowed as how the gWorld thing was >unnecessary these days (in X or Cocoa or Carbon or something). If >anyone happens to be talking to him, mayhaps he could toss off a wee >ditty to illustrate the one-line-and-obvious-to-a-ted new method... >-- >Ted Spencer Now you tell me it's not necessary -- Arrrggggg!!! I simply have something that takes a fair amount of time (>700 ticks) and produces a very, very large graphic, which I want to scroll. I've already finished it (and it works) using Offscreen GWorlds, but I wouldn't mind seeing how it could be done another way -- especially when I intend for the finished application to run in OS X and not under older OS's. tedd -- -------------------------------------------------------------------------------- http://sperling.com/