https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    hmmmm, right... so does "focus = true" work on the textfield? Maybe there will need to be some changes to haxeui-hxwidgets, but i though it was all working
  • b
    also reminds me that a 
    <dropdown editable="true" />
    is a nice addition
  • f
    It doesn't use a haxeui textfield, it's a textentry of a comboBox. But in fact, I don't know even enough of wxwidgets to know how to access to the text entry of a comboBox.
  • b
    oh, so that whole component is a native one, ie, thats how comboboxes look on your OS?
  • f
    yes, in the video, the upper one is a combobox, the other one ( we don't see much) is a choice. As I understand it, only on GTK a combobox and a choice is different, in other oses (windows and mac) they are actually the same. ( I'm on linux KDE plasma now)
  • b
    right, so, my guess is that if the wx component (which is a native component) isnt behaving well, its either a) wx or b) the OS
  • f
    The problem is normally you type and nothing really happens. I'm the one making the filter, and the one showing the popup. But when I show the popup, it steals the focus, and I don't enough about wx Widgets to focus back on the text entry
  • b
    but the whole thing is a self contained wx component right?
  • b
    ie, a 
    wxcombobox
  • f
    Yes. But as I don't know about wxwidgets, I thought maybe there was a way, but maybe not ?
  • b
    not 100% sure, there might be some info here: https://docs.wxwidgets.org/3.0/classwx_combo_box.html
  • b
    but i dont know how to get the textfield part of a combo, or if its even possible
  • f
    Okay, thanks ! So I'll continue to explore another day 🙂 Hopefully it will work
  • b
    it sounds, tbh, that for what you are trying to do, wxcombobox is the wrong control
  • f
    Oh, why ?
  • b
    dunno, feels more like you are trying to create a sort of "auto complete" thing, no?
  • f
    I just want to do what you did for composite. I know there are autocomplete on wxwidgets, there seem easier to use, but I was focused on reflecting the behaviour of your composite dropdown
  • b
    right, i see, so this is basically trying to have a native counter part for a searchable dropdown?
  • f
    exactly
  • b
    maybe combobox is the right choice (still not sure), ill have a play with wx at some point and see how it works / feels
  • f
    BTW, what do you mean by dropdown editable="true" ? 🙂
  • b
    so the idea would be to be able to set "myHaxeUIDropown.ediable = true" and that would, essentially, be a combobox
  • b
    ie, a textfield instead of a label, in fact, i wanted to go one further and allow ItemRenderers to be editable, meaning you get editable listviews / tableviews / treeviews "for free"
  • b
    i think the main difference between a searchable popup list and a combobox is, i think, you can have freetext in a combo...
  • b
    ie, the value doesnt have to be one of the options
  • b
    (i could be wrong about that, but if i am, i dont really see the point in a combobox in general)
  • f
    You're not wrong. The value doen't have to be an option ( which enable to have a placeholder text ! 🙂 ) but if you want non editable (by user) value, it has has to be an option...
  • b
    yeah, so i think the concept of "editable item renderers" could work out quite nicely, just need to think about how best to implement them
  • b
    it could add alot of flexibility to things, i often have to roll out my own systems for things, like renaming nodes in a treeview (like in the builder)...
  • b
    they arent complicated to do, but its defo alot more effort that just going ".editable=true"
1...134513461347...1687Latest