https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    im not sure i want to explicity type the result as Component as it could be other stuff too (Button, Box, etc)... but if its not already typed it might be nice (if thats what you mean)
  • b
    But that's only useful if you know the type, and it's not already inferred from the expr itself.
  • b
    ok, nice, i didnt know that, so thats good to know...
  • b
    but yeah, i think letting the compiler infer the type probably makes more sense
  • k
    I think that mention to correctly type the expected result in documentation is enough.
  • b
    The 
    (foo:Bar)
    part works in normal code too. Type check it's called, I think.
  • b
  • b
    something in neko breaks that when its explicitly typed as Dynamic is all i guess
  • b
    It would cause it to search for the fields via reflection, but if the fields are part of it (not static extension or some abstract type stuff) it should find it.
  • b
    What could happen is DCE removing it, but the same would happen on other targets. That goes for the aforementioned things too.
  • k
    but afaik DCE is off by default.
  • b
    It's constrained to the standard library by default, so yeah.
  • k
    oh you're right. that's not the same )
  • b
    it sounds like its just a neko bug
  • k
    @User no support for disabled components? like 
    button.disabled = true;
    and it just grays out and does not react to any events.
  • k
    I can remove the listener of course but that would be handy )
  • k
    since I could click a button, disable it, wait until it request something from server and read result async, then enable it back again.
  • b
    component.disabled = true / false
    should work fine
  • b
    unless ive somehow broken it recently
  • k
    oh great. just didn't found that in examples. great it exist
  • b
  • b
    hmmmm, weird that that isnt in the api docs... it seems my docgen misses out a load of properties / functions :/
  • k
    Oh I didn't check in API docs for this property just examples. But yeah I see it's missing in API docs too. Also should mention that even if it was listed in Component it should ideally be listed as inherited property for Button (and any other component) docs too 😉 That would be just awesome.
  • k
    yeah, that's a lot of stuff to look for %)
  • k
    oh I see there's a checkboxes to show all the properties.
  • k
    sorry )
  • b
    yeah, the docgen itself is doing something strange
  • b
    no idea what - ill check it out at the weekend
  • l
    I'm running into a problem where if I extend a component and have the class expect an argument, i get compile errors in ``haxe.ui.macros.Macro.hx``. I have a github issue drafted, but I want to make sure if this problem is already known
  • l
    @User
1...330331332...1687Latest