https://linen.dev logo
Powered by
# haxe-ui
  • l
    if not, here's minimal demonstrating weird behavior:
    Copy code
    haxe
package;

import haxe.ui.core.Screen;
import haxe.ui.events.UIEvent;
import hxd.App;

import haxe.ui.Toolkit;
import haxe.ui.containers.dialogs.Dialog;
import haxe.ui.components.Button;

class Main extends App
{
    
    static function main() 
    {
        new Main();
    }
    
    public function new()
    {
        super();
    }
    
    var dialog:Dialog;
    var closeMe:Button;
    var openMe:Button;
    
    override function init():Void 
    {
        super.init();
        
        Toolkit.init({
            root : s2d
        });
        
        openMe = new Button();
        openMe.text = "Open me!";
        Screen.instance.addComponent(openMe);
        openMe.onClick = function(e:UIEvent)
        {
            dialog = new Dialog();
            dialog.width = dialog.height = 200;
            
            Screen.instance.addComponent(dialog);
            dialog.addComponent(closeMe);
            
            openMe.visible = false;
        }
        
        
        
        closeMe = new Button();
        closeMe.text = "Close Me!";
        closeMe.onClick = function(e:UIEvent)
        {
            dialog.hideDialog(DialogButton.OK);
            openMe.visible = true;
        }
        
    }
}
  • l
    I'm having issues recreating the specific error, but fiddling around got me several other errors though
  • l
    in this example, the "close me" button doesn't get added to dialog box on the second time it gets declared.
  • b
    only just saw this, ill check it out tomorrow
  • b
    so im not entirely sure what the code above is trying to do... it feels like a kinda weird way to go about things (but maybe its just for illustrative purposes?), but if the issue is as to why the "Close Me!" button doesnt appear twice its because it gets destroyed when the dialog is closed after the first call and is then never created again
  • b
    you could make it work by creating the Dialog once (ie, not a 
    new Dialog()
    in the handler and setting its 
    .destroyOnClose
    to false
  • b
    ie:
  • b
    Copy code
    haxe
            if (dialog == null) {
                dialog = new Dialog();
                dialog.destroyOnClose = false;
            }
  • b
    you still have kinda weird issue where you are adding the "closeMe" button to the dialog over and over again, but you could fix that by not adding it if its already there... it makes me wonder if haxeui should do that btw... ie, if you add the same button twice to the same container it just wont... not sure
  • b
    on a side note, im going to knock up a simple example of how i would do the same as your test app... ignore it ofc if the above is just to show some issue (which i think is a non issue?)
  • b
    weird, this didnt behave as expected:
  • b
    Copy code
    haxe
class MyDialog extends Dialog {
    public function new() {
        super();
        var closeMe = new Button();
        closeMe.text = "Close Me";
        addComponent(closeMe);
        closeMe.onClick = function(_) {
            hideDialog(DialogButton.OK);
        }
    }
}
  • b
    🤔
  • b
    nvm, i was compiling the wrong project 😄
  • b
    yikes, fun bug in haxeui-heaps...
  • b
    hiding a component seems to destroy it 😮
  • b
    (only with dialogs though)
  • b
    OK, so thats fixed now (git haxeui-heaps), back to the app original issue - its possible that maybe this fixed bug was forcing you to go down a weird route? Anyways, if this is the behaviour you are after:
  • b
    then its possible now - this would cause me an error previously (haxeui-heaps only)
  • b
    Copy code
    haxe
class MyDialog extends Dialog {
    public function new() {
        super();
        title = "Test Dialog";
        var closeMe = new Button();
        closeMe.text = "Close Me";
        addComponent(closeMe);
        closeMe.onClick = function(_) {
            hideDialog(DialogButton.OK);
        }
    }
}
  • b
    Copy code
    haxe
            var open = new Button();
            open.text = "Open Me!";
            Screen.instance.addComponent(open);
            open.onClick = function(_) {
                open.hide();
                var dialog = new MyDialog();
                dialog.width = dialog.height = 200;
                dialog.onDialogClosed = function(_) {
                    open.show();
                }
                dialog.show();
            }
  • n
    no matter how much time passes, I'm always impressed with how many targets haxeui supports O:
  • l
    Yeah, it was making me go down several weird routes. I did eventually figure out a workaround, but it's not an intuitive one
  • l
    Originally i had my code check if the dialog box was null in order to create a new one, and when it got declared a second time, it behaved like it was an entirely different box all together
  • l
    So despite making a new box, giving it the exact same events, actions, components, etc., it behaved like it was a different box i was accessing
  • l
    But only if I declared it as new a second time
  • l
    The work around I found was setting ``destroyOnClose`` to false, and then just checking if the class holding the UI was null. If it wasn't null, then I just add it to the stage instead of re-declaring the class
  • l
    Unrelated: I'm having issues assigning icons to a list view in heaps. I'm looking at the example, and it's showing ``data.add({item : "Name", image : "path/to/image.png"});`` But I'm unable to get any of my assets in my Res folder to show.
  • b
    So are you saying this is a non issue? Im not really sure what you were trying to do, if it still feels smelly, maybe you can knock up another sample and i can take a look
  • l
    yes and no? I was unsure if the way I was approaching it was the intended method
1...813814815...1687Latest