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

Display the reason why the buttons are disabled #280

Closed
ilg-ul opened this issue Feb 16, 2018 · 4 comments
Closed

Display the reason why the buttons are disabled #280

ilg-ul opened this issue Feb 16, 2018 · 4 comments
Assignees
Milestone

Comments

@ilg-ul
Copy link
Contributor

ilg-ul commented Feb 16, 2018

The debug plug-ins disable the Apply button if the configuration is incomplete.

If possible, it would be better to also display the reason.

@ilg-ul ilg-ul self-assigned this Feb 16, 2018
@ilg-ul
Copy link
Contributor Author

ilg-ul commented Apr 3, 2018

All TabDebugger classes call setErrorMessage() when isValid() returns false.

@ilg-ul
Copy link
Contributor Author

ilg-ul commented Apr 3, 2018

Fixed on 2018-04-03.

@ilg-ul ilg-ul added this to the v4.3.3 milestone Apr 3, 2018
ilg-ul added a commit that referenced this issue Apr 4, 2018
- in TabDebugger, call setErrorMessage() when isValid() returns false
- fix log message when numeric fields are empty
@ilg-ul
Copy link
Contributor Author

ilg-ul commented Apr 5, 2018

The 4.3.3.201804051758 pre-release is now available for testing from http://gnu-mcu-eclipse.netlify.com/v4-neon-updates-test.

@ilg-ul
Copy link
Contributor Author

ilg-ul commented Apr 19, 2018

Fixed since 4.3.3.201804191501.

@ilg-ul ilg-ul closed this as completed Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant