Oh, awesome , thanks !

@bright-gpu-74537 Hi, is this the correct behavior?

xml
<vbox style="padding:15px;width:100%;height:100%;spacing:20px;">
    <style>
        * {
            border: 0px solid black;
            padding: 0;
        }

        .test1 {
            background-color: red;
            padding: 10px;
        }

        .test2 {
            background-color: green;
        }
        .test3 {
            background-color: yellow;
        }
    </style>

    <hbox styleNames="test1" width="100px" >
        <box styleNames="test2" width="100%" height="30px" />
        <box styleNames="test3" width="99%" height="30px" />    <!-- wrong size -->
    </hbox>

    <hbox styleNames="test1" width="100px" >
        <box styleNames="test2" width="100%" height="30px" />
        <box styleNames="test3" width="100%" height="30px" />
    </hbox>
</vbox>

it is yeah... there is special handing for "100%", ie, it will take the number of items and divide it by the space left, so 100% 100% 100% will become 33.3% 33.4% 33.3%.. ... however, there isnt anything special about "non 100%", so "80% 80% 80%" will overflow (since you are saying 3x80% = 240%)

I am using a blur on a scene change to discourage interaction and give a visual cue - long scene change at the moment. 2 questions. 1.

pointer-events: none

seems to prevent the mouse clicks while the change is going on but then when I remove the style the clicks are processed - so it's like they were queued. Should I disable instead or is this broken or .... ? 2. does HaxeUI have a spinner I can use ? I know the playground has one but I cannot find the widget

> 1. pointer-events: none seems to prevent the mouse clicks while the change is going on but then when I remove the style the clicks are processed - so it's like they were queued seems very weird... its not intentional, for sure, so sounds like a bug, might even be an openfl "thing" there is no event queue in haxeui... at least not intentionally 😄 - any chance of some type of minimal repro?? > 2. does HaxeUI have a spinner I can use ? I know the playground has one but I cannot find the widget so, the spinner on the explorer is literally just a

<image resource="loading.gif" />

, this is because haxeui will leverage the capabilities of the host, which in this case is the browser which supports animated gifs natively. Openfl doesnt support anything like animated gifs... ... ... however you are in luck! 🙂 There is a

Animation

component in core which is built off of the cross framework

Canvas

component and this does support animated gifs (in fact, in only supports animated gifs currently), so this can be used to show animations on all backends: http://haxeui.org/explorer/#basic/animations (note, you'll need to include the "format" lib which it uses for gif decoding)

ah .... ok so I was on the right track looking at Animation - cool. Thanx. On the pointer-events thing - it seems only the first is queued and played after - if I click multiple times only the first shows effect - but there may be something else going on - I need to check how the new scene renders - if may be removing the style sooner than I thought. If it still looks like a problem I'll try to get a test case

The button onclick event is not triggerred when I click the padding...

this.ui.findComponent("restart").onClick = function(_)
        {
            FlxG.switchState(new PlayState());
        };

are you saying that the button isn't being triggered when you don't click on the button? 🤔

The button has padding and a border.. It is only triggerred when I click on the text...

so when I click on the padding/border.. it doesn't trigger.

can you gif what you mean?

or demo it on the component explorer

demo code would be best for ian to quickly test/bug fix the behaviour, the style and button component xml

I tested it some more locally.. I honestly can't tell if its due to my machine (zooming in on the screen tends to break window focus sometimes). I suspect its just an error on my part because alt tabbing to the game window fixes this particular error.. Gonna have to do further experimentation to validate that hypothesis.

a quick gif would be useful, i'm used to noticing the differences between pixels

no need to zoom in, i should be able to tell if it's off at normal resolution

pixel differences is the bane of ui dev 😂

nah, I zoom in because my eyes are crap and wouldn't be able to read otherwise... My zoom tool messes with window focus soo I'm assuming thats why my button is borked.

well, if you want a second pair of eyes just shoot me a ping. If it seems off it very well could be

^ need to prove/disprove this theory though.

I'll do that 🙂 Your offer is appreciated.

gratitude += 100

Regarding

pointer-events:none

. I think I am fairly sure my new scene switch impl should not be returning too early. But I noticed something I was doing wrong with the selector. I had thought that pointer-events could be applied to the enclosing vbox and all components below would not receive events. Seems I was wrong. So I tried this:

.loading {
    filter:blur(3px);
}

.loading * {
    pointer-events: none;
}

The

loading

style is added the UI's outermost vbox and sure enough the blur appears and the disappears when the class is removed. But with this setup the pointer-events are never restored to the underlying checkboxes when the class is removed. I don't yet have a small test case but I think I see how I could create one.

Hey Ian, what's the state of haxeui android again?

So there is version up there, that honestly, im not sure would even compile anymore. However, i have a partially rewritten version on my other machine, that i really need to get to GH and is much better. The state iirc was "fine"... but i hit some issues (which i cant fully remember now) around listviews with [unreasonably] complex custom item renderers... But for the most part it was working alright for simple(ish) applications (buttons, lists, text inputs, checkboxes, switches, tabs, scrollviews, etc). All that said, im going to need it fairly soon for a project / contract. Although, my current understanding of the scope of the project and my memory of the state of haxeui-android, it would already be fine. I think ill pencil in some time this weekend to give in the once over and see where i left off, and get it all on GH

thank you!

Do you think it will be fine for a camera app?

i cant really think why not... i mean, since its haxe jvm you should have access to everything java has access to

My only experience with Android development is through Cordova, and I didn't like much the plugins ecosystem/mechanism. How is the experience with Haxe?

Oh, and I hate Java 😂