well, electron is just the container for the app though, so has nothing to do with inserting all items in a UI when it changes, thats the job of the framework - just seems like a bit of a crazy way to go about things. I mean, for html type apps i guess its ok, as presumably its super fast - but recreating 100 native components when you just want to add one to the end?

Not recreating them

right

Reinserting them in their parent component at a specific index

ok, thats different then... my bad, i misunderstood

Might just need to check if said index is still good to optimize a little

yeah, but even reorganizing 100 items is presumably going to be a fairly cheap operation... well, fairly

(compared to what i incorrectly understood which was to recreate them from scratch)

Poor man's padding x)

do you mean something like this: http://haxeui.org/builder/?fqbyvs

?

Nah I just want X pixels around my own component

And padding doesn't seem to work on hxwidgets

oh?

if you mean padding inside the button, then yeah, that aint gonna work as the OS (wx) will fix that, best thing you can do is give a fixed w/h

(which wont work on osx fyi)

(who cares about osx °°)

Nah it's padding outside button (so inside box), doesn't work

heh heh, enough people to keep them in business 🙂

doesnt work via coconut you mean? Seem to work fine "normally"

looks like maybe another issue of styles being eaten somehow? It might be worth you setting up a "traditional" haxeui-hxwidgets so you can test if things work as expected without the coconut update "stuff"

Nah, other styles are applied (background is black)

unless im not understanding, it works just fine on my machine so its a) coconut or b) your box

background colour is different to padding though, in the sense it will (probably) require things to resize

ie, in the screen i sent above... the padding is caclulated after the backend has gotten the size of the button

well, i mean the size of the boxes (with the padding)

Doesn't seem likely that these would work with coconut

how could anything then? I mean, a button has a native size (an OS defined size)... you put that in a box with a padding of 10, well, in order to know the size of the outer box you need the size of the button, the flow that upward to the size of the parent (and potentially all the way up the tree also btw)

I meant if some resize things are needed to be handled besides passing the data to the component (including its padding) then it won't work with coconut