After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 320640 - Preferences in gnopernicus magnifier do not always retain their values.
Preferences in gnopernicus magnifier do not always retain their values.
Status: RESOLVED FIXED
Product: gnopernicus
Classification: Deprecated
Component: magnifier
unspecified
Other Solaris
: Normal critical
: ---
Assigned To: Dragan Sarbut
Dragan Sarbut
AP1
Depends on:
Blocks:
 
 
Reported: 2005-11-03 18:15 UTC by Vincent Quigley
Modified: 2005-12-06 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
proposed patch (610 bytes, patch)
2005-11-04 11:34 UTC, Dragan Sarbut 		committed Details | Review

Description Vincent Quigley 2005-11-03 18:15:50 UTC 
Set up system for use with gnopernicus magnifier.
Edit the preferences so that you get full screen magnification with source as
0.1 and target as 0.0.
Once full screen magnification has been established log out and back in again
and start gnopernicus.  The preferences previously set by user have been
overlooked and magnifier is only on left hand side of screen.
Comment 1 Vincent Quigley 2005-11-03 19:42:52 UTC 
Bug is also being tracked in Sun's internal bug database: CR# 6340786
Comment 2 Dragan Sarbut 2005-11-04 11:34:50 UTC 
Created attachment 54310 [details] [review]
proposed patch

This patch should fix the problem. 
At initialization time, after gnopernicus reads the values from gconf, tries to
validate them. There was a small bug in the validation. Please apply the patch
and tell me how it works.
Comment 3 Dragan Sarbut 2005-11-04 11:39:46 UTC 
I tested with a 1024/768 resolution and it works OK for me even after I log out
and back in again
Comment 4 Dragan Sarbut 2005-11-22 10:36:23 UTC 
Patch commited to CVS HEAD.
Closing bug...
Comment 5 bill.haneman 2005-11-22 11:58:31 UTC 
Vincent, does this bug only manifest if you use the maximum resolution values
for fullscreen magnification?  For instance on a 1024 x 768 screen, does it work
OK with 1023 by 767?

If not, then I think there is still a problem which this patch does not address.
Comment 6 Vincent Quigley 2005-12-06 17:24:35 UTC 
Sorry for the late reply:
Yes the bug only seems to come up when the maximum values are set.