that's what I use the parameters for, fetching their data and assigning it to a VM

@User uploaded a file: Untitled

if there is a better way to do charts, I'd love to hear it.

@dr.fornax I think this example meets your requirements. I also pulled out "Phone" into a promptText rather than an actual value. Your problem was related to the terms of the editable flag. When you bound model.label and then called isEditable=true, you wiped out the model.label value with an empty value coming from the ComboBox (see the Javadocs). So, if you defer the binding, the value will be retained post-editable and the binding will work as you expect.

@nimakro commented on @edvin’s file : Well I think you are pretty fast, I know guys that didn't anything like that after a week 😉

@nimakro It sure was a lot of frustration. The machine was missing some parts and the documentation is poor. I got great help in the user's forum though, so now everything is working perfectly.

I will stop blabbing about keyboards soon, just want to show you this:

@carl Thank you very much 🙂 I will try to implement this in the afternoon. Since I have this contact elements for phoneNumbers but as well for email adddress, social contacts etc., I would like to put this into a kind of template and simply have a function that I can call and add this to the view. I therefore yesterday wrote a function and call it in the View but unfortunately it is not adding the entries. I read a bit in the tutorial and tried to find other examples for such a templating in edvins videos but have not found the solution. How would this be done correctly. There are always so simple things where I get a little bit stuck since the design patterns are not absolutely clear to me

@carlw Here is the code snippet I created yesterday. Maybe someone has an hint for me

@User uploaded a file: Contact Element

I still have to update it with your fix. I just tried to simply call it with “dynamicContactElement(“Email Adressen”, FontAwesomeIcon.ENVELOPE, contactModel.emailAddressModels, contactModel.emailAddresses, “Emailadresse”, “@”)”

I think I understand the main principle and that I have to give back some node, e.g. vbox and have to add it to root then, but I’m not sure about the recommended way. I have not seen any examples where someone did this, so I am not sure if this is the right way. The other way is a fragment, but I do not see the wa how to pass parameters

@edvin I will revert by your suggestion. @Ruckus we don't implement inc the way it should be implemented according to the documentation. https://kotlinlang.org/docs/reference/operator-overloading.html#increments-and-decrements If i read the documentation correctly, the inc and dec does not change the values globally. If we need to keep it in the way it is, so with changing the variable globally, I suggest to make another function called increment, where the value really changes globally and for inc and dec stick to the kotlin guide

@tieskedh This is a good point, and you saw first hand how confusing these operator functions can be. Should be remove them? @Ruckus

My seggestion, just stick to the Kotlin reccomendation. then it acts like expected for the operator. We can add a function increment, which increments globally.

@dr.fornax before i look at the refactored function...is everything working as far as displaying your value in the combobox's textfield and also adding any typed items back to the underlying items store?

@edvin How can I expand all the items of a treetableview by default? And is there any way to hide the headers of the treetableview?

@aayush You can call isExpanded = true on both the root and children

@User uploaded a file: Expand root and first level

And can I hide the table headers?

@aayush You can try with css:

.column-header { visibility: hidden; }

There might be an API for it as well, not sure/able to check right now.

Ohkk..Thanks 🙂

@tieskedh @edvin Hmm, that is a very good point. I see why that is the case, but it also seems somewhat counter-intuitive for properties. I think removing them would probably be a good way to go, but since it's a breaking change, I'd recommend deprecating them for a release or two before removing them.

@edvin I used this

.column-header{
    visibility: hidden;
}

And when I used this style on TreeTableView, the treetableview itself is getting hidden I then used

.column-header-background {
    visibility: hidden;
}

Which is now hiding every treetableview's header because the css class name is a global css class of the treetableview. How can i use this css specifically at one treetableview?

@Ruckus They were just introduced, maybe better to just rip the bandaid off? Not many will have started using them.

I didn't realize how new they were. Maybe a good idea then.

@aayush Add a class to that treetableview and include that class in the selector:

my-tree-table.column-header-background

@edvin was your fault, or ...?