confirmed working. I wasnt sure about having the callback inside the null check, makes sense in retrospect. Thanks

yeah, even if the imageInfo is null we still want to call the callback (with null effectively), the issue was i was trying to set something on that imageInfo without checking to make sure it wasnt null... doh

I was also thinking maybe a trace would be handy, as you arent loading anything...but wasnt sure it was a place for that sorta thing

is there already a warning trace if the image cant be loaded? Maybe just in debug?

Well, not in that code. Jumping on conference call. I'll try and check on return

Before the fix I got this haxe/ui/backend/AssetsImpl.hx:34: Null access AssetsImpl.hx:34 After I get nothing.

I can try and create a sample project if you want to look at it. Not sure its a big issue but seems worthy-ish

i dont follow, you mean you give it a non existing image, that used to break, it doesnt now, but it doesnt show anything... isnt that normal behaviour?

yep. Before it logged an error and crashed. It now doesnt log anything. It silently fails on not loading the svg

I guess I was expecting a log or something saying file doesnt exist but not a crash.

Thank you very much!!

any movement on this? \:)

hmm, it doesn't seem css layouts or xml layouts work anymore http://haxeui.org/builder/?0b5b8fdf ? ( did it ever work ? hmmm ... I think so.)

Hey ! I have two questions about the fade in/out animations : First, how do I change settings for the animation ? I've seen the CSS bit and I can change it but wouldn't I change it for all fade in/out animations of the UI ? What if I want some settings for a component and other settings for another ? I've tried this but it doesn't work (on the Builder) :

.myStyle .fade-in {
    animation: animationFadeIn 1s linear 0s 1;
}

Or should I copy the function and use other css classes (change the ``swapClass("fade-out", "fade-in");``) ? Then, is it supposed to be backend dependent ? My fade is instantaneous on Heaps :/

Looks like https://community.haxeui.org/ is down?

Oh, yeah, it is for me too

I've introduced a bug in the Heaps backend :D Since I've changed stuff with the mouse so we could process events in the right order (children first then parents), the cursor is not changed anymore if a button is child of a scrollview :/ It works if I revert the event order for the mouse over. Thing is, it does change the cursor because of the button mouse overing but then, it changes it back to default because the more ancient component are processed afterward and override the cursor settings (in ComponentImpl.__onMouseMove) What do you think would be the most appropriate solution there ? Not change the cursor if it's already been changed ? Also having a way of knowing if the components are over of underneath other blocking components to not have unwanted behaviors (maybe it already exists) ?

I am trying to move background image so I can recreate haxeui logo with tiles http://haxeui.org/builder/?eb3a48bc These call doesnt appear to work? tile2.styleString='background-position: 68px 0px'; Anybody know a better way?

oh, community server does seem to be down... was away in Sicily for the weekend :/

do you mean "layoutName" ?

not sure background-position in supported in haxeui - you could "cut out" bits of images with background-image-clip (i think thats what its called anyway)

none yet... :/

alright, community server back online... phew

Oh indeed it does work with "layoutName" (but it says "layout" here https://github.com/haxeui/haxeui-core/blob/f5ea6c99e01c2b140627a956dd93a3c77ecc1269/haxe/ui/parsers/ui/XMLParser.hx#L326-L327 so I think it should work with layout too ) in the xml version. But in the css , it doesn't and shouldn't it work with "layout" ( https://github.com/haxeui/haxeui-core/blob/f5ea6c99e01c2b140627a956dd93a3c77ecc1269/haxe/ui/styles/Style.hx#L492-L498 )? confused 😕

Bravo !

so, "layout" is handled totally differently, its actually legacy stuff that im fairly sure wont even work... the idea originally was that you could do :

xml
<box>
   <layout>
       <someLayoutProp />
   </layout>
</box>

but actually, there doesnt really seem to be any layouts that need specific props, and also i think i would actually prefect something like

<box layout:someLayoutProp="" />

(but again, this has never been needed so far)

i actually think im going to replace layoutName with layout (ie, remove that legacy code), as ive certainly done "layout" and it not work and then gone "ah, yeah, its layoutName", and "layout" serves absolutely no purpose

ok, so, i dont know why layout in css doesnt work though, that feels like a bug

alright, so im going to remove all of that junky legacy "layout" code (tomorrow), and change layoutName for layout (layoutName will still work though)... ill check out why css "layout" doesnt work then