Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog post comment is closed #3

Open
hajaUR1 opened this issue Feb 13, 2014 · 0 comments
Open

Blog post comment is closed #3

hajaUR1 opened this issue Feb 13, 2014 · 0 comments

Comments

@hajaUR1
Copy link

hajaUR1 commented Feb 13, 2014

Hi Steve,
First thing first, thanks for sharing such valuable material.
Your blog post commenting seems closed so sorry for this github channel.

A question remains though, with such architecture what is the cleanest way to customize the error message ?
Currently, and for sake of clarity, I understand that it's hard-coded in fxml. What I want to achieve is a builder-like :

screens.errorDialog().withMessage("custom warning message").withSeverity(Severity.WARNING).show()

Trouble is that I can update fxml dialog fields' only in controller(with @FXML), but latter is injected in FXMLDialog view on build time in ScreensConfiguration. I also want to re-use FXMLDialog for other kind of dialog.

Thanks in advance,
Cheers,
Ben

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant