On 9/28/07 11:32 PM, "Dave Wooldridge" <electric dot butterfly at mac dot com>
wrote:
> Thanks for that suggestion, Tim. As it turns out, earlier this afternoon, I
> grouped the controls from each PagePanel page into their own Container
> Control, so that each PagePanel page now only has one Container Control
> assigned to it. This way if the controls ever scramble again, all I have to
> do to fix it is drag each Container Control off the Page Panel (onto the
> Pasteboard) and then drag them back on the PagePanel to auto-reassign the
> correct parent-child relationship. It will save me a TON of time in the
> future, since I'll no longer have to fix dozens of controls individually,
> but now only manage 3 Container Controls with the 3-page PagePanel. I
> tested it by resizing the window in the IDE to force the control scramble
> bug to occur, and then easily re-assigned the Container Controls to the
> PagePanel to fix it, and it worked beautifully. :-)
>
> Regards,
> Dave Wooldridge
> Electric Butterfly
> http://www.ebutterfly.com
Hey Dave,
Better yet, ditch the pagepanel all together. You'll never look back!
Create a single containercontrol property in the window. My master window is
sized to the toolbar. As the user selects a toolbar button, the appropriate
containercontrol is initialized in the window property and the window
resizes itself to embed the control.
It's worked flawlessly for me. Besides exorcising the demons of paegpanels
all together, as an added benefit each container control encapsulates the
functionality of a former panel. I've found the refactored code in 18
container controls immeasurably easier to maintain than the former single 18
pagepanel window with hundreds of methods and controls.
Keith DeLong
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|