https://linen.dev logo
Powered by
# haxe-ui
  • f
    (but it won't work on autosized components of course)
  • b
    doesnt 
    .width
    work in those cases?
  • b
    ... or any case really i guess...
  • f
    I don't think so, why would I have done so complicated then ? 😛 I think if i did that, it was because maybe width gave the old value, or maybe it ave up an incorrect value, it was when testing on anadroid with a high quality screen. Or maybe I forgot to try ...
  • b
    hmmm, fair enough... ill have a play tomorrow and see if i get similar results... but width (or maybe componentWidth, which i guess should be called measuredWidth) should give decent results... otherwise the layout(s) wouldnt work
  • m
    I've used
    Copy code
    haxe
this.registerEvent(UIEvent.RESIZE, e -> _delegate.onContainerResized());
  • m
    But when I read the this.width I get the value before resizing, just as I did with openFL resize event 😦
  • m
    Is there a way to get the new value?
  • b
    sounds like a bug, the same on maybe that yoplala is talking about, ill have to try and repro and check it out
  • b
    maybe the resize event is firing too early
  • b
    if you did, for example:
    Copy code
    haxe
this.registerEvent(UIEvent.RESIZE, e -> {
    Toolkit.callLater(function() {
        _delegate.onContainerResized()
    });
});
    Would that give the right value?
  • b
    im guessing it would, note this is a workaround, not a solution
  • m
    well at least it's consistent with openfl
  • m
    let me check
  • m
    Yeap, it does work
  • m
    Will use it for now
  • b
    yeah, ill take a look, feels like the event is firing before anything has actually been resized, ie, its firing when you request a resize and the invalidation queue hasnt kicked in yet
  • b
    i mean more like a real combobox ... an input text field that can autocomplete, take the value from a dropdown, or take the value entered by the user (ie. not corresponding to any predefined value) similar implementaions in html/jquery are select2/select3/selectivity.js widgets for example another real world example is a browsers url-bar widget and the combo-box is one of the most useful widgets for data-management, especial repetitive tasks that still need to happen manually
  • b
    is a comobox useful? I hate them personally, and i dont think have ever needed them
  • b
    im obviously willing to be convinced and add them ofc, i mean, just because i dont use them, doesnt mean they arent useful 🙂
  • r
    In a non-haxe project, I make fairly extensive use of them
  • r
    there are a lot of situations where an input might have a ton of options or very few, and the combobox straddles the convenience of click-to-select and the practicality of type-to-select
  • r
    Maybe a stupid question with an obvious answer but, why is the default value of width and height (It seems) 0?
  • r
    I feel like a spend a lot of time writing width="100%" and/or height="100%" because if I'm not specifying a size, I probably want it to take up its whole container
  • r
    but I can't really think of any situation where I'd want a zero-size element
  • a
    0 probably represents "inherit"
  • a
    so, size to the contents
  • b
    that may be accurate for you, but its certainly not a general fact, usually for example, i want my components to autosize (ie, size based on the size of the children)
  • b
    defaulting to 100% is certainly not a good idea
  • b
    btw, if you really want that, you could do:
    Copy code
    css
* {
    width: 100%:
}
    But i think you'll find quickly why you dont want to do that 🙂
1...108810891090...1687Latest