Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340423 - Auto-size of the AUT-configuration dialog leads to non-visible button bar
Summary: Auto-size of the AUT-configuration dialog leads to non-visible button bar
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-18 09:15 EDT by Markus Tiede CLA
Modified: 2013-11-19 09:26 EST (History)
1 user (show)

See Also:

Attachments
Dialog Size (40.56 KB, image/png)
2011-03-18 09:15 EDT, Markus Tiede CLA 		no flags Details
View All 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 Markus Tiede CLA 2011-03-18 09:15:21 EDT 
Created attachment 191503 [details]
Dialog Size

The auto-size of the AUT-configuration dialog leads to non-visible button bar if a low screen resolution is used (in my case 1024 x 768) - see attachment.
Comment 1 Zeb Ford-Reitz CLA 2011-03-18 11:34:06 EDT 
This isn't as easy to fix as I thought it would be. The problem is that we resize the dialog shell during dialog instantiation (long before creation), and org.eclipse.jface.window.Window (which org.eclipse.jface.dialogs.Dialog extends) pays close attention to whether the shell was resized. If yes, then it doesn't perform the standard bounds calculation and assignment (which makes sense, because the framework shouldn't be messing around with the position and size that we so painstakingly assigned).

After spending some time trying to fix this particular issue, I think I'd rather see a drastic UI change for AUT Configuration. I'm not especially fond of the fact that the dialog resizes itself based on which mode is currently in effect, and I'm pretty sure that removing that functionality would solve the problem described in this bug report.

I'm moving this to Indigo M7 pending further discussion.
Comment 2 Zeb Ford-Reitz CLA 2011-05-05 03:59:46 EDT 
This won't be done for M7. Resetting assignee to default because I won't be working on this bug in the near future, and someone else might want to take a crack at it.
Comment 3 Alexandra Schladebeck CLA 2013-11-19 05:46:18 EST 
Resolving this as wontfix.
Comment 4 Oliver Goetz CLA 2013-11-19 09:26:17 EST 
Closed due to comment 3.