Haxe

It's mostly to work around the dropdown selector spawning in the wrong place. This is caused by something I did, but largely unfixable since the dropdown options place themselves at the DOM root instead of as children of the dropdown

I'm kinda ignoring it for now, will look more tomorrow

Everything's coming in crazy hot for LD and I keep finding new major features that need written <:REEE:415021272494505988>

well, when / if you get time... an issue would be nice, esp the " dropdown selector spawning in the wrong place. This is caused by something I did, but largely unfixable since the dropdown options place themselves at the DOM root instead of as children of the dropdown" part

hows the LD entry coming along? Whats the theme?

LD is this weekend. THis is pre-LD tools and engine integration work

Work's busy as heck too, so I dont' have a ton of time to actually sit down and write code, and I made a huge last-minute tool switch that needs a bunch of associated work <:suzudeflate:587030520412635139>

and so, out of interest, how / where does haxeui fit in? 🙂

Basically I spent like 3 months integrating Articy:Draft

Then found out their pricing model is basically hell, and had to smash the eject button

so the node editor needs to replace a major component of Articy, plus the rest of it needs to be grafted around a few other tools (mainly CastleDB)

<@385014891750096896> yeah since It can get in infinite loop I think it would be better to remove it. But , we could have the old implementation and juste cache the transformer and set it to null during the while then set it back after.

<@385014891750096896>  So ItemRenderers seem to only show one field even if multiple are present( there is a quick fix but I just want to make sure this is the intended behavior). So for example I have ``` <item-renderer width="100%" >
        <textfield id="typeName"  width="100%" />
        <label id="className"  width="100%" />
</item-renderer>
``` The item renderer will show only the textfield by Items. So is this what is intended ?

The quick fix is to wrap all the fields in a box,vbox or hbox. But since the itemrenderer is a box it feels redundant to add another box.

i think its because the item renderer is a box, not an hbox, vbox

`<item-renderer layoutName='vertical'>` should work, no?

maybe its `layout`... ... or maybe it doesnt matter

yeah; setting the layoutName does the job thanks !

Another question: Should the items autopopulate with ItemRenderers ? Because when I have multiple Items the first Item populates the data of the fields but not the second. The typedef has the same named fields as the xml definition id's.

Yes; will try to debug to make sure the data is well set because on another object that had only one item the fields werent populated;