You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by softhorizons August 25, 2022
The editor automatically splits multiline statictext into multiple statictext's inside a group, something like:
var staticTextOneTwo = grpMain.add("group");
staticTextOneTwo.add("statictext", undefined, "One line", {name: "staticTextOneTwo"});
staticTextOneTwo.add("statictext", undefined, "followed by another", {name: "staticTextOneTwo"});
However
the group isn't named
the individual statictext's have the same name
This makes it very inconvenient to access the auto-generated group and sub-elements. You really want to access the group as control.grpMain.staticTextOneTwo. I find myself manually creating a group of single-line statictext's to work around this.
It would be great if the editor emitted:
var staticTextOneTwo = grpMain.add("group", undefined, {name: "staticTextOneTwo"});
staticTextOneTwo.add("statictext", undefined, "One line", {name: "statictext1"});
staticTextOneTwo.add("statictext", undefined, "followed by another", {name: "statictext2"});
Though really, it might be cleaner to not emit names at all for the single-line statictexts since it makes more sense to access them as ...staticTextOneTwo.children[0, 1, ...]. How about it?
The text was updated successfully, but these errors were encountered:
Discussed in #99
Originally posted by softhorizons August 25, 2022
The editor automatically splits multiline statictext into multiple statictext's inside a group, something like:
However
This makes it very inconvenient to access the auto-generated group and sub-elements. You really want to access the group as control.grpMain.staticTextOneTwo. I find myself manually creating a group of single-line statictext's to work around this.
It would be great if the editor emitted:
Though really, it might be cleaner to not emit names at all for the single-line statictexts since it makes more sense to access them as ...staticTextOneTwo.children[0, 1, ...]. How about it?
The text was updated successfully, but these errors were encountered: