https://linen.dev logo
Powered by
# haxe-ui
  • d
    I could also help implement that too
  • b
    not sure ive tried other fonts with flixel to be honest
  • b
    ok, think thats working fine
  • b
    git version of core and haxeui-flixel...
  • b
    ... ... right, im done for now 😴
  • b
    (custom fonts seemed to work)
  • b
    button labels need an offset, but its easy with a bit of css
  • d
    thank you 🙂
  • m
    @User - Is there a way to change the value of a slider programatically without triggering it's onChange callback? - The slider's handle in flixel-backend doesn't follow the "blue bar" when the value changes programatically (ex: frameRateSlider.value = animation.frameRate;) - The slider's handle in flixel-backend also doesn't follow the blue bar when you move your mouse to fast out of the app window. (The blue bar works correctly though)
  • b
    ill take a look at the slider stuff later this eve
  • m
    In relation to the first topic, I think I should be using some sort of binding engine... I think you mentioned something before. Is there any material on that?
  • b
    i still think it will trigger onChange
  • b
    why wouldnt you want an onChange?
  • b
    i mean, from the controls perspective wrt dispatching a change event it doesnt care if its user interaction or via code
  • m
    Maybe I got the usage of the whole thing wrong. I use onChange (triggers through interaction) to update my model. But when I change the model programatically (say by loading a whole new file), I just want to set the state of the UI not really trigger any change events.
  • b
    would it though? If the value does change you should only get a single change event
  • b
    ill have to have a play, but i dont see it being an issue
  • b
    somethng like that? Keep in mind its junk just to show what i mean
  • m
    I mean, because I use the events exactly to update the model, but when I update the model programatically I also want to reflect these changes in the UI, but doing so will trigger a new and redundant update to the model
  • b
    wouldnt you guard against that in the model?
  • b
    Copy code
    haxe
    private static function set_value1(value:Float):Float {
        if (_value1 == value) {
            return value;
        }
        
        _value1 = value;
        update();
        return value;
    }
  • b
    (from Model.hx)
  • m
    I could do that, I was just wondering if I was doing something wrong or unexpected
  • m
    I mean, everything is working 🙂
  • b
    the problem there isnt really with haxeui, its the model having that form of update method (which i personally think is fine)... if you do:
    Copy code
    haxe
mySlider.pos = 100;
mySlider.pos = 100;
mySlider.pos = 100;
mySlider.pos = 100;
mySlider.pos = 100;
mySlider.pos = 100;
    You will only get one change event from the slider in haxeui
  • b
    the "issue" is that you want to set the model in a different way (ie, programmatically) and dont want slider to fire event
  • b
    you could pass the view into the update method and exclude that from being updated in your model, you'll probably also need to pass in a control too... all of it gets pretty messy in the model i think... or you could just make the model only update views when a value has actually changed (as above)
  • m
    That later is what I'm doing
  • b
    i think its the correct way to do it... its how i would do it, and its also just the most sensible
  • b
    why would the model try to update the view(s) multiple times if nothing has changed?
1...441442443...1687Latest