https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    with the shallow clones that lix does you can also revert to older states
  • b
    as long as nobody takes down the project from GitHub / whereever it's hosted
  • u
    oh ok; good to know
  • r
    not sure it is the case with per-project installation, but when installed globally, the lix clones/version are shared between projects so it saves space
  • b
    it is the case for both local and global installations
  • r
    oh nice ! will try the local install workflow then..
  • b
    FYI I’m working on updating the flixel backend, but it turns out writing a new base class is not easy
  • b
    I’m a bit stuck between FlxSprite and Kha implementations of applying styles...
  • o
    Lix should not depend on Node, it's really feasible to change this.
  • b
    FlxSprite has a bitmap that effects would go onto, Kha uses renderTo to redraw/reapply styles each time
  • o
    What do you mean by styles I know Kha and flash but not fixel
  • b
    HaxeUI styles
  • o
    If your looking at a fixel target suspect you have to look deeper into lime/openfl
  • o
    I browsed HaxeUI to see how I could implement it with trilateral
  • o
    I think maybe the styles abstraction needs some thought it did not at the time seem suitable to abstract over.
  • o
    Have you got something working in Both yet?
  • b
    I have a working flixel backend, I just need to update it to be cleaner and integrate better
  • o
    Does it need Fixel could it be implemented for any OpenFL or NME project?
  • o
    I mean add Fixel abilities over but does it actually need fixel just to work?
  • b
    There’s a backend for every target
  • b
    The one I’m talking about is specifically for flixel
  • b
    @bright-gpu-74537 does the kha backend’s 
    renderTo
    get called every frame?
  • b
    As in, it’s redrawing the entire UI every frame?
  • b
    Ultimately I’m wondering if my flixel class should have a bitmapdata backing it (like FlxSprite) or if it should draw to the flixel camera directly
  • w
    Woo event bubbling problems: I have an event on a "root" component for mousedown. Some of it's children also have mousedown events; and these all work as I would expect. HOWEVER, I have input fields, which seem to pass the mouse events down to the root. If I catch them in a parent (ie, a component that contains the input field, but is a child of the root) and cancel the event, the input field stops working as expected.
  • w
    I tried setting bubble=false but this doesn't appear to do anything.
  • w
    What's the "correct" way to fix this, such that any unhandled mousedown events in the container don't get passed down to the root?
  • w
    I also tried adding a check to the "root" to check that target == this, but that always passes
  • w
    Fixed it. Sorta. I'm using the html5 target, which exposes 
    _originalEvent
    , which means I can just do 
    event._originalEvent.stopPropagation();
    which does the correct thing. 
    event.cancel()
    does this, but also calls 
    preventDefault()
    which causes the aforementioned problem with input fields.
  • b
    @wooden-horse-84574 - thats interesting, care to open a PR or an issue? 🙂
1...119120121...1687Latest