https://linen.dev logo
Powered by
# haxe-ui
  • c
    ah okay, yeah sure - ill update everything and try again
  • b
    thanks, and just fyi, that app above works fine on release and debug HL (changing selectFile to openFile)
  • b
    Is there any progress on the file save dialog?
  • c
    So I updated the versions via
    Copy code
    haxelib git haxeui-core https://github.com/haxeui/haxeui-core
haxelib git haxeui-heaps https://github.com/haxeui/haxeui-heaps
    and changed selectFile to openFile but the problem persists
  • c
    which is weird seeing as it works for you
  • b
    weird, im guessing it has to be something in you system (or HL?)
  • b
    can you send over the .hl?
  • b
    Not yet, honestly, i forgot about it 😄 Ill take a look this eve
  • b
    :D
  • c
    this thing? that's super kind of you, thanks so much
  • b
    Thanks! Haxeui has been amazing all around, looking forward to contributing to it this summer :)
  • b
    that works fine on this end... so must be you system / hl
  • c
    ok cheers, ill start investigatinmg
  • b
    thats interesting though
  • b
    looks likes HL detects when its not updating.... this happens if you just leave the open dialog there for long enough
  • b
    not the issue you are talking about but interesting anyway
  • c
    wait so running the .hl file also works for me
  • b
    I found out that's also an issue with openfl FileReference on HL
  • c
    it's just running in debug mode in vscode doesn't
  • b
    So I don't think it's heaps specific
  • b
    ah, so maybe VSC is attching something to it when you run in debug mode... and probably doesnt like that the main loop has been paused
  • c
    hmmm yeah
  • b
    Copy code
    haxe
    static function __init__() {
        #if !usesys
        hl.Api.setErrorHandler(function(e) reportError(e)); // initialization error
        sentinel = new hl.UI.Sentinel(30, function() throw "Program timeout (infinite loop?)");
        #end
        #if ( target.threaded && (haxe_ver >= 4.2) )
        mainThread = sys.thread.Thread.current();
        #end
    }
  • b
    thats from heaps... maybe there is something similar in HL itself
  • b
    shame you cant switch that off... i guess 30 secs is enough to select a file? 😮
  • c
    haha
  • p
    hxd.System.allowTimeout = true
    to disable the timeout check. Alternatively call 
    hxd.System.timeoutTick()
    regularly.
  • b
    nice one... good to know - i dont think haxeui should be setting it though, i think ill leave it to the user
  • p
    Well, setting allowTimeout is exactly what heaps is doing in it's file dialog implementation
    Copy code
    hx
var old = hxd.System.allowTimeout;
            hxd.System.allowTimeout = false;
            var path = hl.UI.loadFile({
                fileName : options.defaultPath,
                filters : options.fileTypes == null ? null : [for( e in options.fileTypes ) { name : e.name, exts : e.extensions }],
                title : options.title,
            });
            hxd.System.allowTimeout = old;
            if( path == null ) return;
            if( options.relativePath ) {
                var cwd = Sys.getCwd();
                if( StringTools.startsWith(path, cwd) )
                    path = path.substr(cwd.length);
            }
            var b : BrowseSelect = {
                fileName : path,
                load : function(onReady) {
                    var data = sys.io.File.getBytes(path);
                    haxe.Timer.delay(function() onReady(data),0);
                },
            };
            onSelect(b);
    (And it looks like it's 
    hxd.System.allowTimeout = false
    to disable the timeout check?)
  • b
    hmmm, maybe its my heaps then, but i dont see that behaviour
1...111411151116...1687Latest