On any click inside the Region to be specific

@pim That shouldn't even matter either, and it doesn't happen when I test it on

DataGridTestApp

in the framework.

Weird.. This is my code

@pim Sorry, my bad!

It does indeed.

Oh okay 🙂

Not sure what the best solution is, because I can't find out how it's solved in JavaFX components.

I'll try to help by reading the JavaFX sources

I guess I could remove focustraversal from the child components. Maybe that's what happens in JavaFX Core components.

If you add custom components to a TableView, focus is lost on the TableView too. With a DataGrid, everything is a custom component, so I think you'd have to disable focustraversal on the children.

I'll try

@edvin do you think that focus causes too many problems with the off-the-shelf behavior of tableview? maybe it would mess up the arrow key handlers if random components started setting their own focus

@carlw Indeed.

I think I know how to do this correctly.

@edvin what do you think about MVVM? keep the selected operands in a ViewModel for binding between overview and details?

It's actually the virtualflow that should have focus.

@edvin Setting focusTraversal to false on children does not seem to help

@pim I know, seeing the same.

Took me a while because I tried it with the previous commit as well and I had to look up git docs because I'm not exactly a git guru 😛

The virtualflow receives focus, and keeps it even when you select other nodes inside it that are not focustraversiable.

Sounds correct. Does it get a blue selection border as well? I think the other panes do

Got it 🙂

Yeah, selection is not the same thing.

What I did was just disable focustraversal for the virtualflow.

Is there a way I can speed up the mvn builds? It's taking me 60+ seconds every time 😞

@edvin Can you tab through the controls?

Yes

@pim No 🙂

Building now, I'll test it

@pim have you disabled the tests?