https://linen.dev logo
Powered by
# haxe-ui
  • b
    obviously a wip, "action plans" will need something thinking out, but working ok i think
  • b
    Is this action manager after an alternative to onChange? So then rather addEventListener('onChange', callback())?
  • b
    no no, its an automatic (alternate) way to navigate the UI based on "action input sources" (keyboard, gamepads, remotes, etc)
  • b
    oh okay xD
  • b
    onChange would be called as usual, same with on click etc, its just you can do those things with different "action sources"
  • b
    a callback manager would also be really handy. Maybe I'll see if I make something in the days which then but also does not break with the old code.
  • b
    what would a callback manager do?
  • b
    i mean, what problem does it solve?
  • b
    just allow multiple callbacks like javascript
  • b
    im not sure i follow
  • b
    you mean like have two click callbacks on the same button?
  • b
    yes
  • b
    you can already do that
  • b
    .registerEvent(MouseEvent.CLICK, ...)
  • b
    the 
    .onClick
    is shortcut, and yeah, that will overwrite any previous listener
  • b
    oh! OOHHHH! xD
  • b
    but if you call registerEvent 10 times, then clicking the button will call the listener 10 times
  • b
    then I do not need to do anything more xD Then you have already build in there.
  • b
    but I noticed something else. you are currently using strings. It is somehow impractical. I have seen somewhere a sysntax which allows to know then also like the callback of it looks.
  • b
    yeah, i want to move them to proper haxe enums at some point... just havent gotten around to it yet
  • b
    using strings does make it much easier to make custom events though
  • b
    but yeah, abstract enums i think should work nicely
  • b
    i was also thinking to move away from the "ALLCAPITALS", but could be a really annoying change for existing users
  • b
    is still a work in progress. But I eh how do you say it? In any case: Good work! :)
  • b
    I always find CamelCase very handy for reading.
  • b
    well, for event types i think 
    MouseEvent.MouseDown
    is nicer than 
    MouseEvent.MOUSE_DOWN
    but im not sure im going to make the change as it could be a real pain for existing apps
  • b
    ASPECIALMOUSEVENTWITHRELATIVECOORDINAGES -> ASpecialMouseEventWithRelativeCoordinates
  • b
    yeah
  • b
    Ah the name is a bit exaggerated xD but a good example that it can be really cruel to read something like that.
  • b
    agreed - i think ill probably change them one day but its like the lower priority thing to me
1...834835836...1687Latest