https://linen.dev logo
Powered by
# haxe-ui
  • b
    ok, @:xml metadata working correctly - as suspected, it was something dumb (adding the components twice essentially)
  • d
    > ok, so the issue (well, not issue, but difference) is that you set the w/h of the game, if i set them to the defaults (0) then everything is fine... so basically, it seems that flixel does some scaling /moving and haxeui completely ignores it... ill take a look, any pointers would be useful... @User I played around with it a bit more. It turns out the issue only seems to appear if there is a mismatch between the size defined in 
    Project.xml
    and 
    Main.hx
    . If they match, then everything works as expected.
  • d
    However the hitboxes are not accurate if you change the zoom in any way
  • d
    so it seems to work when the height and width match and zoom is set to 1
  • b
    have you got latest haxeui-flixel from git?
  • h
    > @User - ive added outline filters to haxeui css: @User wow, extremely easy to use, I like them a lot!
  • h
    couldn't resist implementing them in the end?
  • b
    haha, yeah, saw how easy it was it implement and thought "why not"
  • h
    by the way, another one of these useful-to-have-but-not-essential features I'm interested in is having tooltips that display after we hover a component for a couple of seconds, does haxeui already have something like that?
  • b
    nope
  • b
    but on a list 😉
  • b
    id find them useful too
  • h
    they're extremely useful for accessibility in my opinion
  • h
    thanks a lot for working on them, haxeui looks way more solid than what I thought before
  • d
    @User not running the latest from git right now, should I try that? I actually just ended up rescaling everything so I can use a zoom of 1. Seems to be a sufficient workaround for now
  • b
    yeah, thats one option, but git version has some fixes in it, now your example should run fine... date dropdown is still screwy but its just a style issue
  • d
    is it possible to control the direction of a dropdown menu? e.g. make the expanded list go up instead of down?
  • b
    should happen automatically if there isnt enough space for the list to display downward
  • b
    havent tried that on flixel though to be fair
  • d
    Doesn't seem to automatically do it with flixel. Any way to do it manually?
  • b
    not manually, nope... though might not be a bad idea to add it... any chance for a project sample? It should work automatically regardless
  • d
    this is interesting...it works if you have a static number of things in the data list. But if you dynamically update it (and start it empty) then it defaults to down and doesn't adjust if you later change 
    dataSource
  • b
    sounds like possibly a core bug then
  • d
    or at least I think that's the behavior I'm seeing, but I'll play around a bit more to confirm
  • d
    oops
  • d
    I think it's my fault - I was improperly setting dropdownHeight
  • d
    apologies for the false alarm
  • b
    improperly in what sense? Still doesnt sound like it should happen
  • d
    I was setting it to the height and width of the box - which if the dropdownHeight is meant to represent the height of the dropdown with the items, would be making the height within the screen
  • b
    If I have a custom/extended OpenFL TextField, what’s a good way of integrating it? If it’s a custom component or something, is there an example on the site?
1...414415416...1687Latest