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

Bug 341943

Summary: [expr] Cheese in the Expressions view
Product: [Eclipse Project] Platform Reporter: Michael Rennie <Michael_Rennie>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: grant_gayed, pawel.1.piech, remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
screen shot
none
screencast of the problem none

Description Michael Rennie CLA 2011-04-05 12:29:01 EDT
Created attachment 192576 [details]
screen shot

Version: 3.7.0
Build id: I20110405-0800
Ubuntu 10.10 64bit OS / Eclipse

Steps:

1. create a watch expression
2. mouse away to a different view / area
3. select the new expression to edit it
4. without clicking again move the mouse out of the edit cell to the right to hover over the Value cell

Happens:

you get a double over-lay of the expression offset a bit

Expected:

nothing happens
Comment 1 Pawel Piech CLA 2011-04-05 15:12:27 EDT
I'm not able to reproduce on Utuntu 10/32bit.  Could this be a 64-bit specific thing?  Either that, or I'm not following the steps correctly.
Comment 2 Michael Rennie CLA 2011-04-05 16:23:51 EDT
(In reply to comment #1)
> I'm not able to reproduce on Utuntu 10/32bit.  Could this be a 64-bit specific
> thing?  Either that, or I'm not following the steps correctly.

Not sure what more I can say, select a watch expression to edit it (so it enters the edit mode of the cell) and then move the mouse right until over the Value cell, thats pretty much it. 

I can try debugging it if you are having trouble reproducing it.
Comment 3 Michael Rennie CLA 2011-04-05 16:44:31 EDT
additional steps:

1. select the 'Add new expression' element so editing starts
2. mouse to the right over the Value cell
3. notice 'Add new expression' blinks on in the cell
Comment 4 Pawel Piech CLA 2011-04-05 17:10:39 EDT
I don't see it in any of these, and unfortunately I don't have the hardware right now to install a new OS on.  It's odd, because there shouldn't be any cell editor activating for the value column.
Comment 5 Michael Rennie CLA 2011-04-06 11:13:20 EDT
Created attachment 192650 [details]
screencast of the problem

Here is a screencast of the problem.

I tried debugging the problem, but could not find any place when a focus listener was being called and causing something like this.
Comment 6 Michael Rennie CLA 2011-04-06 11:15:01 EDT
CC'ing Grant, perhaps this is an SWT issue?
Comment 7 Grant Gayed CLA 2011-04-06 11:41:46 EDT
It looks like the string in black does not match the string in white below it (the black string is surrounded by quotes).  Is there custom draw being used here, and the client is drawing a different string than that which is set in the TableItem via setText()?  Which string is "correct", the one with the quotes or without?
Comment 8 Michael Rennie CLA 2011-04-06 11:58:08 EDT
(In reply to comment #7)
> It looks like the string in black does not match the string in white below it
> (the black string is surrounded by quotes).  Is there custom draw being used
> here, and the client is drawing a different string than that which is set in
> the TableItem via setText()?  

I don't know of any custom drawing in debug, we delegate the cell editing widgetry  to TextCellEditor from JFace.

>Which string is "correct", the one with the
> quotes or without?

When the cell has focus - i.e. being edited - the non-quoted string is correct.
Comment 9 Lars Vogel CLA 2019-11-14 03:53:58 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.