Red Hat Bugzilla – Bug 838871
Apply button is always clickable
Last modified: 2012-08-09 19:27:02 EDT
Description of problem:
This behavior mislead that the changes may be not applied.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Apply button is clickable regardless of something is changed.
it should be reflected according to the current status
I have remove the "Close" button and change "Apply" button to "OK"
The "OK" button will show a pop up window to warn that changes will write to configuration file, when there is changes. The changes include add/remove one language to/from list, or remove all the language.
If there is no changes, press "OK" button just close the window.
I will include this change in new release 0.0.7.
fonts-tweak-tool-0.0.7-1.fc16 has been submitted as an update for Fedora 16.
fonts-tweak-tool-0.0.7-1.fc17 has been submitted as an update for Fedora 17.
I can still see this issue on Fonts tab with 0.0.7-1.fc17.
FWIW it looks like the dialog-wise window though, embedding the dialog buttons into the tab looks a bad idea.
I'm wondering if I should open another bug but it may be related to this. so just add a comment here.
Well, due to the thing as I mentioned in the above comment, if one do the following steps, the changes will be missed:
1. Add a language on GTK Language Order tab
2. Switch the tab to Fonts
3. Click the close button
As I told you on IRC, you better consider to use "instant apply".
fonts-tweak-tool-0.0.8-1.fc17 has been submitted as an update for Fedora 17.
fonts-tweak-tool-0.0.8-1.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fonts-tweak-tool-0.0.8-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fonts-tweak-tool-0.0.8-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.