Auckland is as bad as Berlin was when the wall was up

the way the world is going, i wouldnt make any plans for 2022 yet, likely all be dead by then 😄

i was ready for 2000 meltdown.

heh heh, true

@User I ran into a bit of an issue using the locally defined module last night when I compiled to native (kha/linux). I got a segmentation fault and dump. This happened when I added the second screen which was entirely themed. It occurred when the XML Component was being built. It works fine if the theme resources are moved into the first screen's CSS and the Asset folder. I believe that I will need to push the theme pack to an external library to get it work ok. I am going to press on with screen builds at present until I get to the point of needing a custom component or getting them all built. Then I will circle back and play with the theme module.

ok, it would be good to get a minimal test case of that... you certainly dont (or should i say shouldnt) need to have an external haxelib for a theme... its neater, but its defo not a requirement

so a minimal reproducible test case would be nice, as that sounds more like a bug than a feature 🙂

that sounds like a plan. Is it possible to place sounds in the theme?

^ If not, that's a pretty interesting idea

I had to play with Alsa to get it working but I got the background music to play whilst loading the resources

You can place them as resources but the way kha treats then is Assets.sounds.

no concepts of sounds whatsoever in haxeui

i mean, in built

im open to suggestions / ideas though...

what would be the use case? Mouse over a button and it makes a sound, click it, it makes another sound?

I'll add it to the test case and see if I can get it to work. Yes, different sounds per action.

just like the OS theme

i wonder if thats outside the scope of haxeui?

i mean, wouldnt you just have the sound playing on different event handlers?

may not matter if we can use the theme just to store the sounds

I don't know if the backend can access the resources placed in the module

should be able to

how does the resource list get built from Toolkit.theme?

it basically looks up all the "style" entries from the them with that name

well, it looks like I got a different project for this morning then what I was planning on 😛

😄

I'll try and get something up in my github for tomorrow then.

cool - for the theme crash? Id like to get that sorted as it doesnt sound right, so something is up

yep, that and the sound thingy. I'll just use the start button screen I was working with.

sounds great, lemme know when you have something working, by which i of course mean broken 😄