https://linen.dev logo
Powered by
# haxe-ui
  • m
    i had no idea, in my head it would trigger all the time 🙂
  • b
    the issue, im farly sure is, in one handler you are doing some manipulation to change the value to something, and then in the other handler you are doing a different manipulation, so it the value is different, which means you are going to be bouncing back and forth between the handlers
  • b
    its like doing something like:
    Copy code
    haxe
slider1.onChange = function(_) slider2.value = slider1.value + 1;
slider2.onChange = function(_) slider1.value = slider2.value + 1;
  • b
    thats gonna bounce back and forth between because the values are different (until it gets to the max in this case)
  • m
    Yeah, I completely overlooked that, because I thought it wouldn't matter if the onChange event is called regardless of the value being the same
  • b
    you'll need to make sure that whatever maths you use to set the values, will lead to the same results otherwise change is just going to be refired over and over again...
  • b
    personally, i wouldnt do any maths if possible and leave it all up to SPColor, that way you know its gonna be the same every time
  • b
    btw im late to the party, but 
    Reflect.setField
    sets a property without calling thier setter
  • m
    @bright-gpu-74537 probably is that situation that I've talked with you about, regarding the menus that doesn't have submenus, they re-render like a button. @best-agent-85158 does the Edit and View , have submenus (subitems)?
  • b
    nope
  • b
    @most-caravan-45834 if you do
  • b
    ah
  • b
    Copy code
    haxe
Reflect.setField(slider.pos, 20);
    then 
    onChange
    wont get called
  • b
    the point though is that you shouldnt need to do anything like this
  • b
    if a textfield is linked to a slider (and vice versa) and the values are being set are the same, then you arent going to get into a loop, if you are setting them different, then yeah, its going to be a loop, which is "normal", again, its like doing:
    Copy code
    haxe
slider1.onChange = function(_) slider2.value = slider1.value + 1;
slider2.onChange = function(_) slider1.value = slider2.value + 1;
  • m
    I see you are using tooltip, and I have a tip/suggestion that I don't know if you are aware of, and that is the haxeui localisation/internationalisation subsystem. I use it in my project and it's really nice integrated in haxeui. https://community.haxeui.org/t/haxeui-v1-2-released/318
  • b
    yup, thats the issue
  • b
    OK, fixed in git core ( @magnificent-crayon-8615 / @best-agent-85158 )
  • b
    it seems very hard to get used to. ill do that near the release of the app, otherwise id get very confused...
  • m
    Actually I believe it to be easier to use than other solutions, probably not fully featured, but has all the essential localisation features, my project is localised to 6 languages and I didn't feel the need to use anything else, but that's only my opinion, ofc
  • b
    what is the default background color for darkmode
  • b
    ?
  • m
    and I know that you don't use xml, but it also integrates very well with it, all you need is to use the 
    {{the_localised_tag}}
    , actually, you can also use it in code very easily 
    button.tooltip = "{{the_localised_tag}}"
  • b
  • b
    speaking of locales, ive added formats now 🙂 https://github.com/haxeui/haxeui-core/tree/master/haxe/ui/_module/locale/en
  • b
    only decimal separator and short date currently, but the "system" is there which nice
  • b
    eg (from number-stepper):
    Copy code
    @:clonable @:behaviour(DefaultBehaviour, Formats.decimalSeperator)  public var decimalSeparator:String;
  • m
    👌 the std-strings, I use it already (Dialog buttons), but nice addition (formats)
  • b
    i have to say, seeing my documentation on haxeui is pretty wierd 🥴
  • b
    heh heh
1...109510961097...1687Latest