Haxe

It'll take me a bit before I can strip out the database connection stuff from my app, so we'll see if I can get it to ya

I'll copy the kha project's contents into the openfl one and see if it runs with the same scenario

sorry, thinking and typing at the same time...

heh heh, no worries... ping me if you get a minimal test case

I made a minimal app that contains the same layout as the kha one and it works fine

I'm going to tweak it until I find the step that reproduces my problem... I think I know what it might be

in this, I'm adding the layout to the app in the main file, in my main app, I extend the scrollview for the layout, and I add that to the app. Then I add my layout on top of that scroll view

I added the scroll view with the layout and then a button over the top. When I hit tab, things didn't go well...

... so this begs the question... why didn't kha work? Kha also didn't catch the tab key in general... I'll have to look into that later...

<@385014891750096896>  So I'm up and running with proper tabbing, but now I have a more basic issue. I originally was using AddChild for my layout in the scrollview. That took into account the X and Y positions I gave the elements. However, it was the original reason my tabbing wasn't working. I switched to addComponent and tabbing now works, but it no longer seems to care about X and Y position.

Is there an easy way to make the elements utilize the x and y cords or to simply make the elements that would go off screen go to a new column? I feel like the latter wouldn't be hard, but its been a while since I've done any html/xml layouts

```xml
<scrollview>
    <absolute>
        <button left="300" top="300" />
    </absolute>
</scrollview>
```

```xml
<scrollview width="100%" height="200" contentWidth="100%">
    <hbox continious="true" width="100%">
        <button />
        <button />
        <button />
        <button />
        <button />
        <button />
        ...
    </hbox>
</scrollview>
```

the last one is a continuous hbox, so it will grow horizontally until it gets to the 100% width of the parent (contentWidth), the it will start placing on the next line