Or example of ViewModel class for complex object

Sry for noob questions >_>

@thlinde The default behavior of JavaFX is to exit when the last window closes. You can control this behavior with

Platform.setImplicitExit(booleanValue)

@iLobanov Show us the code that's not working the way you think it should 🙂

@edvin It‘s the same behavior when I set implicitExit to true or false. In my thinking the modal window is not the last because the main window is shown under the modal window or I‘m not right? I use openInternalWindow. And to the version 1.7.14 with close() only the modal window closes and not the application, so I think ist should not be related to JavaFX.

@edvin here is simplified example of what I'm want

// DATA OBJECTS

data class Project(
    val id: Int? = null,
    val sender: Sender?
)

data class Sender(
    val id: Int? = null,
    val sensors: MutableList<Sensor>?
)

data class Sensor(
    val id: Int? = null,
    val measurements: MutableList<Measurement>
)

data class Measurement(
    val dataType: MeasurementType,
    val value: Double
)

...

// MDOELS

val Project.senderProperty: SenderModel
    get() = SenderModel().apply{
        itemProperty.bind(SimpleObjectProperty(sender))
    }

class ProjectModel : ItemViewModel<Project>() {

    val id = bind(Project::id)
    val companyId = bind(Project::companyId)
    val sender = bind(Project::senderProperty)

    override fun onCommit() {
        item = Project(
                id.value,
                companyId.value,
                null
        )
    }

}

...

//VIEW

class ProjectCardFragment: ListCellFragment<Project>() { 

	private val project = ProjectModel().bindTo(this)

	override val root = stackpane {  
		vbox {
			text(project.serialNumber)
			text(project.sender.serialNumber)
			text(project.sender.sensor[0].serialNumber)
			vbox {
				for(m in project.sender.sensors[0].measurments) {
					hbox { 
						text(m.dataType.toString())
						text(m.value.toString()) 
					}
				}
			}
		}	

}

@thlinde Are you sure you're not closing the main window and leaving the modal window? That would also close the application, as the default behavior of openModal() is to assign the same owner

@thlinde Try passing

owner = null

to the openModal() call

@iLobanov There are several issues with your code - can you supply a runnable sample? Will make it much easier to explain and clean up

I have the following function for mapping: inline fun <K, V, R> ObservableMap<K, V>.mapObserved(crossinline transform: (K, V) -> R) = map { (k, v) -> transform(k, v) } .observable().also { it.bind(this) { k, v -> transform(k, v) } } but is there a way to filter?

@edvin Can you give me some help how to use the parameter owner. In a menu/item I call openInternalWindow(view::class). In the button-close-Action from the dialog I call this@view.close().

@thlinde OpenInternalWindow doesn't actually open a new window, it's just an overlay inside the current window. If you do `this@view.close() you are probably targeting the owner window. Can you show me the code?

@thlinde There is a sample app showing how to use OpenInternalWindow in the framework test apps, actually.

@thlinde I just ran it, and indeed it exhibits the same issue you're describing, so it does look like there is a bug here.

@thlinde I committed a fix for it now, and I'll publish a new snapshot with the fix to oss.sonatype.org right away

For completeness, here is the sample app:

@edvin uploaded a file: Untitled

@edvin Thank you. I‘ll try it after you publishing the Snapshot

@thlinde you can try it right away using this link: https://jitpack.io/#edvin/tornadofx/-SNAPSHOT

It's also in sonatype now 🙂

Hey, thank you again. It works. 😁👍

@thlinde Thanks for bringing it up, nice to have it fixed 🙂

This question is very interesting: https://github.com/edvin/tornadofx/issues/660

Basically the guy wants to open a window and get some input, then use that input on close. There are so many ways to do it, but I wonder if we should provide some straight forward way to handle this.

@edvin This sounds like a plain Alert where you get the result. Optional<ButtonType> result = alert.showAndWait(); if (result.isPresent() && result.get() == ButtonType.OK) { formatSystem(); }

@carlw We could have something similar for UIComponent to support more complex values/situations perhaps

maybe this could look at something genericized? like an Alert<StructuredResult> which allows showAndWait() : StructuredResult

@carlw Yes. I don't want to add generics to UIComponent directly, but we could add a special UIComponent subclass that accepts a generic type argument for the return type, or something we can tack on an existing class. What I don't like about a special class with generic type argument is that we'd need two (to support View and Fragment) and that sucks 🙂

Will think about this today.

@edvin @carlw - isn't this what the javafx Dialog api does for you?