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

    bright-gpu-74537

    06/14/2019, 2:33 PM
    @fierce-restaurant-45913 - its really quite strange, but i think there is something off with something on your installs
  • b

    bright-gpu-74537

    06/14/2019, 2:33 PM
    but we seem to have the same versions of everything
  • b

    bright-gpu-74537

    06/14/2019, 2:34 PM
    so to confirm: * latest haxeui-core (git, branch new-component-method) * latest haxeui-openfl (git, branch new-component-method) * latest openfl / lime (haxelib versions) * haxe rc2
  • b

    bright-gpu-74537

    06/14/2019, 2:34 PM
    ?
  • b

    bright-gpu-74537

    06/14/2019, 2:34 PM
    (thanks @quick-king-64105 )
  • q

    quick-king-64105

    06/14/2019, 2:37 PM
    Copy code
    C:\Users\Dorian Greyson\Documents\deleteme>haxelib list
    haxeui-core: [new-component-method] old
    haxeui-openfl: 0.0.2 [new-component-method]
    lime: 7.2.0 7.2.1 7.3.0 [7.5.0]
    openfl: 8.7.0 8.8.0 [8.9.1]
    I can pull git versions but it should be most recent for both of those. Just so the note's here in case it matters at all.
  • b

    bright-gpu-74537

    06/14/2019, 2:39 PM
    yeah, i think your versions match mine... and it works as expected... i guess just wait till benji and confirm or retest or something, as doesnt make alot of sense to me at the moment... i wonder if nuking the haxelib folders and starting again might help (openfl, haxeui-core and haxeui-openfl)
  • q

    quick-king-64105

    06/14/2019, 2:39 PM
    also, unsurprisingly...
    Copy code
    C:\Users\Dorian Greyson\Documents\deleteme>haxe --version
    4.0.0-rc.2+77068e10c
  • b

    bright-gpu-74537

    06/14/2019, 2:40 PM
    to be fair, haxe version i dont think matters, but wanted to double check and i think all 3 of us are on rc2
  • q

    quick-king-64105

    06/14/2019, 2:40 PM
    No real input there. Just verifying the relevant parts of my setup.
  • f

    fierce-restaurant-45913

    06/14/2019, 3:22 PM
    i have deleted haxeToolKit and reinstall everything and it seems to work on neko ( i didn't tested other for the moment )
  • b

    bright-gpu-74537

    06/14/2019, 3:31 PM
    ok, great!
  • f

    fierce-restaurant-45913

    06/14/2019, 7:23 PM
    does dialog box is implemented ? the code of the method " showDialog()" is in comment
  • b

    bright-gpu-74537

    06/15/2019, 6:56 AM
    dialog has changed a little in new-component-method... if you give me a little time ill knock up a sample here: https://github.com/haxeui/component-examples
  • b

    bright-gpu-74537

    06/15/2019, 10:15 AM
    ok, its all working... just need to clean things up a little bit... forgot but the new dialog is still called "Dialog2"
  • b

    bright-gpu-74537

    06/15/2019, 12:17 PM
    @fierce-restaurant-45913 - heres a dialog example: https://github.com/haxeui/component-examples/tree/master/dialogs
  • b

    bright-gpu-74537

    06/15/2019, 12:17 PM
    you'll need latest haxeui-core (haxeui-openfl should be fine)...
  • b

    bright-gpu-74537

    06/15/2019, 12:17 PM
    https://github.com/haxeui/component-examples/blob/master/dialogs/src/Main.hx
  • b

    bright-gpu-74537

    06/15/2019, 12:21 PM
    wish openfl's shadows were working propery 😦
  • b

    brave-kangaroo-30399

    06/15/2019, 2:53 PM
    @bright-gpu-74537 what do you think about some kind of ā€œdeactivatedā€ property in core’s component?
  • b

    brave-kangaroo-30399

    06/15/2019, 2:54 PM
    Thinking about @quick-king-64105’s issue where inactive flixel objects can still receive mouse events
  • b

    brave-kangaroo-30399

    06/15/2019, 2:55 PM
    I’m wondering if that should be handled in my mouse handler or not, like would it affect core in a negative way
  • b

    bright-gpu-74537

    06/15/2019, 2:55 PM
    i cant remember where now, but there was a time i wanted this too
  • q

    quick-king-64105

    06/15/2019, 2:55 PM
    I'm awake, don't mind me.
  • b

    brave-kangaroo-30399

    06/15/2019, 2:56 PM
    And I don’t see how Screen mouse events would be affected by my ComponentImpl ones
  • b

    bright-gpu-74537

    06/15/2019, 2:56 PM
    ah yeah, i remember now... it was in the designer... i wanted the controls to essentially be disabled, but not greyed out, ie, no mouse events
  • b

    brave-kangaroo-30399

    06/15/2019, 2:56 PM
    Like I’m not sure there would be a way to disable the ā€œclick outside a dropdown to make it disappearā€ screen event
  • b

    brave-kangaroo-30399

    06/15/2019, 2:57 PM
    Without doing it in core
  • b

    bright-gpu-74537

    06/15/2019, 2:57 PM
    right... im not totally sure i follow... so in flixel you can have "inactive" states?
  • b

    brave-kangaroo-30399

    06/15/2019, 2:57 PM
    Yeah all sprites and states have an active property
1...585960...1687Latest