and wanted to sketch this out to turn it into a fragment as I need to apply this in several modes.

thanks again

Darn it. Just spotted userData. That's what I also needed. Didn't spot that subtle slot for data

You’ve never used that in Swing?

I'm just searching a few of my projects. I don't recall, per say, that it was a specific technique I was using.

There's also a Properties object that's a more general way of doing this. Each Node keeps track of a Map. This is used heavily in TornadoFX

userData is a special case (single item versus multiple items) that I figured was more familiar to Swing readers

yes, I'd been using it with out having given it much thought in years gone past

the switch to JFX has left me forgetting some basic's

My like my touch typing. I know I'm pressing keys and still amazed that I never look at the keyboard!

LOL. @edvin’s status just changed to active when "keyboard" appeared. must be a bot

Haha 🙂

is there a way with the typesafe css, to do the equivalent of this

.jfx-hamburger {
	-fx-background-color: lightgrey;
}

.jfx-hamburger StackPane {
	-fx-background-color: green;
}

particularly the child selector of StackPane

Use

backgroundColor += c("green")

c(...)

is a helper function to turn various common patters into actual JavaFX colors.

yeah i get that, i need specifically to be able to target nodes under this one

ok screw it I wrote my own 😄

does this exist somewhere else? does it look ok?

Time to go offline again. This is looking much healthier!

Thanks @carlw @gtnarg

The collision on file rename is dealt with. I've NOT used runAsync, purely more from the point that I couldn't get it to function correctly. Will address later. For now, it is working perfectly for my needs. Going to return back to adding new nodes and then adding drag-drop

IMHO the best strategy for this would be to validate as much upfront. before you attempt to execute an OS file rename, check it against it's siblings for collisions. then, you can be optimistic about the rename. if there's an error, you can post an event back calling for a general refresh of the tree structure which will undo the optimistic rename that preceded the actual operation

In the apps I build, nothing besides RAM operations (objects, properties) would be on the FX thread. For instance, if you rename a file on a USB and pull the drive out, the whole app is screwed if you're on the FX thread. You'll get an error for sure with my technique, but the app will be lively and will recover.

Oh I agree with all of your reasoning. I had the same thought in the car drive over to my daughters swim. Easy to do a quick check in the parent folder to see if name exists first. Agree with moving it of FX thread (just didnt get it to work earlier when I tried)

will gradually improve; but have a deadline to meet

..and the usb idea is a great way to test. I was wondering how I could simulate a problem. Was going to create a virtual file link and delete it was the app was running. Pulling a USB would be much easier!

yeah. pull it out before you commit the rename

Is the TornadoFX icon available somewhere as svg 🌪️?

that one