👍

-.kt

this may be a bit hacky, but you could use a

SimpleIntegerProperty

instead of the object property and use the ordinal of the enum?

Thank you both of you for helping. Simple property to contol bindings make sense but once things get more complex it starts getting confusing. Im also probably needlessly making the menu more difficult this way, but since im just doing it to learn... 🤷‍♂️

👍

it will all make sense eventually

I would drive the whole navigation off events. Will put up a post on that eventually

Things need to be more decoupled when you display windows in the nav because the controls aren’t right there

Yeah i figure that would just make everything much more simple. the print statement was going to be an event ... Thats how the main view was going to change out the content.

Good morning to those around. My File explorer/creator code is moving along. However, during testing I'm finding two odd things:

(1) In treeview, if I edit a cell (which is a TextFieldTreeCell), all is well. However, after I finish, the TreeView has lost focus, thus the selected item has changed and has a grey highlight, but is Not in focus. Is there something I can do to force the refocus on TreeView? <EDIT: SOLVED. I needed to add requestFocus() in the onEditCommit>

(2) Once I click on a TreeItem, I can't click on the white background to ensure the root is selected (in Swing, the selected TreeItem would become unselected). Thus, my client will not be able to add folders/files to the root (as it is hidden). Is this normal behaviour for a tree? i.e. if I click into white space, should it not unselect the currently selected tree item?

@sp33dy I think clicking outside just removes the highlight/focus, while the item is still selected until you select another one. You could probably add a click event to the treeview itself and remove the selection

Thanks, that's the conclusion I've got from testing. I've now added a setOnClick, but struggling to pinpoint from the mouse event whether it is selected node or not

getting there thanks @edvin

I think we determine something like that for TableView somewhere. Let me check.

I do find this odd behaviour, as I'm sure it should be catered for. Swing does it beautifully

...my reasoning is that I'm clicking into the TreeView, thus I want that pane to remain in focus, but it should look to see if I've actually selected anything. If not, it should be cleared (in my opinion)

There are some oddities in JavaFX default behavior, and most of the time we don't want to change that, but we could add an option to change it. Like

TableView.clickOutsideDeselects = true

for example

Trying to find that piece of code I'm talking about. It was connected to a MouseEvent I think

I remember it felt like a hack, so we might have gotten rid of it

We could probably use the pickResult to get at it

It certainly feels like a hack right now; as it is common behaviour of a tree

I'll post my code shortly, so you can see it becomes impossible for the user right now to add to the root. 😞

oh, pickresult is getting me closer

In a treeView, I suspect you'll always be over a cell, but you might be able to check if the cell represents an item or not

Click outside to deselect

Like this?

I don't know how useful this will be, once the items fills the screen you'll have a hard time deselecting, since the tree cells spans the whole width of the treeview

I wrote up something quick and dirty: