[EMAIL PROTECTED] wrote: > > No, it really doesn't. The reason tab panels can't reliably be placed > on each other has nothing to do with how things work under the hood, > and is mostly to do with how they're defined in your project. Every > control has one (count 'em!) TabPanelIndex property to indicate which > tab or page it's on, if it's on a tab or page panel. You can see this > if you export a window to XML, for example. This is a design decision > that goes back to prehistoric times, and projects would break like mad > if it were changed, but it causes confusion when you have nested panels. >
Why, then, couldn't a panel have a location index? Or am I not thinking clearly: a control is on control x control x is on control y control y is at the "0" level... you still only need one "location" property per control, correct? - CSW _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
