François Martin

Thanks for your comment! During the implementation, we thought of PreferencesFX being the central and only place where these values would be influenced, hence why we didn't think of this....

Hi @trixon This is actually a use case we didn't think of, but it makes sense! Actually I think with the current implementation of PreferencesFX, yes, your solution is probably...

Interesting... Actually, then I could imagine a way we could do this is to postpone the initialization of the GUI elements (essentially in `PreferencesFx.init()` everything after `preferencesFxModel.loadSettingValues();`) to only run...

Hi @Naoghuman, I think we don't have it there since there is now a feature on Github to define the license. If you have a look at the "Code" tab...

The project files are consistent - in a way that the license header included in the files taken and modified from the FormsFX project is kept. I think if we...

Hi @aang7 I see what you mean - currently we don't have support to persist and load settings without having them shown in the GUI as well, is that what...

@aang7 Concerning your first comment on how to start: As mentioned above, I would first add a method to `PreferencesFx` where you can pass global settings to be saved. Then,...

Concerning the second thing you mentioned: We didn't foresee people wanting to use PreferencesFX as a node in a new window, which is why an exception gets thrown in this...

Here I have the same answer as I wrote in #23, feel free to implement if you want and submit a PR!

100% agree on this. We discussed this already before making PreferencesFX public and due to the limited time we had, we decided to not implement it in favor of other,...