Sorry, but this PR as well as your other has several additional commits that are not part of what you are proposing. Please open a new, clean PR.

My personal opinion is, that I wouldn't want to have this feature. When weighing the benefit of this new feature and the cost by adding more parameters, I would vote to not include this.

As already said in the original PR, I'm not a big fan of the button to save the params. Imho it only makes code a lot more complicate and may confuse the user which likely expects the setting to be for himself only, when it's in fact for all users.
If we want to add new params they should be in the configuration page, and not as a button in the list itself.
Also, adding component specific code into a JLayout looks strange to me. It sort of defeats the purpose of JLayouts.

So please either update this PR with a solution which addresses those issues, or close this one and create a new one.

Sorry, but this PR as well as your other has several additional commits that are not part of what you are proposing. Please open a new, clean PR.

Hi!
My first Pr were processed with my git client, giving in fact too many problems. Since, my lastest PR are much more clean!
Really sorry for inconvenience, and thank you to forgive a "newbie" in contribution! ;)

My personal opinion is, that I wouldn't want to have this feature. When weighing the benefit of this new feature and the cost by adding more parameters, I would vote to not include this.

So please either update this PR with a solution which addresses those issues, or close this one and create a new one.

Thank you for your advice and opinions!
I closed this PR, and when a little time, will work on a better advanced solution to integrate this possibility inside core, or by a third party extension...
The opinion of seasoned contributor is most interesting!

Best Regards,
Cyril