https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    hmmm
  • b
    ill have to fire up the VM at some point
  • f
    ( just checked I have wx 3.2.1)
  • b
    im on 3.3.0
  • b
    and on my VMs im on git latest
  • b
    well, latest from a while ago
  • e
    "latest" isnt a version 🤓
  • b
    well, to find the sha, id have to start up the vm 😉
  • b
    i would consider git version of wx...
  • b
    i think 3.2.1 is pretty old and ive had all types of issues in the past with even release versions of wx on mac / linux
  • b
    3.2.1 is from sep, so not old at all
  • f
    ??? Do you mean 3.3.0 ?
  • b
    well, 3.3.0 is technically the git version, ive just looked on GH and 3.2.1 is the latest release, and its like 3 months old, so i doubt it super outdated
  • b
    you might want to try a repro with just hxWidgets (ie, no haxeui)
  • f
    Yeah It was the last released version when I downloaded a few days ago
  • b
    yeah, i doubt you need to go to git... i dont remember what version i had, but it was years ago, and certainly not "3 months old"
  • f
    Okay I'm going to do a break on debugging for today, but I plan to try with only hxWidgets
  • f
    I've noticed that toggled buttons don't dispatch nor click nor change events. It seems quite easy to correct ( by dispatching an event in the button handler ) , but I have a question, should a toggle button dispatch only a change event or also a click event ( it won't make any differences in hxWidgets) ? Html5 does both, I think
  • b
    so, technically change is for toggle, click is for non-toggle... especially when talking about native (totally different events in wx)... that said, it might make sense to unify them, even on native as i think it is valid for a toggle to dispatch a click
  • b
    however, you are saying its dispatching neither on native, correct?
  • f
    indeed, neither one work on native.
  • b
    wow... you are right 😮
  • b
    i wonder if i broke this very recently with my last change, or i just dont use toggles enough
  • b
    (wasnt the last change)
  • f
    Yeah I didn't notice it even checking after you last change ( it was a part of the app where it was kind of used as parameters, so it didn't need to fire any change instantly)
  • b
    OK, i think i can see whats happening, not sure when i broke this, but i think its when i changed the way native properties were looked up from the xml
  • b
    in fact, this has been broken for a while... this entry in native.xml is no longer valid (ie, unused):
  • b
    Copy code
    haxe
    <component id="haxe.ui.components.Toggle" class="hx.widgets.ToggleButton" allowChildren="false">
        <behaviour id="text" class="haxe.ui.backend.hxwidgets.behaviours.ControlLabel" />
        <behaviour id="value" class="haxe.ui.backend.hxwidgets.behaviours.ControlLabel" />
        <behaviour id="selected" class="haxe.ui.backend.hxwidgets.behaviours.ControlValue" autoDispatch="haxe.ui.events.UIEvent.CHANGE" />
        <behaviour id="icon" class="haxe.ui.backend.hxwidgets.behaviours.ControlBitmap" />
        <behaviour id="disabled" class="haxe.ui.backend.hxwidgets.behaviours.ControlDisable" />
        <behaviour id="toggle" class="haxe.ui.behaviours.DefaultBehaviour" />
        <behaviour id="tooltip" class="haxe.ui.backend.hxwidgets.behaviours.ToolTipBehaviour" />
        <size class="haxe.ui.backend.hxwidgets.size.BestSize" includePadding="false" />
        <handler class="haxe.ui.backend.hxwidgets.handlers.ReflectionHandler" event="EventType.TOGGLEBUTTON" sourceProp="value" targetProp="selected" />
        <event id="click" native="EventType.BUTTON" class="haxe.ui.events.MouseEvent" />
        <event id="change" native="EventType.TOGGLEBUTTON" class="haxe.ui.events.UIEvent" />
    </component>
  • b
    there is no Toggle component... so obviously adding events to that (as i just tried) makes no sense... 🤦‍♂️
  • f
    Indeed but there is also in the Button component
    Copy code
    xml
<behaviour id="selected" class="haxe.ui.backend.hxwidgets.behaviours.ControlValue" autoDispatch="haxe.ui.events.UIEvent.CHANGE" />
    Maybe it has to do t=with the last change and it doesn't autodispatch a CHANGE anymore ?
1...134813491350...1687Latest