Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 552316 - In place table cell editing does not work in 4.13 on Linux (Fedora 29)
Summary: In place table cell editing does not work in 4.13 on Linux (Fedora 29)
Status: RESOLVED DUPLICATE of bug 550606
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 06:28 EDT by Mattias Bertilsson CLA
Modified: 2019-10-22 06:33 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mattias Bertilsson CLA 2019-10-22 06:28:09 EDT
For instance, clicking the green plus and "Add new expression" text in the Expressions view table in the Debug perspective will result in nothing. You can add expressions by using the action in the toolbar and following dialog, but you don't seem to be able to edit an existing expression.

The problem is not limited to that view, it occurs in other views, including the Registers view, and probably most other tables. Oddly enough, it works in one table in the product I working on, but not others.

It seems to be a problem rendering the cell editor UI. If you type some characters and then press tab, after having clicked the cell, the characters do appear in the cell, but there is no hint that it was ever editable, and you can't see the characters as you type.

It works fine in Eclipse 4.12 on the same machine with the same GTK versions:

org.eclipse.swt.internal.gdk.backend=x11
org.eclipse.swt.internal.gtk.theme=Mint-X-Aqua
org.eclipse.swt.internal.gtk.version=3.24.1

org.osgi.framework.os.name=Linux
org.osgi.framework.os.version=5.2.18.fc29
org.osgi.framework.processor=x86-64
Comment 1 Paul Pazderski CLA 2019-10-22 06:33:15 EDT
Should be fixed in 4.14M1.

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