https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • h
    I could create a quick demo project in a few minutes I'm sure
  • h
    On another note, how have you been using kha with modules without using the '../asset' work around? I'm assuming this is supposed to be possible
  • b
    i use "haxeui create kha" which moves somethings around
  • b
    im almost certain i would have used modules there, but ill check
  • b
    maybe i never tested "classes from xml files" though
  • b
    which is when this issue comes to light, correct?
  • b
    ie, 
    <component file="../assets/file.xml" />
    in a 
    module.xml
  • h
    Right! That should really be all there is to the bug
  • h
    and then you can't access it like 
    assets.File
  • b
    gotcha
  • b
    and with your PR that works again? i presume normal non-".." paths still work also
  • b
    btw, im going to have a play at rewriting the way custom components work in general thanks to that conversation yesterday, i think it can (possibly) be alot simpler and without that wrapper component
  • b
    unless ive overlooked something and that wrapper component is needed
  • h
    Well I did just run into an error. Maybe I missed that actually
  • b
    on a normal file class?
  • h
    No wait - I think it worked I'm just clumsy haha
  • b
    🙂
  • h
    It did work, I forgot I gave my normal file path an alias
  • h
    I didn't make that same mistake when it's using 
    ..
    though! I know that is true haha
  • h
    Also yeah - that sounds great! Components having an extra element around them have always felt a little off
  • b
    yeah, im wondering if there was another reason as to why it was done that way... not sure yet
  • b
    there could be something else im overlooking, but ill find out when i start playing
  • b
    so, just to confirm, in your PR... the following xml => classes work:
  • b
    <component file="../assets/class1.xml" />
    <component file="../../assets/class1.xml" />
    <component file="../../bob/../assets/class1.xml" />
    <component file="assets/class1.xml" />
    <component file="./assets/class1.xml" />
  • h
    Sorry - didn't catch this. Were you asking me to check on my end real quick?
  • b
    yeah, just to see if the above work with your change
  • b
    i think only 
    <component file="assets/class1.xml" />
    will work without it
  • b
    (if im understanding correctly anyway)
  • h
    Tested it - works!
  • h
    This all compiled and rendered together
1...290291292...1687Latest