86260 – Monitor getBounds/getClientArea not accounting for task panel

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 86260 - Monitor getBounds/getClientArea not accounting for task panel

Summary: Monitor getBounds/getClientArea not accounting for task panel

Status:	RESOLVED DUPLICATE of bug 33659

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	SWT (show other bugs)
Version:	3.1
Hardware:	PC Linux-GTK

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-SWT-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-02-23 09:15 EST by Stef van Dijk
Modified:	2005-02-23 10:11 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stef van Dijk

2005-02-23 09:15:19 EST

My understanding is that Monitor.getBounds() should represent the size of the
display while the getClientArea() method is the amount of available space (for
example, minus the OS's taskbar).
This is not the case on GTK. The implementation is setting the client area to
match the overall bounds and is not accounting for the panel along the bottom
(assuming it's not set to autohide).
Note that maximize does the right thing and makes sure not to extend the window
over or behind the panel.

Comment 1 Billy Biggs

2005-02-23 10:11:33 EST

Maximize is easier because you just ask the window manager to maximize.  Getting
the client area requires that the desktop system (GNOME, KDE, whatever)
advertise it in some useful way.  The standard for getting this information
isn't as reliable as I would like, but definitely we can do better than what we
do now.

*** This bug has been marked as a duplicate of 33659 ***