then why not just

build....

buildWindow

,

buildFragment

@gtnarg @edvin Oh, thanks.

`ignoreDirtyStateProperties`works perfectly 🙂

@permalmberg It shouldn't be needed for

autocommit

of course. I've found and fixed the error, will commit it later tonight 🙂

@ron Seems like the overlay was not added to the root?

@edvin Yes, but now I can test that my my logic works as expected 🙂 btw, got an eta for 1.5.10 ? 🙂

@permalmberg I was going to release before this weekend, then I started this grand Workspace thing. It will be next week for sure though.

I might add the Workspace as an experimental feature without guarantees of backwards compatibility, so it can be tested for more use cases before we go all in with that.

It's totally optional, so it will not interfere with anyone's existing stuff, and the whole thing is 150 lines.

@edvin sounds like a plan. put it in an `experimantal`package, makes it obvoius

The strange thing is that the primaryStage jumps back to its initial size

Good idea.

@edvin it happens constantly

@ron Weird. We'll figure it out, but now I'm working on testing the Workspace.

no rush

@ron Are you on board with renaming the adhoc window stuff to builderWindow?

sure I still have it open

build or builder?

builderWindow

. I'll have to make some adjustments here before I merge, will let you know. I've made a git-mess today 🙂

grins it can happen

that is why I usually do stuff like this on a branch

I should have. Not used to it + lazy

@carlw You saved us there with the naming suggestion 🙂

@edvin I would have mentioned it sooner, but I didn't have time to look over the code and see what the adhoc difference was exactly.

@carlw Glad you did 🙂

its pushed

btw the buttonbar in the form is excellent and the Pos.BaselineRight works like a charm

It's going to take me several hours to integrate the Workspace into my CRM. I want to try it there because it will reveal a few corner cases.

@ron That was a nice suggestion on your part. Very happy for it!