I've played with this some in the past.
IIRC, changing the size settings in XML either doesn't produce any usable results or screws up the hardcoded layout such that lower level elements end up getting cropped by the window frame.
Kinda gave up dorking with it, but I think a workable solution would be to use onHover scripts to dynamically change the required sizing policies at runtime. This way the hardcoded layout can still do its thing, but onHover you can stretch the window.
Since these windows use template objects, to achieve the desired results, you're likely to have difficultly getting lower level object to respond to scripts. You may need to do some detective work to figure out what exactly the final nesting structure is within the window and what the resulting object names actually are.
|