Many of you know I've been working on a ribbon bar implementation, and so far it's all gone pretty well. Today I was trying to implement a new behavior in the bar, and ran into something weird.
So, my assumption was that if you made the pageframe height = 1 or 0 that it would effectively have the appearance of the page from being "invisible". The idea being that some people don't want the ribbon bar to stay "in the way" while they're doing other stuff, and only want it to pop down when they go to the topline menu, or maybe choose to turn it on and off.
So I built a routine that slowly collapses the pageframe down to 1 pixel high. (This is good, as it helps maintain the appearance of the bottom "bar" of the top line menu.
But then I discovered, where I have "container" objects on the various pages, they do not "collapse" with the page frame itself. So if I go to another page, those icons (which are in container) remain on the main form background, and if I change page to page, they will even "overlap". Though other controls (like drop-downs, spinner, non-containerized objects) vanish and appear as the page grows and shrinks. Is there something magic about the container objects on a page like this, and if so, how can I get them to follow the "collapse" behavior?
MIET, MASHRAE, CDCP, CDCS, CDCE, CTDC, CTIA, ATS
"Everything should be made as simple as possible, and no simpler."