Re: Does the IDE support having controls on >1 layers
Andrew Katz wrote:
>
> The only thing I would like is that controls placed on a tab cannot be
> captured
> by controls in another tab. This needs to be done in grand parenting. For
> example
> if control A's parent is Group 100 and Group 100's parent is tab2. Control A
> should not be be captured by control x whose parent is Group 200 and
> group 200's parent is tab1. Or by group 200. The way I design tabs has
> controls
> overlapping. And the more tabs the more confusion the way the IDE is now.
>
> Andy Katz
I got lost by your term "captured" so I'm assuming control A is the control you
are moving. When you move a control into TabItems IDE should look at the ACTIVE
tab (the one whose Name appears in the dropdown in ToolBar) for possible parents.
However the parenting routine specifically requires a prospective parent control
be a control in Layer 0 or the same layer the moving control is in or at the same
X and Y as the moving control. I'm not too sure why I made this rule and changing
it might break other people's projects. From what I understand about your project
you may not have your layers set up this way.
Can you send me a small sample of your project (just the TabControl and all the
controls within the TabItems) with Control A outside the tabs so I can see what
is happening when I move control A inside the tabs?
judith evans
|
Not Categorized, Please Help
|
|