it works lovely, the menu item greys out when I click on a directory but not a file

oh, I'm in a treeview

darn it, you are treetable

sorry bud. I must read

well, really i want to stop the entire context menu from popping up

I imagine it will be VERY similiar

eh treeview and treetable i believe are very similar, so that would work in general

I'm setting enablewhen on items, but there is no reason why you can't do on the contextmenu itself

with beginner's hat on, so could be wrong 🙂

i'll see if i can do what you have and use enableWhen... i tried using that but it managed to grey out my entire table :X

yeah thats weird... enableWhen within my contextmenu dsl seems to be affecting the treetable itself :x

@sp33dy i have it somewhat working. i set a bool prop when user selects something. and have visibleWhen bound to that bool for each item. Except I have a separator ... and so even when no items are shown i get a tiny box with a tiny separator in it. 🤣

😞

@Spike Baylor All extension functions will "bubble up" until they find a suitable target. We do have

enableWhen

for menu items, but not for the context menu itself.

i see. My solution is ok for now. This is just a "fun" project for me that could in the distant future become something useful so nothing needs to be perfect at the moment. I'm diving head first into both tornadofx and javafx so soon i may just need to take a step back and make sure i truly understand how some of this works, particularly the javafx vs swing way of doing things with properties and bindings and all that. I get it on a very simple level, but not enough to be super comfortable either.

here's a contextmenu example

@Spike Baylor Break yourself of the addListener() habit. If you're not binding, you're probably doing something suboptimal.

yeah i don't have any addListeners. i think the difference here is that I was just doing something like

TreeTableView<MyObject>().apply {
   // add columns
  contextmenu {
    item("menuitem")
    item("yep")
  }
}

where yours dynamically adds and removes the context menu. which in the long run might be a better way for me to go as right now I really only have on/off for the menu but in the long run may want to swap out context menus entirely depending on the item selected

unless i'm misunderstanding what is happening there

Any tips/tricks for when you've got an existing complex model, and want to create a JavaFX-property version

@carlw thanks, that works splendidly and sets me up much better for what i'll need to do in the future i think.

@hudsonb I'd look into MVVM. That FX Propertizes the objects but in a value-added way. Your domain objects stay the way they are with logic, relation, etc. Each view is supported by properties that more closely mimic the UI

that way, you don't have trivial mappings or wrappers although that's an option too

This code from @Rob goes right from JSON to JavaFX Property classes with Klaxon

Ya MVVM is how I've been doing it, but it seems like overtime my ViewModel is mostly becoming a full blown wrapper over the underlying model

Keep going with it then and plan for a refactor where you scrutinize any redundancy

Hmm maybe I can make a delegated property that can handle some of the boilerplate for me in the ViewModel