https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • h
    actually, this is funny. I just realized that bob.assets is going to be the exact same xml as 
    Test1
  • h
    but different packages because bob is in the string even though 
    ..
    effectively says "I am not the bob you're looking for"
  • b
    ok, nice
  • b
    (merged)
  • b
    ... ... ... ... i love the smell of PRs in the morning 😄
  • b
    wasn't there haxe-ui backends using the java target? java swing or android or something - can't seem to find anything though
  • b
    I'm asking because Haxe dev just got a new .jar file loader, which fixes a whole bunch of issues the old one had: https://github.com/HaxeFoundation/haxe/pull/9608
  • b
    but there might still be some regressions, so it would be good to test some "real-world usages" against it
  • b
    haxeui-android uses hxJava
  • b
    i want it to use jvm, but hit a bug (which has now been fixed) but holding out for a release rather than use a nightly
  • b
    there was an experimental swing backend also (which also used hxJava), but i lost it when i lost my SSD and honestly, imo there is NO reason to use swing
  • b
    i did play with a JavaFx backend too, but decided not to pursue it, not because it was possible (because it defo was) but because i didnt really see a need for it and its just another backend to support
  • b
    > but holding out for a release rather than use a nightly
  • b
    well, the idea is to test it before a release so the bugs can be fixed before then 😄
  • b
    yeah, its a fair point
  • b
    ill probably grab a nightly then and have a play around... dunno when though, probably next week
  • b
    👍
  • b
    the new loader is on by default for jvm if i read the PR correctly, correct?
  • b
    yes
  • b
    Copy code
    Warning : The super class of 'MyTest2' does not match the root node of 'assets/custom/test1.xml' (haxe.ui.containers.HBox != haxe.ui.containers.VBox) - this may have unintended consequences
  • b
    😉
  • b
    not sure if the warning is clear... i think it is
  • b
    i wonder if an error is better? 🤔
  • b
    ... sweet, no more wrapper components in custom components!
  • b
    looks to work just fine...
  • b
    now time to just sit back and see how ive broken everyones code! 😄 not that people seem to use custom components anyway it seems
  • c
    lol
  • f
    I'd implement a colour selector as a custom component, right?
  • f
    It'd be mostly Kha based code, how would that work? I need to show a render texture and grab haxe UI's events
  • b
    good question
1...291292293...1687Latest