I wouldn't shy away from using the GM - it's a great time-saver and i've used it successfully but there are a couple of need-to-know things.
I usually set this as the very last thing i do in my app.
I then run in the messagebox:
Code: Select all
revCacheGeometry trueThen i also add
Code: Select all
revUpdateGeometryIf these 2 things were done automatically i'm fairly sure people would have many fewer issues with the GM, which is otherwise a time saver, and I believe there is an active bug report about this as above.
There are situations where GM alone doesn't work well - for example i have 6 adjacent groups, that all contain controls, and want them all to expand and move as the stack resizes.
I've written on resizeControl handlers for each of the group to move their constituent controls.
I then use the top left group as an anchor, and use the GM on that, so that is resized when the stack size changes.
But then i include code in the on resizeControl of the anchor that moves/resizes all other groups (the alternative would have been group these, which would have worked to reposition the whole group of 6 groups, but not resize them). Now my group of 6 controls expands/moves to fill empty space when users (invariably on Windows) maximise the window. Works fabulously, but did take an afternoon to sort out
A very valid point, especially as you can't use the GM inside a group - consider submitting an enhancement request to change this behaviour?
Stam
