https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • k
    just noob haxor issue ))
  • b
    if:
  • b
    var x:Dynamic = buildComponent(...)
    is used it think it stays as an Expr
  • b
    however, if:
  • b
    var x:Component = ...
    then all is fine
  • b
    That's an expression macro. It must always return an Expr, but once its out of macro context, it's typed depending on what the Expr is.
  • k
    so it's not casted to component which does have all the methods...
  • b
    You can't work with Expr outside of macro context.
  • k
    nice. I should learn macros. didn't invested time into this topic. sorry )
  • b
    sure, but for some reason, if the result is assigned to a Dynamic then things dont work... im not sure if gets typed correctly
  • b
    i havent tested this myself, so its all just guesses
  • b
    If you assign it to a Dynamic, you work with it as if it was Dynamic. But it shouldn't cause any issues apart from ones that are caused by something being Dynamic. 🙂
  • b
    So what are the things that don't work?
  • b
    yeah, thats what i would have thought
  • b
    i think all the component functions, dont worrk, is that correct @User - what if you try something basic like setting the text of the component? Ill have a this afternoon, got meetings in an hour
  • k
    I cant use 
    ui.findComponent
    from screenshot above if ui is Dynamic on neko target. it throws an exception 
    Uncaught exception - Invalid call
  • b
    but works on hxcpp?
  • k
    yeah it works on hxcpp 
    lime build linux && lime run linux
  • b
    Interesting. Most likely a neko bug then, which no one is going to fix these days.
  • b
    fair enough... weird... well, i guess for now just type it as component... dont quite understand it tbh
  • b
    A neat trick in macros is to explicitly type the result, if it's not already there.
  • k
    @User I had some troubles with HL I don't remember already )
  • b
    Then just doing 
    var foo = macroCall(); $type(foo);
    would show the correct type due to inference.
  • k
    so I use Neko which works almost always
  • b
    Neko is old, simple, and not really maintained anymore (I think).
  • k
    i mean for development and debugging only. but I understand. should drop it
  • b
    yeah, i think if you dont type it, its fine, its when you explicity type the result as Dynamic i think
  • b
    > A neat trick in macros is to explicitly type the result, if it's not already there.
  • b
    got an example?
  • b
    Something like instead of 
    return expr
    , you do 
    return macro ($expr:$type)
    .
1...329330331...1687Latest