Right but I don't want layout and styling to affect the result

Like, animation replaces the existing

tile

with a different one, but haxeui is probably creating new textures and setting that same field

Maybe it's just a matter of adding a non-component object, but I'd like it if that could still be laid out

i'm not sure what the "correct" procedure to modify internally used fields like that tbh

it doesn't seem like it is

it reads the default set tile once

There was something I had issues with before, but maybe it's changed

altho i didn't try with the animation prop

just with a standard image prop

yessssss

nice 😄

nice

I'm having trouble with a vbox sizing in an accordion section. The example is at . When it loads if you open the "Lighting Test" section and then select the optionbox for "Light Casters" you'll see that the scrollview extends beyond the vertical space opened for the accordion section. The problem is that the vbox at L93 has a fixed height. But if I remove the fixed height then the element only shows the top border line and no content. I have tried setting the various vbox, frame and scrollview heights but cannot find a combination that allows me to get this to work without a fixed value height. What I really want is for the content of the accordion section to fill the space in the section automatically. I keep adding sections to the accordion and I don't want to have to resize the manual height values to avoid having the content overflow the open section, if I can avoid it. Any suggestions ?

The Canvas component is new for me, and it's along the lines of what I was thinking. But also I can just extend component I think

+

comp.styleable = false

it looks like?

yeah, i think if you set styleable to false then basically it skips any haxeui drawing meaning you can do anything you want with it... thats the idea anyway

yeah, there are a few things that seem a little weird there, but its a big layout, so will need some time to parse it, extract bits and see if they are borked in isolation

it is what you want ?

oh yeah... it still doesnt make it totally right, you are correct there is a few things like that

tbh, i would be very tempted to split all this up into multiple files... its quite hard to understand... and thats really quite a feat with xml layouts 🙂

Yes there is a problem with width too for sliders,and components that are not always hidden like they should be

yeah, there seems like quite a few missing 100%'s

like that i think is better for simple lighting

?

i basically just added some 100%s to certain parts of the UI - you'll probably need to diff to see exactly what / where

thanx for this - yeah breaking it up might be a good plan - I am not yet sure how I would do that - should I create components for each chunk - or should I just import files for each section but not really built as components ? I guess I don't know what my options are. As 100% in various places - I am always a bit unsure as to when to add them and when not - it ends up coming down to trial and error. What's the general rule ?

What is the problem with width for the sliders ? And I don't know exactly which components you are referring to that should be hidden. I know that some things are not hidden in some cases - I had problems with the hiding of bits of the labelled-sliders and introduced a bug when I didn't get that right - still have to resolve that.

well, the basic idea is if you want the child to be the size of the parent, the thing i think that catches everyone out (it seems) is that if the parent is autosized (ie, doesnt have a px or % size) then 100% will lead to 0

and this works up the display tree too... so if you have 5 levels of 100% but your root component is autosized, then all 5 levels will be 0