Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339740 - [Perspectives] Examine the layout behavior
Summary: [Perspectives] Examine the layout behavior
Status: CLOSED DUPLICATE of bug 416845
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-11 13:15 EST by Eric Moffatt CLA
Modified: 2015-08-04 08:36 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2011-03-11 13:15:55 EST
While fixing bug 339737 I noticed that we have far too many places where we are directly forcing a layout. We should go over these to see how many we can make part of the standard rendering behavior...
Comment 1 Eric Moffatt CLA 2011-03-11 13:16:26 EST
Changing milestone to look at this in M7.
Comment 2 Dani Megert CLA 2013-06-05 10:57:19 EDT
Removing outdated target milestone.
Comment 3 Eric Moffatt CLA 2013-06-06 11:53:10 EDT
I'm marking this for a look in 4.3.1 (perhaps 4.4?) in order to see if we can address an outstanding issue in the JDT being caused by the use of the SWT.Defer layout flags...

Dani, do you remember the defect I'm talking about (it's the one causing your current 'focusHack' implementation.
Comment 4 Dani Megert CLA 2013-06-10 10:39:48 EDT
(In reply to comment #3)
> I'm marking this for a look in 4.3.1 (perhaps 4.4?) in order to see if we
> can address an outstanding issue in the JDT being caused by the use of the
> SWT.Defer layout flags...
> 
> Dani, do you remember the defect I'm talking about (it's the one causing
> your current 'focusHack' implementation.

Yes, it's bug 375576.
Comment 5 Eric Moffatt CLA 2013-06-10 15:54:31 EDT
Thanks...
Comment 6 Dani Megert CLA 2015-08-04 08:36:55 EDT

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