This_is_the_Data_type_i_am_using_.kt

That sounds about right, so you must be doing something else wrong 🙂 Post a minimal runnable code sample 🙂

This_is_where_the_data_lives_.kt

The_View.kt

@iari Here's a demo app that updates the TableView when you change a domain object outfitted w. JavaFX properties

TableView_Updates.kt

Are you updating _i18nReferences? I'm not sure, but I don't think that will be reflected in the observable list (how could it?) Why do you keep a variable to a

MutableList<I18nReference>

? Why don't you just use the observable? After all,

ObservableList

implements

List

.

I am only updating i18References - the underscore version is just there for serialization

Are you changing the observable on the wrong thread?

using https://github.com/Kotlin/kotlinx.serialization - i have written serializers for some basic property types, but I have not yet been able to serialize an ObservableList<T> generically 😞

its all happening on the ui thread

mhh. I don't see where the problem is then. 😞 We might be able to help more if you could share something we can run ourselves

heres_the_function_that_changes_the_data_.kt

Yeah, Ill try to boil it down

it was the fault of the cellformat i used: i forgot to set teh text, duh I'm stupid!

That format didnt update as i expected it to, which is why I thought the content wouldn't be updated either

anyways still thanks a lot for the nice support - the code example helped a lot @carlw 😉

Hi all, can anybody let me know which strategy I should follow? I have a form that is driven by a combobox. I.E. Based on its selection, I need to show one set of two fields in a fieldset. Am I better off creating one fieldset and trying to hide the relevant fields or am I better of creating as two views and then switching between views based on combobox?

to help explain. I have a single XML object that describes EITHER a Database connection OR a REST call. Either is keyed off the type of Database or REST

Thus, it is one object stored, but I need two sets of forms. The directory has many of these entries and is due to a crappy client requirement.

For me, it depends on the overlap. If it's an address form, say CA versus US addresses, you might keep the same fields in the same place and use the combobox value to untangle which type of address you have. If the forms a really different, the different views will be better because they can be supported by specific ViewModels or Controllers.

They are different, i.e. a database requires a connection url, uid, pwd etc. A REST call has an http endpoint and parameters etc.

IF I go with the idea of a combo box that triggers one of two other views to show. My concern is how to model that. Would you put the Combo box in a view using a borderpane (top) and then link in the selected view into the centre (so it's positioned underneath). Will the labels etc line up as to look like one form?

These are some FXML / plain JavaFX links that toggle forms http://bekwam.blogspot.com/2015/09/javafx-binding-1-conditional-address.html https://bekwam.blogspot.com/2015/09/javafx-binding-2-subforms.html

This one might be of interest for your datasources

In TornadoFX, these would make use of functions like visibleWhen() or disableWhen() which would be bound to a particular condition, say the combobox value property == something

I had trying setting a simple observable boolean on selection of combobox and then use the whenVisible to show one set or another, but hit the problem that visible doesn't remove the component; i.e. the white space remains. Having a whenHide type solution would have been brilliant

only Hide() seems to truly hide the entire field (label and field form type)

have you tried removeWhen ?