Oh. Let me try that.

Shoot. That did work techincally, but I did not realize the sorters physically modified the backing

ObservableList

I guess what I could do is I call that

getSortOrder().clear()

and then reset the "natural" order of the backing

ObservableList

.

So I think that solved that problem for me. Thank you!

np

It isn’t really clear to me what you’re meaning, btw

when you change the sorting, you’re modifying the sort order list

when you change between ascending / descending, you’re modifying the property on the table column

I’m not clear what you mean by ‘natural order’ - I’m guessing you mean the order of the items list?

Yeah I meant manually putting the items back in an arbitrary order that I've deemed to be the natural order, and I do that manually.

ok

Thank you for clarifying though

Did some investigating around TableView column resizing yesterday, and I think we can do everything we need to just by supplying a custom columnResizePolicy. I will start with support for pref width, content-based width, weighted with and percent-of-total, and remaining-width. I have found a nice way to store the column resize preferences as well.

@thomasnield I'm also working on the TableColumn preference metadata thing, so you can save information about sort order and column order per View and have it automatically restored. Both these features will go in 1.5.6, and then we'll do a release. We have a pretty nice feature set for this release now.

@thomasnield I also think I finally nailed the typeless column parameter headache: https://github.com/edvin/tornadofx/issues/163

Basically, if you don't want to muck with types, you can define a table column like this:

@User uploaded a file: Untitled

If the object returned from

value

is not an

ObservableValue<*>

it is wrapped in a

SimpleObjectProperty

. Since you have access to the

TableColumn

as

this

you can do whatever you want in there. I think this should cover your "ad hoc" use case @thomasnield 🙂

I like the

value { it.value.name }

concept, let the developer decide if he wants to make that value observable or not

would it support

column("name") { value = { it.value.name}}

@ron Yeah, and still the greatest value (pun indented) is that you don't need to specify the type. Type type of

it.value

is derived from the TableView type parameter. The trade off is that the second type parameter to TableColumn will be

Any?

. It is very rarely needed, and if you do, you can define your column as

column<Customer, String>("Name") { it.value.nameProperty }

@ron Unfortunately not. This would be a platform type clash with the column builder I mentioned above.

ok

I just committed

Improved TableView.rowExpander with lessons learned from the ControlsFX port

. Having the main JavaFX guy review your code is pretty valuable 🙂 We should do this more often... haha 🙂

btw that code I am working on is on github, if you cant wait to look at it 😉

I realized yesterday that I need to see if tornadofx already has something to work with background tasks and progressbars

@ron Great, I will get to it, but first I want to play with SmartColumnResize(TM). I couldn't sleep last night because I was dreaming of this feature!

not like the

async { } ui { }

there is no hurry

basically I have a long running task (Scanning directories) that I will run in the background with an indeterminate progressbar