https://linen.dev logo
Powered by
# haxe-ui
  • u
    And then moving that single sprite moves the rest of the group
  • b
    yeah, haxeui uses an FlxGroup with some added stuff to have children
  • b
    FlxSpriteGroup
  • b
    so yeah, all seemed fine... no thills ofc
  • b
    Copy code
    xml
    <vbox id="testBox" width="200">
        <frame text="Drag me!" width="100%">
            <vbox width="100%">
                <hbox width="100%">
                    <button text="Button" width="50%" />
                    <button text="Button" width="50%" />
                </hbox>
                <vbox width="100%">
                    <button text="Button" width="100%" />
                    <button text="Button" width="100%" />
                    <button text="Button" width="100%" />
                </vbox>
                <hbox width="100%">
                    <button text="Button" width="33%" />
                    <button text="Button" width="34%" />
                    <button text="Button" width="33%" />
                </hbox>
            </vbox>    
        </frame>
    </vbox>
  • b
    Copy code
    haxe
            _testBox = mainView.findComponent("testBox", Box);
            _testBox.registerEvent(MouseEvent.MOUSE_DOWN, onMouseDown);

...
...
...


    private static var _offset:Point = null;
    private static function onMouseDown(e:MouseEvent) {
        _offset = new Point(e.screenX - _testBox.screenLeft, e.screenY - _testBox.screenTop);
        Screen.instance.registerEvent(MouseEvent.MOUSE_MOVE, onScreenMouseMove);
        Screen.instance.registerEvent(MouseEvent.MOUSE_UP, onScreenMouseUp);
    }
    
    private static function onScreenMouseMove(e:MouseEvent) {
        var x = e.screenX - _offset.x;
        var y = e.screenY - _offset.y;
        _testBox.left = x;
        _testBox.top = y;
    }
    
    private static function onScreenMouseUp(e:MouseEvent) {
        _offset = null;
        Screen.instance.unregisterEvent(MouseEvent.MOUSE_MOVE, onScreenMouseMove);
        Screen.instance.unregisterEvent(MouseEvent.MOUSE_UP, onScreenMouseUp);
    }
  • b
    obviously a real drag system inside haxeui-core would certainly be a little more clever but thats the basic concept i was talking about above
  • h
    @User do you know how flixel's layering works? If I display `FlxSprite`s after adding the interface my interface gets hidden and I don't want that
  • b
    are you saying if you add a 100x100 sprite after you add a 100x100 haxeui component then the component gets hidden?
  • a
    > @User do you know how flixel's layering works? If I display `FlxSprite`s after adding the interface my interface gets hidden and I don't want that @User you can achieve something like a layer system by using FlxTypedGroup
  • a
    Copy code
    var levelSprites:FlxTypedgroup<FlxSprite>;
var entitySprites:FlxTypedgroup<FlxSprite>;
var ui:FlxTypedGroup<WhateverTheHaxeUiComponentTypeIs>;
  • a
    for example, a layer for level sprites, entities and the UI`
  • h
    @User here you go
  • a
    only add relevent objects to each group and they will be stacked in the order you add the group to the FlxState
  • b
    but i dont see why it would even happen if the first place, i mean, why would the haxeui component (which is essentially just a sprite group) be hidden in the first place
  • b
    ok, so thats weird behaviour
  • h
    still clickable, the white boxes are FlxSprite
  • a
    oh the haxui component is already a group, I guess just make sure it's the last thing added to FlxState and keep your other sprites in another group added earlier?
  • b
    but it does kinda make sense though now i think about it... you are indeed adding a sprite over another sprite
  • h
    @User do you think that every time I generate the world I should re generate the interface after?
  • b
    i wonder what the best way to handle this is... how do you say in flixel "render this last"... like a z-order type thing
  • h
    you usually just add it last in the create() method
  • a
    > @User do you think that every time I generate the world I should re generate the interface after? @User probably don't need to, if you have separate groups
  • a
    adding the level sprites to a group instead of the FlxState directly should be enough
  • h
    they are already part of a FlxGroup
  • h
    the entities too
  • h
    they need to be for collision checking, however they aren't inside FlxTypedGroups, don't know if that's an issue
  • b
    so looking briefly online it seems what halfwheat is saying is the best practice
  • b
    > You can make use of FlxGroup objects to control the drawing order. > > For example, create and add a flxgroup to the state and after that add the hud (to the state too). > Then, instead of adding your game objects directly to the state, add them to the flxgroup, that way they will be drawn before the hud.
  • a
    > they need to be for collision checking, however they aren't inside FlxTypedGroups, don't know if that's an issue @User shoud not matter
1...388389390...1687Latest