https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    but presumably if (when) haxeui-flixel incorporates more naturally into flixel the issue would remain
  • b
    ie, at the moment, without haxeui, a substate doesnt pause?
  • q
    Well, it doesn't set 
    active
    to false for the parent state, which had been the expectation many of my premises were based on. Why I'm too stupid to check such things is beyond me. šŸ¤¦ Anyway, what it does do is if you check the logic, only the substate really seems to get updated while it's open, while the parent just kinda sits there doing a lot of nothing. It's written so that it checks to see if there's a substate and then... if substate - update substate... if not substate, update self. Well, something like that, anyway. I'm not quite awake yet, and a maintainer could give much better than I could just glancing at it.
  • q
    But I mean, that logic is pretty straightforward I think, especially if I can understand it and usually under the hood is as good as german to me.
  • q
    ( No offense to any German friends about. )
  • b
    right, so that makes sense also, the parent doesnt explicitly deactivate itself, but simply stops updating itself.
  • q
    Right.
  • q
    Or at least, that's how it looks.
  • b
    gotcha
  • q
    Ian, I'm not trying to be difficult, I'm just afraid of being wrong.
  • b
    didnt think you were trying to be difficult... its good insight, and more than i have about anything in the flixel realm
  • q
    Okay. I think looking at it cleanup is clean for substates.
  • q
    The conditional worth interest for "do we want parent doing things right now?" seems to be:
    Copy code
    haxe
if (persistentUpdate || subState == null)
    for the state itself. You can find this on line 171 in FlxState, as part of its logic for handling update checking around substates. Specific implementation from that note I don't know. But it appears that properly setting substates to null when they're closed is going on, and that would mean that check is the one we're interested in here.
  • q
    blah word salad a bit, sorry.
  • q
    ... I went ahead and threw what may be useful of those notes into an edit of issue 17 on the tracker.
  • b
    I thought about it
  • b
    Flixel doesnā€™t give any good way to do it
  • b
    I donā€™t want to get into some recursive ā€œfind all objects that are children of the current stateā€ every single frame of mouse handling
  • b
    So I need to think if the HaxeUI side gives me something useful
  • q
    I looked at it, too, trying to find a workaround.
  • q
    As you might imagine, I didn't find anything too clever šŸ˜¦
  • q
    Ideally haxeui would have a cutoff switch for event handling in a container (and its children) that "just works". Then we could leverage that pretty cheaply.
  • q
    I hesitate to suggest that strongly enough to request it - I don't know how badly that would break or complicate haxeui's core.
  • q
    There is something I'm puzzled about. If haxeui objects are normal backend objects, why are they not obeying flixel's update cycle? Does haxeui's toolkit maintain its own update thread alongside flixel?
  • q
    In the meantime... šŸ˜¦
  • q
    Copy code
    haxe
    public function onClick_faq(ignored:UIEvent):Void
    {
        FlxG.log.add(this.doHxui);
        
        if (this.doHxui)
        {
            FlxG.log.add("Oops I did it again!");
            var faqSubstate:FAQSubstate = new FAQSubstate(0x80000000);
            openSubState(faqSubstate);
        }
    }
  • q
    and...
  • q
    Copy code
    haxe
class FlxHaxeUiState extends FlxState
{
    /**
     * Whether or not we should be doing Haxeui things.
     * 
     * It's expected this will be checked manually.
     */
    public var doHxui:Bool = true;

    override public function create():Void
    {
        // cut for brevity
    }

    override function openSubState(SubState:FlxSubState)
    {
        this.doHxui = false;
        super.openSubState(SubState);
    }

    override function closeSubState() 
    {
        this.doHxui = true;
        super.closeSubState();
    }
}
  • q
    I don't know if it works for haxeui-based substates and I don't want the struggle.
  • q
    But it seems to work okay for non-haxeui substates.
1...737475...1687Latest