https://linen.dev logo
Powered by
# haxe-ui
  • s
    :grief:
  • b
    good find though 😉
  • s
    that's weird because of how the base stays in the right place
  • b
    well, the static texts are flxtext's, the inputs are openfl textfields "floating" over the top of the UI (its a shitty solution but the best that flixel can offer at the moment)
  • b
    so it makes sense that the out of place parts (the openfl textfields) arent lining up since technically, they arent anything to do with flixel
  • s
    I didn't know that fullscreen messed stuff up
  • s
    lmao
  • s
    that's really weird
  • b
    well, its not messing it up really, its just that flixel has scaled everything by, lets say, 2
  • b
    but since the floating openfl textfields arent anything to do with flixel it doesnt touch them (or even know about them)
  • b
    so they remain at the position when the scale was 1
  • b
    that my assumption anyway, but pretty sure that'll be it
  • s
    why don't you use the flixel ui ?
  • b
    for what?
  • s
    for your ui? it has a working text field that you can look at
  • b
    flixel ui doesnt make sense with haxeui... i could write a haxeui backend that would use flixel-ui, but that also doesnt really make much sense (in the terms of haxeui)
  • b
    i could copy and paste the flixel-ui textfield... and we discussed it a while ago but its very limited and doesnt support multiline text input
  • s
    ... so is there no real fix? you said it's the best flixel can offer
  • b
    for text input, yeah, the best at the moment is to use openfls textfield... im not saying btw that your issue cant be fixed... its a bug, and ill fix it
  • b
    another option, which i dont have time for at the moment, is to adapt haxeui-khas textfield to haxeui-flixel
  • b
    but its also not as feature rich as openfls, but it would integrate better with flixel itself
  • s
    aren't text fields and text areas different?
  • s
    only text area is multiline
  • b
    so there is flixel-uis textfield, which is a no go because its single line input only (but does integrate nicely), openfls textfield which doesnt integrate nicely but is feature rich and an adoption of haxeui-khas textinput which would be kinda middle ground (but would natively integrate into flixel)
  • b
    they are different components yeah, but the "thing" that backs it usually is the same (though it doesnt have to be)
  • s
    kha sounds like the best for text area. if you had the time to differentiate text area and text field flixel ui would be good for textfield
  • b
    yeah, what might be the best path is to use all of them and allow the user to select with a define... so 
    -D haxeui-flixel-use-openfl-textinput
  • s
    sounds good
  • b
    but at the moment a) there is only openfl text input, so the define doesnt make sense and b) regardless, the bug you have found is a bug and should (will) be fixed
  • s
    ok
1...623624625...1687Latest