https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    hmm, works for me
  • b
    Copy code
    xml
<module>
    <components>
        <component file="assets/some-component.xml" />
    </components>
</module>
  • b
    Copy code
    xml
<hbox>
    <button text="Button 1" />
    <button text="Button 2" />
</hbox>
  • b
    Copy code
    xml
<some-component />
  • i
    hovering over the class for the layout I'm trying to include 
    tiletoolbar
    in, gets me this error: 
    no class found for component: tiletoolbar
  • i
    maybe it's something to do with mixing code-and-XML and XML-only?
  • b
    > hovering over the class for the layout I'm trying to include what does that mean?
  • i
    the layout I'm trying to include this custom 
    tiletoolbar
    in is called 
    mainView.xml
    , with a corresponding class 
    MainView
    declared via code:
    Copy code
    hx
@:build(haxe.ui.macros.ComponentMacros.build("assets/ui/editor/mainView.xml"))
class MainView extends VBox
{
    public function new()
    {
        super();
    }
}
  • i
    the build macro part is underlined with an error, that 
    no class found
    one
  • b
    yeah, that should be totally fine - its the same as ive done basically
  • b
    and yeah, the error is valid, in the sense that that xml is using a component haxeui cant find
  • b
    one thing ive just though about, is that my component isnt in a sub folder, lemme try that
  • b
    ... bingo
  • b
    Copy code
    D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ModuleMacros.hx:374: WARNING: Could not find path C:/Temp/haxeui-testapps/test01/assets/foo/bar/some-component.xml
D:\Work\HaxeUI\haxeui-core\haxe/ui/Toolkit.hx:54: characters 9-38 : Uncaught exception Could not read file C:/Temp/haxeui-testapps/test01/assets/foo/bar/some-component.xml
D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ModuleMacros.hx:407: characters 19-51 : Called from here
D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ModuleMacros.hx:333: characters 21-52 : Called from here
D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ModuleMacros.hx:187: characters 9-34 : Called from here
D:\Work\HaxeUI\haxeui-core\haxe/ui/Toolkit.hx:54: characters 9-38 : Called from here
D:\Work\HaxeUI\haxeui-core\haxe/ui/Toolkit.hx:16: lines 16-201 : ... Defined in this class
src/MainView.hx:6: characters 1-8 : Warning : no class found for component: somecomponent
D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ComponentMacros.hx:289: characters 70-83 : Unknown identifier : c5
D:\Work\HaxeUI\haxeui-core\haxe/ui/macros/ComponentMacros.hx:289: characters 70-83 : ... For function argument 'child'
src/MainView.hx:7: lines 7-19 : ... Defined in this class
  • b
    do you get the "could not find path" warnings?
  • b
    oh, actually, ignore all that... i had the file in the wrong place... its all fine now
  • b
    OK, so are you sure your module.xml is on your classpath?
  • b
    what if you add 
    -D module_resolution_verbose
    do you get something like this:
  • b
    Copy code
    scanning class path for modules
    module found at 'D:/Work/HaxeUI/backends/haxeui-html5/haxe/ui/backend/module.xml'
    module found at 'D:/Work/HaxeUI/haxeui-core/haxe/ui/module.xml'
    module found at 'src/module.xml'
3 module(s) found
  • i
    Copy code
    matt@desktop-ubuntu:~/MEGAsync/code/flixel/HelloWorld$ lime build linux -D module_resolution_verbose
scanning class path for modules
    module found at 'source/module.xml'
    module found at '/home/matt/.local/share/haxe/lib/haxeui-core/git/haxe/ui/module.xml'
    module found at '/home/matt/.local/share/haxe/lib/haxeui-flixel/git/haxe/ui/backend/module.xml'
3 module(s) found
  • b
    so strange
  • i
    I updated to most recent git for both -core and -flixel, still no dice
  • i
    maybe the build macro is trying to build 
    mainView.xml
    before the module has been parsed? but the output from verbose at least shows it's scanning the module paths first, so probably not
  • b
    yeah, it should all be fine... is there anyway you could create another test project, and just try to reproduce this minimally?
  • i
    I'll have a go
  • b
    thanks!
  • i
    oh god now new flixel projects are failing because it tries to look up the spec of 
    Project.xml
    and the lime website URL still doesn't work
  • b
    i think it changed recently, didnt it?
  • i
    the default XML still looks at http://lime.software/xsd/project-1.0.2.xsd, which doesn't exist any more
  • b
    ¯\_(ツ)_/¯
1...122512261227...1687Latest