Copyright © 2008, 2009 Arndt Roger Schneider
Each window must be visible when hijacked. That is, each call to »hijackwindow« has to be performed in response to a »<Map>« event. This is also required to gain acceptable performance. The hijacking is thus broken in smaller chunks, which can be performed without slowing down the Graphical User Interface at all.
The Example 6.4, “Use The Map Event for hijacking” contains an additional binding for the configure event on the container window (in this example a toplevel). The configure event must be processed geometry changes.
The hijacking of labels is identical to messages.
Labels may feature multi-line text. The »justify« property will be used to align the successive lines. I recommend using »messages« for multi-line text. Labels should be used for descriptions and not to display verbose informations.
The window is lowered behind the stripes–enslaved by its hijacker–, after hijacking. This disrupts the window Z-Order and thus the focus ring is in disarray.