True, but these properties are certainly within the control of the
developer, no?
IOW, the procedure can still be used in standalones, unless a
standalone's stack cantmodify is set tot true.
best,
Chipp
Wouter wrote:
This will still crash in certain cases.
Because a stack with its cantmodify set to true and which buffered
state is not true, cannot be forced to update its screenbuffer.
The effectiveness of a screen buffer update can be seen in the
difference between the pixmapID of a stack and the windowID of a
stack. If those numbers are the same the stack is NOT buffered and the
handler will crash gloriously.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
