https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    tables not working?
  • l
  • c
    how to prevent editing the fields of a treeview while still allowing interaction with it
  • b
    oh, is native treeview editable by default??
  • b
    so it is
  • b
    alright, fixed, latest haxeui-hxwidgets and hxWidgets (since i needed to add the vetoable NotifyEvent)
  • a
    lmao i just realised something
  • a
    Copy code
    hx
case MouseEvent.MOUSE_UP:
  if (mapping.exists(MouseEvent.MOUSE_UP) == false) { ... }
  • a
    you unlink the listeners immediately right?
  • a
    these probably should be 
    once
    as well
  • a
    I have them all set to 
    on
    😂
  • b
    no, you dont unlink listeners immediately - there is "unmapEvent" for that... the component will tell you when its done listening to a, for example, mouse up event
  • a
    ah okay
  • b
    so i think you are fine there... it was just the calllaterimpl that was borked
  • a
    have you considered making 
    haxeui-textinput
    and using your own input across all the composites?
  • a
    is that difficult to setup in a cross lib way
  • a
    it might stand the best chance at improvements as it is hitting a wide userbase
  • b
    its not impossible, but its not the simplest thing to do either... i dont think you need many font type functions to do it, but its more effort than zero 🙂
  • m
    If you do make haxeui-textinput, please do it before I start looking creating my own, lol.
  • m
    It looks like lime has built in font rendering support so I'm going to dig in there and see if I can get it to work, but I'll have to borrow the rest from somewhere.
  • a
    i may explore the concept a bit myself, but, not that far into my backend just yet
  • m
    Oh I don't even have anything drawing yet, and definitely not text let alone input.
  • a
    cause what i'm thinking is essentially having the rendering done by a label + box
  • a
    which would be handled by the backend implementation
  • a
    then all the behaviours would be universal
  • b
    heres a fairly functional one for kha, but to have it "universal" it would have to follow some type of abstraction / interface and thats not going to happen for a while (at least not by me 🙂 ): https://github.com/haxeui/haxeui-kha/blob/master/haxe/ui/backend/kha/TextField.hx
  • a
    i may explore custom components in the near future then, and maybe see if i can employ my idea as a backend agnostic textbox
  • a
    but still got more backend stuff to do 😄
  • m
    Thanks for that, it will be helpful
  • b
    @ambitious-knife-25690 The text input api provided by Ceramic should be helpful for haxe-ui integration, spent a lot of time on that specific feature to make it very similar to what you would have with a standard text input in web
1...141914201421...1687Latest