@ron That's exactly how I hoped people would feel 🙂 I think it will solve many use cases.

one of the tickets I have is to implement a toolbar in it

can one drop the two arrows ?

@ron Yes, you can disable the arrows, and it's possible to set the viewstack depth to 0

not just disable, remove them 🙂

@ron I'm committing

Workspace.disableNavigation()

which will remove them. You can also manually set the

maxViewStackDepth

property to 0 and they will disappear.

@ron Sorry about the wait, busy here today. I've committed it now. This is how my CRM workspace looks with it:

@User uploaded a file: Untitled

will that only remove the arrows?

It also removes the whole view stack pushing thing.

It doesn't remove the save / refresh buttons.

good

adn it will be easy to add buttons

Very. If you want buttons that look the same as the integrated onces, do

addClass("icon-only")

on the buttons you provide. If you then set the graphic to an icon it will look just like the default ones. You can also change their icon with css, check out the `workspace.css`:

@User uploaded a file: Save icon is defined like this

So if you add the same selector with a different shape, you're good to go.

hmmz I thought you used awesome icons for them 🙂

No, these are taken from here: https://materialdesignicons.com/

good to know

Search for an icon, choose the

</>

dropdown and choose

View SVG

. From there you can extract the path of the icon you want.

To use such icons for your own buttons you would do:

button("My button") { addClass("icon-only"); graphic = graphic = label { addClass("icon", "myicon") } }

Then have

.workspace .header .icon.myicon

in the css file with the correct

-fx-path

@ron Thank you, it's important we get some feedback like this so we can support as many use cases as possible out of the box.

well I want the keepassFX ui to be an absolute showcase of what tornadoFX can do

(which is why I am so not happy with it at the moment (again!))

the builderInternalWindow is good and implemented but I am still fighting with the syncing of the views when a new file is opened

@thomasnield Remember also that since the

cellDecorator

runs for every cell, even those that currently has no value, you need to check if you have a value before calling

rowItem

. Something like

textFill = if (it != null && rowItem.model.lastName.isDirty) Color.RED else Color.BLACK

Meaning, you can't call

rowItem

when there is no cell for it. Maybe it should have been nullable, but then it's not so nice to use from

cellFormat

.

@thomasnield I can make a dirtyStateTracker that would require a lot less memory, will do it tonight 🙂

dirtyStateTracker for the tableview?