@ron I don't really buy his argument, so if you'd like to implement it inside app.xml that's fine by me.

@permalmberg Do

isFitToWidth = true

on the scrollpane.

I wonder why the

ScrollPane

fitToWidth and fitToHeight are false by default. Should we add those parameters to the

scrollpane

builders, and if so should we change the defaults?

I just realized why those are false by default. I'm adding them to the builder but I'm keeping the default value of false.

Committed a version with those params.

@edvin it breaks the API for existing fxlauncher users and I am not very enthusiastic about it let me think some more about it

@ron We should try to find a way to not break the API.

That should be possible IMO 🙂

I have an idea but I need to work it out a bit

OK, no rush 🙂

@gtnarg

contentWidth()

simply doesn't look for nested columns. I'm looking at it now.

@gtnarg I've committed a fix that lets SmartResize.POLICY ignore parent columns and operate on nested columns. There might still be corner cases where it doesn't perform as intended, so it would be great if you can test it with your use case.

I'll go ahead and release 1.6.2 now.

@edvin - that fix doesn't seem to work

@gtnarg Do you have some code I can run?

@User uploaded a file: PojoTableColumns.kt and commented: All I did was add 'resizeColumnsToFitContent'. Am I using the api correctly?

@edvin That was too easy. I feel ashamed now 😛

@permalmberg Hehe 🙂

@gtnarg I see. I fixed the wrong thing 🙂 I fixed nested column support in SmartResize.POLICY. Hehe.. Checking this out now.

@edvin - sorry I should have provided more information with the original post...

@gtnarg Actually, very glad that you didn't because now I get to fix both issues 🙂

I just tripped across it when testing my PR yesterday

I have fixed the issue now, committing...

It will be in 1.6.2, starting release procedure now.

@edvin - try adding it to PojoTreeTableColumns.kt as well - it's not working there...

@gtnarg Thanks, fixing now.

Fixed 🙂

Will add it to PojoTreeTableColumns now

What's the preferred way of storing application settings these days? It is still a

.properties

file? Does TFX provide magic for this too?

@permalmberg Yeah, we have lots of magic. Every Component has a

config

property where you can set key value settings and call save to persist. There is also a

preferences

property which us backed by the Windows Registry or Plist on Mac.