|
From: Andreas R. <and...@gm...> - 2004-03-21 12:18:06
|
Tim, > Indeed, but what interaction should it have with the > deferDisplayUpdates flag? I'm puzzled by the way that > the win32 code for this does involve deferDisplayUpdates. ioForceDisplayUpdate is a no-op on Windows these days. Ignore it. > That's fine; it would be nice to have better commenting of > this where possible. Again, the win32 code refers to > deferDisplayUpdates which has the same concern as above. And the same answer. Note that both of these depend on the setting of the "fDeferredUpdate" variable which predates "deferDisplayUpdates" a couple of years. But it's turned off by default these days. Cheers, - Andreas |