> Page Panels behave a bit too much like Tab Panels > (e.g. all controls are "really" on the same page...
This is to be expected, since TabPanel is a PagePanel subclass. I have had success using a PagePanel where each page contains a single ContainerControl subclass, which contains all the controls that the user will see on the corresponding tab. A custom Canvas subclass acts as the tab-switching mechanism in my case; I see no reason you couldn't use a TabPanel instead. It works great on Mac OS X. I haven't tried it on Windows so I don't know if there are flicker problems. I also haven't tried it with panels that attempt to size themselves dynamically as one sees here and there. I don't quite trust the IDE window editor for PagePanels and TabPanels yet, after having some extended, miserable experiences with them using RB 5.x. Also, I find it far easier to keep things consistent when I can look at all the panels at once. I don't think I'd use "raw" Page/TabPanels again without this technique except in very simple cases. There is a glitch on Mac OS X at least; if I change the ContainerControl's layout, its image within the PagePanel doesn't immediately update. But that is just a cosmetic problem in the editor and needn't affect workflow (and it might have been addressed in RB2006). lj _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
