but the important things are:

(1) I want to line up the 'summary line' (which is the line with the button

(2) with the children. Each child will be an amount that makes up the summary; but will be added and subtracted often

If I use the TreeTableView, I can't get the table cells to line up

If I use the RowExpander, I get the same issue

Open to suggestions

I'm writing a trading bot, so getting the buy/sell tables perfect for the viewer is key; as the bot is going to be automated. The user will keep an eye on it

Can the items of the TreeTableView be customised to appear with cells that line up? i.e. the title row and children all have a nice look?

A bit like this. Starting:

image.png

and then expand:

image.png

I have to maintain the order of the children too; but assumed I can have indexes in the elements to order by

Oh, i've just found this:

image.png

would work, which Edvin posted. I'll get reading. Maybe I can do what I need with TreeTableView

Many thanks @gtnarg You are right, going back to TreeTableView is exactly what I need to do.

I think the example in that article is probably what I need to achieve what I desire

@sp33dy - got it working. Did a few things that are more standard javafx. I added observable properties to your domain objects and a property extractor to your observableList so that the SortedFilteredList will respond to updates when that property (visible) changes on the underlying domain object in the list. This way the ui layer responds to changes in the underlying model. With plain domain objects that will not happen. I think you should still look at TreeTableView but wanted to show how to get it working the way you had written it.

@gtnarg Oh my, thank you! I will have a look shortly. Just got up and have to make the teas for the house 😞

Many many thanks. That does do what I required. I will continue exploring the TreeTableView and am learning from your example. I've also got to get my Comparator working to ensure the list is pre-ordered

This is an advance copy of a blog post I'm putting together. It shows how you can bring up View and Fragment through a variety of actions -- menu, keyboard shortcut, button -- as you would in a typical app. The emphasis is on parameter passing and communication.

Hey guys. One thing: I love the syntax of columns in table view:

column(...){}.cellFormat{}

Is there something similar for labels? I only find a way to add converters which is a bit cumbersome.

this is a video demo of the navigation code snippet posted above https://www.screencast.com/t/nR9G2DRzvw

Can anyone explain the "correct" way to replace code behind? Do you delegate everything to the Controller class instances, so any setOn looks like

setOnAction { controller.action(<args>) }

, or is it better to provide FXEvent and subscribe controller to the event bus:

setOnAction { fireEvent(ActionPerformedEvent) }

(which actually reminds of Qt signal/slot system, but with no direct coupling)? What are the advantages of each method and what are the use cases?

@alex - Direct delegation is probably the most common. I usually use the event bus in the opposite direction so that my controller doesn't access the view directly.

@alex The benefit to the direct controller call is simplicity. You can navigate from the control code to the button code easily in an IDE. Also, you can call a specific controller function and pass it specific parameters and handle specific exceptions. With the EventBus, things need to be generalized a little (parameters have to go in maps, exception handling is centralized). The biggest benefit to the EventBus is the decoupling. If you look at the example I posted earlier, I can call the same functions from multiple places. Grant's suggestion is very solid. Call controller methods but post back asynchronous results via the EventBus.

@jschneider Do you want to set just the text of the label or the graphics as well? When I just want the text, I'll usually create a stringbinding to represent the value I want. I usually deal with the graphics property the same way. Maybe there is a use case for a more direct cellFormat function, so that you can pass in any property you want, and instead of a converter, you can access the label and configure it as you want?

@jschneider Can you tell me more about your use case, a code example perhaps?