Bugzilla – Full Text Bug Listing
| Summary: | monitor.getClientArea reports too large value on Linux | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Thomas Singer <eclipse> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | arunkumar.thondapu, ericwill, Silenio_Quarti | ||||
| Version: | 4.3 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
I can't reproduce this issue, is it still a problem Thomas? I can't reproduce the problem on Fedora 28. (In reply to Thomas Singer from comment #2) > I can't reproduce the problem on Fedora 28. I'll close it then, please re-open if you experience the bug again. |
Created attachment 227183 [details] Sample When I run the attached sample on a Ubuntu 12.04 default installation with a dual monitor system (1366x768 notebook and external 1920x1200 HDMI), it returns too large values for getClientArea: Monitor count: 2 bounds: Rectangle {0, 0, 1920, 1200} clientArea: Rectangle {49, 24, 3237, 1176} bounds: Rectangle {1920, 0, 1366, 768} clientArea: Rectangle {1920, 0, 1366, 768} IMHO, the clientArea never must be larger than the bounds.