I haven't tried old Haxe versions. I mostly test nightly and would recommend at least 4.2.5 (although I haven't tested 4.2.5 either).

hmmm, ill update at some point - though im not going to do that now... likely something will go wrong 😄 Isnt it a little bit of a limitation not supporting slightly older versions of haxe? 🤔

that limitations is simply due to me trying to keep things small, there is probably no reason why it wouldn't work with old Haxe. I just didn't have the time to actually do that, since the lib is still in very early stages and more of a proof of concept.

the lime mouse event just uses x and y values, so no component needed, and it will properly handle visibility. but I have no idea what component actually received that event. that's what I rely on

findComponentUnderPoint

for. so e.g. my testcase says find a button with id

mybutton

and then click on that button. if I just take x/y center-point of mybutton and send a lime event, then I have no way of knowing if that click hits. so finding out if the component on which a click should happen actually received that event is part of the protocol. a click is either a success or a failure and the testcase can deal with success or failure. sometimes failure is expected, for example when a button is underneath a modal window.

right, i see and you get back

["modal-background", "main-view", "hbox", "button"]

for that call, where as in this specific case

["main-view", "hbox", "button"]

is really waht you are after?

or is the button under the modal background?

the button is under the modal window, so technically it should not show up at all

well, i think it should show up for the getComponentsUnderPoint... haxeui is just telling you what components are under that point... not if they are obscured, partial, totally, alpha'd out etc

well, I'm speaking from the view point of my tests of course. so yeah the function is not limited to interactable components. and should list all of them, but the order is wrong to be easily usable

so, i still dont think im following: 1. there is a button in a vbox (button id = "button1") 2. you find the center point, and call getComponentsUnderPoint... you get back: ["vbox", "button1"] 3. button1 is the last item in the array (top most)... all good... click worked 4. this click brings up a dialog (with a modal back ground) 5. you try to click button1 again 6. find the center point call getComponentsUnderPoint, now you get back: ["vbox", "button1", "modal-overlay", "dialog", ... ... ... ] 7. button1 isnt the last (topmost) item... click failed

am i missing a step, or what the actual behaviour is?

button is still last item, "modal-background" is first item in list, because it is from rootComponent #2 and rootComponent traversal starts from the back

oh

so that sounds like a bug then

I just took a look and I'm currently using some

obj is Type

and some modul level fields, which makes it not compatible with anything below 4.2. but that should be easily fixable

i use obj is Type also, but i use (obj is Type)... ie,

if ((obj is Type))

- not as nice, but works on all haxe versions

well mine are missing the second parens. so that only works with newer versions (don't know when that was changed)

yeah, this defo seems like wrong behaviour

i explicitly reverse the root components

i wonder why - or maybe there isnt a reason

this certainly seems alot more correct

I guess reverse was meant to make sure that the element on top comes first, but the way it traverses childs doesn't align with that

hmmm, dunno... feels like i added it for a reason... but whatever reason it was, it wasnt a good one, since - exactly as you are saying - the list that comes out of find under point isnt representative of whats on screen

yeah that's what I figured. I mean I fund a way to make it usable for what I need, but ultimately it should give some more usable results

btw. I've updated haxeium to run with 4.1.5

OK, fixed - if it was there for some type of reason, then it was certainly the wrong fix from the get go

i was going to just comment it out... but its just not valid... for whatever reason it was put there for

... well, i cant figure it out - ive run the component explorer with this change and everything seems perfectly fine...