OpenEuphoria

Re: Release IDE version 0.18.6m

• Posted by "Judith" <camping at txcyber.com> Feb 10, 2004
• 585 views

Thanks for the idea, Hayden, but the problem is that IDE wants to figure out
parenting of controls at exw time. Parenting is normally established when
user drops a control onto Design or moves a control into a container
control. There are situations in which it needs to be re-established parent
at exw time. Since your post I found the bug in findDirectParent routine. It
wants to find parent of a control but only when the control is in the same
layer as the active layer. This routine serves a dual purpose (1) when
dropping into a control/moving the control in Design and (2) at exw time
(which I missed.) Since Layer 1 was the active control, IDE did not
re-establish Group2 in Layer 0 as parent of the other 2 controls and used
Window1 as parent. When Layer 0 is active then it worked. But if Layer 1
perhaps had a group control and child controls, and I internally set layer
to Layer 0, then the controls in Layer 1 would not parent to its group
control properly. This is probably more information than you wanted LOL. I
just need to fix findDirectParent to work correctly when fired from the exw
generation routine. Your suggestion would be a good one otherwise.

I'm not sure what the problem was when you got the " not declared" errors.
But, please do not use version 0.18.5 since it was a testing version, with
other bugs,  and many testing versions followed until 0.18.6m which is the
official one.
~judith

Hayden McKay wrote:
The origional bug I found when user selects 'run' when viewing layer1, and
controls in layer0 where producing 'not declared' errors.
eg: In the bug.prj I posted I was expecting to get a
"If isVisible(Group2) then
    Group2 has not been declared" error.

When selected run while viewing layer1.

I believe that this has something to do with the same bug we found below.

I dont know much about the IDE structure, but here is a posible fix that
would not require a huge operation to fix it.

Maybee when a user selects 'run' when viewing 'layer1' in the frame, IDE can
default the frame view back to 'layer0' (as if the user clicked the 'layer0'
tab) before produceing the exw. You could even do this silently so the frame
would still have layer1 in the view, but IDE would act like user is viewing
layer0. Then after exw is generated, IDE could return to its previouse state
and lauch the exw as normal.