@edvin Will have a look here in a few minutes.

@kastork Great.

@edvin looks good as far as it goes. I'm only using

String

and

Boolean

values.

@kastork OK. I covered a lot more use cases than earlier, and hopefully I didn't mess anything up.

It smoothly handles the case where an optional field is not there, which is great

Good.

Now we need the same thing for YAML 😉

Bah.. installed Windows Creators Update and it bricked my computer. Everything is blank after login. Seems to have something to do with the NVIDIA driver.

I was about to make a screencast, but now I can play with this instead.

I did it on two computers at once, so now I'm anxiously waiting to find out if I bricked them both 😁

The laptop survived 🎉

what's the pattern when you want to present a modal with a number of buttons and then act based on which button closed the modal? Typical "continue or cancel" kind of scenario?

opening the modal with a fragment is easy enough, but getting the response in the parent that opened it isn't clear to me

@edvin Sorry but I have to say it #linuxRocks 🙈😜

@User uploaded a file: seems clunky and error prone

Since you actually want to wait with navigation until the dialog is closed, this one way to do it, and in my opinion, not that clunky. You could however return false at once, and then just do the navigation in the buttons for this particular use case.

I like your approach better. What feels error prone about this?

@edvin using the value from the dismissed fragment

I guess since it is modal, there's little chance of problems

Zero, since it's blocking.

You would add a function to the

ConfirmUnsaved

fragment and do:

override fun onNavigateBack() = find(ConfirmUnsaved::class).confirm()

confirm

would do

openModal

and then return

result

.

that's appealing, let me try that,

@kastork I just added

Workspace.navigateBack()

and

Workspace.navigateForward()

in case you want to do this non blocking instead.

You would then basically show the confirm fragment and return false immediately in

onNavigateBack

. Then your

Continue

button would do

workspace.navigateBack(); close()

and you can remove the

result

property.

evening chaps

Good evening Mike 🙂

do any of you have any small, simple command line tools that you'd like me to try turning into standalone mac binaries?

i'm looking for test stuff. no guis right now please

@edvin seems a nice approach