| Shell setMaximized Problem [message #459950] |
Sun, 21 August 2005 00:18 |
 Terry Corbet
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
When I setMaximized (true) on the top level Shell of my application, the
result [on a W2K host] is 'full screen'. The entire Display surface is
painted.
If I maximize a typical application [presumably one built with some widget
tool kit other than SWT], its behavior is more *kind*. Let me explain
that my standard desktop is the ToolBar on left, which results in the
system tray in the bottom left corner of the Display. I get most of my
application launch buttons from the Office 2000 feature of Quick Launch --
it is still the most compact way to organize a large number of
commonly-accessed application icons to avoid the cumbersome use of
Start=>etc=>etc.
The *nice* behavior of the other applications is that when they are
maximized they will not over-write the QuickLaunch bar. Notice what I am
saying -- the software knows how to avoid overlaying. Yes, there is also
an 'Always On Top' option, but that is not in use, and not in play in the
solution to the problem. It is not that the other applications are 'just
lucky' that my QuickLaunch will over-write whatever space they consume --
they avoid space conflict. Indeed, a well-behaved, maximized application
responds to my moving the QuickLaunch. If I move it from the bottom of
the Display to the Right, the maximized application adjusts immediately.
So, certainly this is Window Manager behavior. Now, I see, and
understand, that what I am discussing falls under the caveat wisely
written that the SWT maximize and minimize behaviors must be considered as
'Hints", not as absolute, failsafe promises. Indeed, if I am reading the
source code correctly for Decorations, all that SWT does is pass the
SW_SHOWMAXIMIZED manifest constant to the OS. So, I guess it is axiomatic
that this is not a SWT bug. That is why I am not posting it as such. I
am just seeking clarification. Do all SWT applications become 'full
screen' when maximized or have I mis-configured something? [Another
possible answer might have been that W2K is just too old to worry about,
but the problem is being reported to me by a tester running on XP-Pro at
SP2.] If OS.SW_SHOWMAXIMIZED is the same mechanism that would be used in a
native application, I wonder why the result is not the same? This is not
'the end of the world', but I am getting strong push back from the user
community that says, "Sorry, nice try with your latest Java stuff, but it
still doesn't really work like a Windows application."
Thank you.
|
|
|
Powered by
FUDForum. Page generated in 0.03555 seconds
] 
Search
Help
Register
Login
Home
