OpenEuphoria

Re: Does the IDE support having controls on >1 layers

• Posted by Judith Evans <camping at ccewb.net> Mar 18, 2007
• 513 views

Andy Katz wrote:
<snip>

I am still not sure if I can make my tabs of different sizes, so that some
controls can be on 2 of my tabs and not the third. I will let you know
when I get to this issue.

However, I still have a huge problem with the IDE. The parent of a control
in the IDE acts in a very quirky way. I cannot assign the parent I want
until I move the controls just right. Many times I have had to start over
and move the controls back into groups one at a time. I would suggest that
the IDE does not try to guess what parent each control should have, but the
parent drop down should include all of the controls.

Andy Katz

I am not likely to make the parenting change you suggest. I want to control the
parenting. If I included all controls people could pick a control to be parent
that isn't anywhere near the moved control. There are several ways you can move
controls. By mouse, by keyboard arrow keys and by right click in the control you
want to move in Design and selecting "Move" followed by right clicking in the
place you want the control's upper left hand corner moved to and and selecting
"paste." Parenting will be reassigned after paste.

I don't think the parenting is assigned in a quirky way but anyone is entitled
to believe so If a control is moved into another control it becomes child to
that control. IDE used not to work like that in all cases; only if the moving
control ended up in TabItem, ToolBars, ReBarBand, Group, CWindow, StatusBar,
Table, EuGrid, and any other container controls, was that control made the parent
of the moved control. But as more and more people wanted to parent to other
controls that are not container controls I changed the rule to the present one.
To help people that wanted controls to overlap but not obtain parenting I opened
up the Parent dropdown in Properties. I'm sorry this is a problem for you. I
possibly could add a new item in Configurations that you would check for
parenting to be restricted to Window1 and/or a container control. If the control
were moved over a control that is not a container control then the parent would
be Window1. Mull this suggestion over and let me know if it would help you. This
will not be a trivial enhancement but is doable.

judith evans