Community
Participate
Working Groups
Build Identifier: 0.7.0.v201109282102 1) Open the BorderContainer.egl in attached project with RUI handler with VE. 2) The outline view should show the hierarchy tree of the component. Please refer to the attached picture for the detailed information. Reproducible: Always
Created attachment 204255 [details] The sample project.
Created attachment 204256 [details] The screen-shot.
It use new Div{}, blocked by 359165
I looked at the Handler in this project, and it contains: top Div = new Div{}; While I agree that this code needs to be handled correctly by the VE Outline in the future, I don't believe that this issue is a high priority at this time. I do not believe that this issue is a high priority because the EGL source, while technically correct, is not something we would recommend as a best practice. In the line mentioned above, a new Div is first created and assigned to 'top', next, a second Div is created and assigned to 'top', resulting in the initial Div being thrown away. The recommended approach would be: top Div{}; Note that since there is no '?', the variable is treated as a 'value', and a new Div is instantiated immediately, followed by the processing of the settings block. If a '?' had been used, a 'new' would be required: top Div? = new Div{}; If you are seeing an issue with the outline view when using either: top Div{}; or top Div? = new Div{}; then this issue can be raised to a high severity and priority for .7.
Created attachment 205899 [details] test case 2
Hi, Brian I tried top Div? = new Div{};, and the problem is also occurs, see attached test case 2. Rocky said the defect is not important, so I did not investigate into it.
I retried the testcase in comment 5, and it looks like things are rendering correctly. Please re-try this and provide additional information if things are still not working as you would expect.
if this is not already fixed, then it is being deferred. If you retest and it is fixed, then resolve, and reset target to 070 final
Closing as working as designed. When something is created dynamically, it should not be editable in the VE: top Div? = new Div{}; If you do not agree, please reopen this defect.
