Issue 101310 - undocumented com.sun.star.awt.DisplayAccess
Summary: undocumented com.sun.star.awt.DisplayAccess
Status: CLOSED DUPLICATE of issue 83353
Alias: None
Product: documentation
Classification: Unclassified
Component: Manuals (show other issues)
Version: OOO310m9
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: smaug42
QA Contact: issues@documentation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 18:28 UTC by sos
Modified: 2009-04-24 09:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
How DiplayAcces can work (12.63 KB, application/vnd.oasis.opendocument.text)
2009-04-23 18:31 UTC, sos 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description sos 2009-04-23 18:28:26 UTC 
Ariel Constenla-Haile pointed me to the undocumented 
com.sun.star.awt.DisplayAccess.
Please make it Documented and think about using the more new service 
constructors - IMHO it has no sense to use css.beans.XPropertySet and 
css.beans.XPropertySetInfo in this case (all properties are read-only); so 
getter methods are better (and less error prone than css.beans.XPropertySet).

There may even be a code issue: WorkArea and ScreenArea return the same on 
Linux (tested on  Fedora 10 and Ubuntu Intrepid).
Comment 1 sos 2009-04-23 18:31:29 UTC 
Created attachment 61760 [details]
How DiplayAcces can work
Comment 2 smaug42 2009-04-24 08:58:53 UTC 
Investigating
Comment 3 jsc 2009-04-24 09:11:32 UTC 
jsc: seems to be a duplicate. Why the service doesn't make use of the new style
service constructors is unclear to me. Probably because it is context specific
to impress. For the new style constructors you would need an appropriate context
and that might be a problem here. I don't know the details here without further
investigation. But it should at least documented. 

*** This issue has been marked as a duplicate of 83353 ***
Comment 4 jsc 2009-04-24 09:12:55 UTC 
jsc: one further comment, this kind of issues are  better submitted as api or 
api -> sdk issues.