Yeah, kde people like fancy things xD

After removing a component from the screen, it stops rendering (as expected). . . However, the mouse still interacts with the buttons of the now removed component. But, if I execute

Screen.instance.removeComponent(view);

before any rendering happens, then none of those ghost-component interactions occur. Any ideas? Did I do something wrong?

I can post code, it's pretty minimal

yeah, code would be useful... also, which backend is probably more useful - feels like a bug

haxe
import haxe.ui.macros.ComponentMacros;
function main() {
    var app = new haxe.ui.HaxeUIApp();
    app.ready(()->{
        var component = app.addComponent(ComponentMacros.buildComponentFromString("
        <box width='100%' height='100%'>
                <vbox style='padding: 5px;' verticalAlign='center'  horizontalAlign='center'>
                    <button id='playbtn' text='Play!' style='font-size: 45px; border-radius:20px;' />
                </vbox>
        </box>"));
        // Press any key to remove component from app view - notice it's still "functioning"
        kha.input.Mouse.get(0).notify((_,_,_)-> app.removeComponent(component));
        kha.System.notifyOnFrames(app.render);
    });
}

For Kha, haxelib version

My HaxeUI is a bit rusty

Alright updated the code so that it just uses main and is self-contained. XML doesn't really matter except for buttons

> For Kha, haxelib version The haxelib version of Kha is outdated, and you're not supposed to use it. The intended way to use kha is to add it as a git submodule to your project. (Or are you talking about the haxelib version of haxeui-kha?)

I'm using the haxelib version for haxeui-kha

Ah. Haxeui-kha should be up to date on haxelib.

feels like a haxeui-kha bug tbh

leave it with me, ill see whats going on

Thanks! Lets split up and search for clues . . . lol

haha!

It’s the 25th anniversary of that show…

Nice Ian. Is there a property to autohide the scrollbar until rollover the contents (or maybe touch)?

sure... "autoHideScrollbars" or "mode:mobile"

right, thank you

(first is xml / code, second is css)

Or maybe, if you read your link, in module (didnt mean to sound snarky, I thought it was great new feature)

that aint gonna work

:p

autoHideScrollbars is a class level property

damn, I should have stayed snarky...

<property name="haxe.ui.components.scroll.style" value="autoHideScrollbars" />

will apply a css selector

.autoHideScrollbars

to each

haxe.ui.components.scroll

so if you had:

css
.autoHideScrollbars {
    mode: mobile;
}

somewhere, then it would work

although, you would also need change the property name to

haxe.ui.containers.scrollview.style

not sure if that makes sense?

ya, I will play, it seems to make sense. So what else does mode:mobile do? I suppose I should go look for it