yeah, maybe no idea tbh

i would have expected both to work side by side... but maybe not

@User - i tried this:

haxe
class Main {
    public static function main() {
        var app = new HaxeUIApp();
        app.ready(function() {
            app.addComponent(new MainView());

            Lib.current.stage.addEventListener(TouchEvent.TOUCH_MOVE, onTouchMove);
            Lib.current.stage.addEventListener(TouchEvent.TOUCH_BEGIN, onTouchBegin);
            Lib.current.stage.addEventListener(TouchEvent.TOUCH_END, onTouchEnd);
            Lib.current.stage.addEventListener(TouchEvent.TOUCH_OUT, onTouchOut);
            
            app.start();
        });
    }
    
    private static function onTouchMove(event:TouchEvent) {
        trace("onTouchMove");
    }
    
    private static function onTouchBegin(event:TouchEvent) {
        trace("onTouchBegin");
    }
    
    private static function onTouchEnd(event:TouchEvent) {
        trace("onTouchEnd");
    }
    
    private static function onTouchOut(event:TouchEvent) {
        trace("onTouchOut");
    }
}

And it seemed to work fine on both windows and android (ie, the 3 buttons there onscreen from the xml work fine)

might need a minimal repro

I'll do that

not sure how to scroll the

ListView

to get the

selectedItem

in view

im changing

selectedIndex

from code

(using item renderer btw)

tried to calculate the right scroll position myself but

ListView.itemHeight

is -1

oh i just found this haha

haxe
    private function ensureVisible(itemToEnsure:ItemRenderer) {
        if (itemToEnsure != null && _listview.virtual == false) { // TODO: virtual scroll into view

i just hardcoded it for now then

selectedIndex*26

is a good

vscrollPos

ensure visible should work, and infact if you set the selected index it should automatically scroll into view

Ok, sorry for the knee-jerk reaction, I should've investigated further before... Seems like when you add code to a captured event and something goes wrong, other events of the same type and target do not get triggered.... But strangely I'm not getting any errors... Still investigating

... sounds fun :/

Oh am I outdated

dunno, unless its a bug... what backend?

I completely forgot to mention I'm using virtualised list view

ah

ill have a play

Ok, found the problem... The problem was my first handling of TOUCH_BEGIN was infinite, it ran forever... Naturally other subsequent events were forever waiting to be handled. Yeah, I'm that stupid, sorry for the wrong report... my bad...

cool - no worries - glad you managed to track it down

🙂

Is there a way to make using

ComponentMacro

more friendly with the vscode haxe extension?

Or rather the compilation server.

Compiling my project using without the server works fine but it takes longer of course.

this is an on going issue im afraid - ive tried multiple times to even understand what its issues are

more than open to suggestions / hints / ideas ofc

I've got no ideas right now. This kind of thing goes over my head.

i certainly dont understand the internals of the completion server