https://linen.dev logo
Join Discord
Powered by
# openfl
  • s
    Copy code
    bat
export/debug/windows/haxe/ApplicationMain.hx:216: characters 25-37 : Too many arguments
export/debug/windows/haxe/ApplicationMain.hx:151: characters 5-36 : ... Called from macro here
export/debug/windows/haxe/ApplicationMain.hx:216: characters 25-37 : Too many arguments
export/debug/windows/haxe/ApplicationMain.hx:169: characters 4-35 : ... Called from macro here
  • s
    huh...
  • s
    i got this from an almost empty openfl project
  • s
    i just got it from a template, modified project.xml a bit and used a bit of haxeui in it
  • s
    Copy code
    hx
package;

import haxe.ui.HaxeUIApp;
import openfl.display.Sprite;
import haxe.ui.core.Component;
import haxe.ui.ComponentBuilder;

class Main
{
    var app = new HaxeUIApp();

    public function main()
    {
        app.ready(function()
        {
            var main:Component = ComponentBuilder.fromFile('assets/main.xml');
            app.start();
        });
    }
}
  • s
    The Main.hx file
  • h
    I embed HaxeUI in an openfl project but I don't use HaxeUIApp to do it. Just call Toolkit.init() should be all you need.
  • s
    oh
  • h
    Actually your Main doesn't extend Sprite which mine does. I think this is in the backend example. But here is a pointer to my Main
  • s
    trying to use an hxp file for my project, but its trying to build to neko for some reason.
    Copy code
    bat
Called from lime/_internal/backend/native/NativeCFFI.hx line 613
Called from lime/system/CFFI.hx line 172
Called from lime/system/CFFI.hx line 306
Uncaught exception - Could not find NekoAPI interface.
    or assume that's whats happening here
  • p
    The build tools use Neko, and it looks like it can't find 
    lime.ndll
    for some reason. Did it only break when you started using hxp files (ie does it work if you use a project.xml file),
  • s
    it only happens with hxp
  • l
    I think I remember the workaround for this bug; grab the NDLL from your Haxe install folder and put it in the root of your project
  • s
    oh! let me try.
  • s
    neko.ndll, right?7
  • s
    tried with neko.ndll, doesn't seem to work. or that isn't it?
  • s
    oh that's dll
  • s
    i just realized
  • l
    Um I think you need 
    lime.ndll
    ?
  • s
    i do? that doesn't come with the template project.
  • l
    Because it's trying to call a Lime function
  • s
    copying lime.ndll from a random project seems to work.
  • s
    that's funky
  • s
    tried setting app.path through hxp and it goes to the default folder
  • s
    Copy code
    hx
    function dirConfig() {
        var architecture = is64Bit() ? "x64" : "x86";
        var buildDir = 'export/${debug ? 'debug' : 'release'}/$target/$architecture';

        Log.info('Output directory: $buildDir');
        app.path = buildDir;
    }
  • s
    that function is called on the new function
  • c
    Hello! This might be a little late but I was in the same boat as you and anti-aliased graphics were driving me crazy until I saw your thread so thank you! Although I have since discovered that Instead of using 
    smooth = false;
    on every graphic element in the game, you can edit the HaxePunk source file of 
    Graphic.hx
    and change the field 
    public static var smoothDefault:Bool = true;
    to 
    false;
    . That way when the game runs, newly created graphics will have the 
    smooth
    setting set to 
    false
    by default. Hope this helps anybody in the future!
  • f
    BTW UPDATE: It turns out the way defaults were set changed between lime 7.2.1 and 8, so the game was running /just fine/ but at 1x1 resolution and 1fps with OpenGL turned off.
  • f
    (all the defaults were set to 
    null
    )
  • a
    Hey on the html5 target is there any documentation on changing the default html page used to embed the game or to manipulate said page?
1...424344...57Latest