Haxe #haxe-ui

bright-gpu-74537

10/15/2019, 8:26 AM

vscrollPos = vscrollMax

fancy-photographer-54440

10/15/2019, 8:41 AM

Like this?

textArea.onChange = (_ -> textArea.getTextInput().vscrollPos = textArea.getTextInput().vscrollMax);

bright-gpu-74537

10/15/2019, 8:51 AM

is there no properties on textArea itself?

fancy-photographer-54440

10/15/2019, 9:17 AM

fancy-photographer-54440

10/15/2019, 9:18 AM

I tried doing this on its

element

field (HTML5 target) but that does nothing

bright-gpu-74537

10/15/2019, 9:18 AM

oh... what backed? Not that im guessing it matters much... maybe there those properties havent been exposed at all...

bright-gpu-74537

10/15/2019, 9:19 AM

any chance you could open an issue on haxeui-core repo so we can track it?

fancy-photographer-54440

10/15/2019, 9:21 AM

Sure

fancy-photographer-54440

10/15/2019, 9:22 AM

Do you know if haxeui is compatible with the Haxe compilation server? I'm getting this diff after compiling through it.

bitter-family-72722

10/15/2019, 9:35 AM

I think others have run into that as well

bitter-family-72722

10/15/2019, 9:36 AM

I wonder if there's some static variable in one of HaxeUI's macros that needs a

@:persistent

bright-gpu-74537

10/15/2019, 9:37 AM

what would be the conditions for using such metadata?

bitter-family-72722

10/15/2019, 9:37 AM

"Keeps the value of static variables in macro context across compilations."

bitter-family-72722

10/15/2019, 9:37 AM

not sure if you're caching anything in static vars?

bitter-family-72722

10/15/2019, 9:38 AM

such as those resources that seem to vanish in particular 🙂

bright-gpu-74537

10/15/2019, 9:38 AM

let me have a dig

fancy-photographer-54440

10/15/2019, 9:42 AM

There was something else that disappeared but I just closed the diff... looked like some huge lookup table or something

bright-gpu-74537

10/15/2019, 9:43 AM

@fancy-photographer-54440 - are you able to edit a haxeui source file and see?

bright-gpu-74537

10/15/2019, 9:43 AM

haxe.ui.macros.ModuleMacros, line 24

bright-gpu-74537

10/15/2019, 9:44 AM

private static var _modules:Array<Module> = [];

bright-gpu-74537

10/15/2019, 9:44 AM

can you put a

@:persistent

in the front and see if the problem... ... .. erm... ... persists

fancy-photographer-54440

10/15/2019, 9:48 AM

That makes no difference

fancy-photographer-54440

10/15/2019, 9:51 AM

It doesn't take much to reproduce this with vshaxe:

Copy code

class Main {
    static public function main() {
        haxe.ui.Toolkit.init();
        var button = new haxe.ui.components.Button();
        button.text = "Hello World";
        haxe.ui.core.Screen.instance.addComponent(button);
    }
}

fancy-photographer-54440

10/15/2019, 9:51 AM

1. Compile, 2. ctrl + click on

Screen

, 3. compile again

fancy-photographer-54440

10/15/2019, 9:52 AM

Looking at

Screen

invalidates a lot of modules I think

bright-gpu-74537

10/15/2019, 9:53 AM

ok, what about sledge hammer approach, does putting that meta on all the static vars at the top of that file do anything?

bright-gpu-74537

10/15/2019, 9:53 AM

probably not, but worth a try... does the LS need to be restarted also?

fancy-photographer-54440

10/15/2019, 9:53 AM

That doesn't help either

bright-gpu-74537

10/15/2019, 9:54 AM

wide-greece-63479

10/25/2019, 2:35 PM

Hi guys! Trying out HaxeUI Kha on Android native, and I get unexpected behaviour on the Button.onClick events. Any click anywhere is caught by the first button listener.