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 481009 - magnifier should expose "full-screen capable" property to bonobo clients
magnifier should expose "full-screen capable" property to bonobo clients
Status: RESOLVED FIXED
Product: gnome-mag
Classification: Deprecated
Component: API
0.14.x
Other All
: Normal enhancement
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks: 467664
 
 
Reported: 2007-09-27 16:10 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2007-10-14 20:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20

Attachments
Proposed patch (2.66 KB, patch)
2007-10-08 19:13 UTC, Carlos Eduardo Rodrigues Diógenes 		committed Details | Review

Description Joanmarie Diggs (IRC: joanie) 2007-09-27 16:10:58 UTC 
When an Orca user attempts to enable full screen magnification on a single-head machine that does not have the composite extension enabled, the screen "blanks out".  Therefore Orca -- and potentially other clients -- should attempt to prevent the user from enabling full screen magnification under these conditions.  For the purpose of doing so, it would be quite handy were magnifier to expose a property to inform clients whether the system is "full-screen capable" or not.  Perhaps this could be added to the property bag?

Thanks!
Comment 1 Carlos Eduardo Rodrigues Diógenes 2007-10-08 19:13:41 UTC 
Created attachment 96898 [details] [review]
Proposed patch

See if this is sufficient for you needs Joanmarie.
Comment 2 Joanmarie Diggs (IRC: joanie) 2007-10-09 21:16:15 UTC 
So far so good!  Still experimenting and testing, but this is looking quite promising.  Thanks VERY much!
Comment 3 Joanmarie Diggs (IRC: joanie) 2007-10-10 00:54:47 UTC 
Carlos, I think it's good.  Thank you again.
Comment 4 Carlos Eduardo Rodrigues Diógenes 2007-10-14 20:56:26 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.