https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b

    bright-gpu-74537

    06/12/2020, 8:59 AM
    ie when interactive is set to true
    private function set_interactive(value:Bool):Bool {
    then make sure container is still first child, etc
  • b

    bright-gpu-74537

    06/12/2020, 8:59 AM
    i guess
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:00 AM
    for now I hacked it with a custom
    class StyleContainer extends Object
    and then loop thru a Component's children and
    Std.downcast(child, StyleContainer)
  • b

    bright-gpu-74537

    06/12/2020, 9:00 AM
    ok, and that works?
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:00 AM
    and it works 🎉
  • b

    bright-gpu-74537

    06/12/2020, 9:00 AM
    sweet
  • b

    bright-gpu-74537

    06/12/2020, 9:00 AM
    not a a massive hack either i would say, just making sure that the container for the graphics is the right one
  • b

    bright-gpu-74537

    06/12/2020, 9:01 AM
    i still think it probably always needs to be index = 0 at some point
  • b

    bright-gpu-74537

    06/12/2020, 9:01 AM
    otherwise i wonder if you'll get strange results of things drawing over each other... maybe it will never happen
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:01 AM
    yes, needa checkout where is the place does addChildAt
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:03 AM
    ok this is simple
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:04 AM
    just need to add an offet to
    handleAddComponentAt
    and such
  • b

    bright-gpu-74537

    06/12/2020, 9:21 AM
    yeah, and presumably in set_interactive too...
  • b

    bright-gpu-74537

    06/12/2020, 9:21 AM
    although maybe it makes less of a difference there
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:43 AM
    I think it is fine, because
    Interactive
    is more like a wrapper over an
    Object
  • b

    bright-gpu-74537

    06/12/2020, 9:44 AM
    yeah, i think so too
  • b

    bright-gpu-74537

    06/12/2020, 9:44 AM
    thanks for the fixes / PRs btw 🙂
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:46 AM
    I am playing with coconut.haxeui + haxeui.heaps Seems working quite well. Impressive work to you and Juraj
  • b

    bright-gpu-74537

    06/12/2020, 9:47 AM
    i was going to ask if this is via coconut (i figured it would be 😉 )... cool stuff 🙂
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:50 AM
    except
    style
    attr isn't properly supported, else seems good
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:51 AM
    I wonder, does components (e.g. Button) has default style? or does it only have
    class
    by default?
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:51 AM
    My real question is: is it safe to replace the Style instance completely?
  • b

    bright-gpu-74537

    06/12/2020, 9:52 AM
    the .style instance of the component?
  • b

    bright-gpu-74537

    06/12/2020, 9:53 AM
    so how does coconut work? I mean, does it totally subvert the haxeui macros?
  • b

    bright-gpu-74537

    06/12/2020, 9:53 AM
    ie, how does end up as an instance of VBox?
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:54 AM
    <VBox attr=${value}>
    is basically transformed to:
    Copy code
    haxe
    var c = new VBox();
    c.attr = value;
  • b

    bright-gpu-74537

    06/12/2020, 9:55 AM
    right, but how does it know haxe.ui.containers.VBox for vbox and haxe.ui.components.Button for button (ie, the different packages)
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:56 AM
    I have to import it
  • b

    bright-gpu-74537

    06/12/2020, 9:56 AM
    gotcha
  • c

    cool-psychiatrist-49311

    06/12/2020, 9:56 AM
    <VBox style=${value}>
    so this will always assign a new value to
    vbox.style
1...275276277...1687Latest