https://linen.dev logo
Powered by
# haxe-ui
  • b

    https://community.haxeui.org/uploads/default/original/1X/7adf392931f005fac488f9b457ad0392e3836221.gif▾

  • a
    oh, so it's actually mostly okay except for maybe a component specific issue?
  • b
    yeah, well, at least i got to the item renderers, tried to get all fancy, saw the massive slow down, spent days trying to track it down and rage quit instead 😄
  • a
    😆
  • a
    what is the correct way to extract a value from an item/dropdown?
  • b
    you could just use theme.value... but i guess event.value should have also worked
  • a
    Copy code
    xml
 <section-header text="Theme Test" />
<hbox>
<dropdown text="Select Theme" id="theme">
  <data>
    <item text="Light" value="0"/>
    <item text="Dark" value="1" />
  </data>
  </dropdown>
</hbox>
  • b
    i think thats a relatively new addition, so maybe i missed that one
  • a
    ahh alright
  • b
    theme.value btw will be the index of the selected item... if you wanted the data you are probably better of with theme.selectedItem anyway
  • b
    i think thats right anyway, checking
  • b
    oh, no actually, im wrong... theme.value is theme.selectedItem
  • b
    isnt that ambigious ?
  • b
    in what sense? .value is a shortcut that varies depending on component, one which is essential for item renderers
  • b
    i guess technically i could do away with selectedItem (or .pos, or .text) and just have .value
  • b
    this is fixed now in latest... .value should work as expected
  • b
    so with literally about 10 lines of java / xml its easy to get haxeui-html on android in a webview
  • b
    so ill probably pursue this at some point as its really simple...
  • b
    im honestly not that huge a fan of it though, since it defo doesnt feel native, defo feels like a webpage in an app... nothing some theme tweaking wouldnt fix, but i still prefer 100% native on mobiles, for sure
  • a
    is value meant to return an object, rather than the value property?
  • a
    I would expect 
    event.value
    to return 
    1
  • a
    but i'm not sure if that's "too much" html/js thinking
  • a
    selectedItem
    has value because it holds the active state which I think most people would probably have in their code base anyway
  • b
    it returns and object, which is basically the item data
  • b
    eg:
    Copy code
    xml
<dropdown text="Select Theme" id="theme">
  <data>
    <item text="Light" value="0" something="bob" foo="bar"/>
  </data>
</dropdown>
  • b
    another eg:
    Copy code
    xml
<dropdown text="Select Theme" id="theme" onchange="haxe.ui.Toolkit.theme = this.selectedItem.themeName">
  <data>
    <item text="Light" themeName="default"/>
    <item text="Dark" themeName="dark"/>
  </data>
</dropdown>
  • a
    the api suggests that I would get the 
    value
    property rather than the component data object, it's fine, but not "expected" and was making sure
  • a
    using any of these functions would cause an error as it can't cast an object to any of these types
  • a
    this is a neat thing i wouldn't have guessed be possible
  • a
    for the most part tho i was just seeing if i could figure out a way to do it in the way that felt the most intuitive
1...108610871088...1687Latest