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

Bug 334419

Summary: [LTTng] ControlFlow View alignment problem between table entries and Gantt
Product: z_Archived Reporter: Francois Chouinard <fchouinard>
Component: LinuxToolsAssignee: Patrick Tasse <patrick.tasse>
Status: CLOSED FIXED QA Contact: Francois Chouinard <fchouinard>
Severity: normal    
Priority: P3 CC: patrick.tasse, tonyj
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Bug Depends on:    
Bug Blocks: 301629    
Attachments:
Description Flags
Screenshot showing issue none

Description Francois Chouinard CLA 2011-01-14 15:05:09 EST 
When the Control Flow View was implemented, it was estimated that it would be much more complex to extend the original widget to support multi-column than to just "paste" a multi-column table the original single-column widget. 

This worked well when using GNOME/GDM (Ubuntu) but was the source of an alignment problem when KDE and/or KDM were used (Debian). Initial investigation pointed at SWT which was not reporting the correct cell height in all cases. So a small tweak was introduced to cover for the known cases cases.

This problem surfaced again with the following conf:
metacity-2.30.1-2.9.x86_64   window manager
gdm-2.30.2-6.1.1.x86_64      display manager

This is still GNOME/GDM (likely Suse) so it seems that the original diagnostic was not correct.

The ideal solution would be to extend the original widget to support multi-column. This would solve the alignment problem once and for all.
Comment 1 Tony Jones CLA 2011-01-18 21:30:37 EST 
Created attachment 187070 [details]
Screenshot showing issue

Attached screenshot.  Any estimate on fix date?
Comment 2 Francois Chouinard CLA 2011-01-19 13:16:41 EST 
(In reply to comment #1)
> Created attachment 187070 [details]
> Screenshot showing issue
> 
> Attached screenshot.

Thanks!

> Any estimate on fix date?

We don't have any estimate yet, sorry. We definitely want to have it fixed for 1.0 (next June) but I can't tell you now when it will actually be ready.
Comment 3 Patrick Tasse CLA 2013-05-21 15:17:14 EDT 
Fixed with commit 2e6975cb87a439984820e65f4c3d375f9b85bcd3

Released in 1.0