ok so I'm wrong bc that listener doesn't work on my local

only on the builder

my full new() function is

hx
    public function new() {
        super();
        unitSelector.registerEvent(ItemEvent.COMPONENT_EVENT, (event:ItemEvent) -> {
            trace(event.itemIndex, event.data.checked, event.data.text, event.sourceEvent.type);
        });
        gp = {
            width:Std.int(graphDisplay.width),
            height:Std.int(graphDisplay.height),
            dateStart: new Date(2022, 10, 1, 0, 0, 0),
            dateEnd: new Date(2022, 12, 31, 11, 59, 59),
            units: [
                A1
            ],
            params: [
                RT
            ]
        }

        var metricNodesTree = unitSelector.addNode({text:"Metrics"});
        for (metric in Type.allEnums(Params)) {
            metricNodesTree.addNode({text:EnumValueTools.getName(metric), checked:(metric==RT)});
        }
        var unitNodesTree = unitSelector.addNode({text:"Units"});
        var coolTree = unitNodesTree.addNode({text:"Thermals"});
        var powrTree = unitNodesTree.addNode({text:"Power"});
        for (unit in Type.allEnums(Units)) {
            if (EnumValueTools.getIndex(unit) <= 12) {
                coolTree.addNode({text:unitNames[EnumValueTools.getIndex(unit)], checked:(unit==A1)});
            }
            else {
                powrTree.addNode({text:unitNames[EnumValueTools.getIndex(unit)], checked:false});
            }
        }
        loadGraph(gp);
    }

is the builder using a different version of haxeui?

I'm on 1.5.0 for core and html5

oh wow, yeah, you wanna upgrade to git

1.5.0 is like 4 months out of date now

and yeah, builder is on latest git..

swapped both to git

... ... ... ... all good?

ok yeah lmao I was using old libs

should be

heaps: any way to disable cursor changes within a component? All of my interactives are overwritten by haxeui's cursor behaviors. I see 'pointer-events:false' in core but it doesn't seem to exist in heaps

any chance of a minimal repro, not 100% sure, but smells like a haxeui-heaps bug

Just found a bug and found the correction. WIth Item Renderers I was wondering why dropdowns didn't send ItemChanged events . ( In fact it send only when it was clicked but not when it was changed) https://github.com/haxeui/haxeui-core/blob/3b7ee39153b00b7279ea0c8d801728821aef3c13/haxe/ui/core/ItemRenderer.hx#L102-L109 it it's because if it's a button ( which is the case of dropdowns), it only dispatches on a CLICK event. I just removed the else

Hope this helps

I'm (still) working on a new backend for haxeui and just a quick question. I'm looking at the heaps implementation, and in the StyleHelper.hx code which has the bulk of the logic for creating the geometry, it looks like a component can only have a background image and potentially a gradient image if there's a background color gradient, does that sound right?

yeah, background-image, and background-color (or background for gradients)

exciting stuff, i think you might be the only other person who has created a backend... certainly recently

what is this backend again? lime or raw opengl calls?

hmmm, yeah, this seems smelly.... this is somewhat related to the above... ie, without the if it will generate two events, but i guess thats preferable to this dumb "if its a button" logic

thanks ill take a look

found a fun little bug while tracking this down... if you remove a component from the screen in haxeui-heaps, it still thinks its on screen and "in bounds", so still gets mouse events 😮

Is it really problematic to have two events ? I think it could be useful, for example if you want a sound effect on the clicking of a dropdown.

i think thats what im kinda settling on, they are discrete events, i mean, take the checkbox... it will dispatch two ItemEvent events, one for the click and one for the change... both are technically totally valid

(and both could be useful to the user)

one thing that might be nice though is in addition to

ItemEvent.COMPONENT_EVENT

we also dispatch a

ItemEvent.COMPONENT_CHANGE_EVENT

and a

ItemEvent.COMPONENT_CLICK_EVENT

(where relevant)... at least that means you can just listen for the event you care about

Oh that's a good idea, so you don't need to look at the source event

i just dont like this sort of stuff:

haxe
function foo(event) {
    if (event.sourceEvent.type == "change") {
    }
}

exactly