Bug 119499 - "Configure KStars" settings changes do not cause immediate redraw upon "Apply" or "OK"
Summary: "Configure KStars" settings changes do not cause immediate redraw upon "Apply...
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kstars
URL:
Keywords:
: 119507 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-01-04 14:22 UTC by Shriramana Sharma
Modified: 2008-06-22 00:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shriramana Sharma 2006-01-04 14:22:32 UTC
Version:           1.2.0 (using KDE 3.5.0 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15-smp

Steps to reproduce:
1. Load KStars
2. Goto Settings > Configure KStars
3. Change any setting. For example, switch off the Hipparchos catalog.
4. Hit Apply or OK.

Actual Result:
The settings are not immediately applied. (The stars do not disappear.) They are applied only after a redraw is manually caused by the cursor keys or other input.

Expected Result:
The settings should be immediately applied. (The stars should disappear.) This is the meaning of "Apply" and implied meaning of "OK". A redraw should be implemented immediately when the "Apply" or "OK" button is pressed in the settings dialog.

Comment:
This bug should be simple enough to fix. Just call a redraw function when the Apply or OK button is pressed. (I am only now learning Qt programming else I would contribute this fix myself.)
Comment 1 kstars 2006-01-04 17:45:57 UTC
*** Bug 119507 has been marked as a duplicate of this bug. ***
Comment 2 kstars 2006-01-23 21:23:50 UTC
Yes, this bug has existed ever since we adopted the KConfigXT paradigm.  We'll try to get it fixed for 4.0.
Comment 3 Akarsh Simha 2008-04-16 18:21:06 UTC
This bug seems to have been resolved and should probably be closed.
Comment 4 Bram Schoenmakers 2008-06-22 00:49:09 UTC
Indeed, this is fixed in the meantime.