https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    well, i just mean, you should be able to access the java apis directly from haxe, no go between, its what haxeui-android does to build the native api
  • c
    That sounds promising
  • r
    @cool-musician-79004 Are you making a vim phone 😆
  • c
    Hahaha, no, I want to make a camera app focused on organization rather than image quality
  • c
    I am tired of ha in my gallery full of useless pictures that I only don't see when I look for them
  • r
    Is there a way of detecting when "enter" was pressed in a TextField component?
  • h
    So I have test case for the later thing I found, that is, removing the class that defines 
    pointer-events:none
    does not restore pointer-event processing. I see this on HL but it happens here too. I can workaround it by adding an explicit style that add 
    pointer-events:all
    . I don't know if that's expected but it seems a bit asymmetrical as the blur happily comes and goes with the class add/remove. Here's the test case . Click the Disable/Enable button on the right and it will blur/disable events on the left side.
  • h
    Also, as far as I can tell on openfl the 
    pointer-events:none
    doesn't work. It happens on HL and HTML5. The blur happens and in the same block of CSS I have the pointer-events thing but it is not effective. I haven't yet run my small test case in openfl specifically but that's basically what I'm doing in my app.
  • b
    i think you have to use the good old fashioned onKeyPress and then check the event code for 13... it would be nice to have some type of "onDefault" or something like that (would be nice for forms / dialogs too)
  • b
    ill check it out when i get a moment - thanks for the repro
  • f
    offtopic but, the way haxeui xml works is that it's compiled to haxe via a macro right?
  • f
    essentially making the xml into a DSL for haxeui
  • f
    looks through code
  • f
    ah I see using the actual xml parser but then building things in a macro context?
  • f
    ah oh no, haxe 3 workarounds
  • b
    so what happens is the xml gets parsed into this sort of "interim" format (bunch of classes, etc), this then gets turned into haxe code via macros yeah, its why technically it doesnt have to be xml. Json, yaml, something custom is also more than possible, in fact, originally there were parsers for yaml and json... but i removed them because, when it was all in its infancy, i wasnt keeping them up to date - arguably now i could reintroduce them since i rarely touch that stuff but im not sure its worth it
  • f
    nah xml is fine for UI I think
  • f
    but I was looking through the code for how it's done because I might want to use a similar approach for compiling game scripts to haxe code
  • f
    providing I write a parser that can make something looking like an AST
  • f
    right now I'm just using buttloads of reflection at runtime
  • f
    butt yeah I've currently still only got haxe 3 working since the lime-switch runtime hasn't been updated past 7.2.1 yet so... maybe I gotta port lime 8 first.
  • b
    > still only got haxe 3 working since the lime-switch interesting, i was considering dropping haxe3 support... sounds like that wouldnt have been a good move
  • b
    > but I was looking through the code for how it's done because I might want to use a similar approach for compiling game scripts to haxe code it depends how complex it needs to be really, but at a base level, its pretty easy to turn "anything" into haxe code at compile time
  • f
    I mean, I wouldn't blame you - I'd just have to use an older version until I can figure out how to get lime 8 running
  • f
    I did do some work on it, but for some reason the switch just shows a black (maybe dark grey?) screen (however I can hear the Pirate Pig music playing and it hasn't "crashed" according to the debugger)
  • f
    that being said, it never seems to initialise OpenGL either so IDK why it isn't exploding
  • f
    I feel like /something/ should crash/throw in that case
  • f
    anywho
  • f
    project for another time - unfortunately day job doesn't have me working on haxe (yet...........)
  • b
    well, there is no technical reason to drop haxe3 support tbh... i mean, it just catches me out every now and then with things i didnt realise were haxe4 only (Array::contains for example)
1...136513661367...1687Latest