Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356403 - ENTER key does not activate the cell editor when the table is read only
Summary: ENTER key does not activate the cell editor when the table is read only
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 16:13 EDT by Marcelo Paternostro CLA
Modified: 2021-11-19 09:22 EST (History)
1 user (show)

See Also:


Attachments
RCP app showing the reported problem (29.06 KB, application/zip)
2011-08-31 16:13 EDT, Marcelo Paternostro CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Paternostro CLA 2011-08-31 16:13:17 EDT
Created attachment 202564 [details]
RCP app showing the reported problem

Scenario:

- In the Sapphire definition file, add a "read.only" hint to a Properties Editor and set it to "true".
- Make sure a writable property is added as a "Child Property" of the properties editor above
- Populate the model and pass it to a Sapphire dialog

As expected, double clicking the cell activates the cell editor, allowing the user to change the contents of the property. However, selecting the table's row and hitting ENTER does not activate the cell editor (it closes the dialog, if the OK button is enabled). Setting the "read.only" hint to "false" fixes the problem.

The same happens when the table is used via a SapphireControl, in a view for example.

I am attaching a RCP application example that illustrates the problem. It has its own launcher.
Comment 1 Konstantin Komissarchik CLA 2011-09-01 16:41:51 EDT
Fixed in 0.3.1 and 0.4 streams. Please verify.
Comment 2 Konstantin Komissarchik CLA 2011-09-20 14:37:09 EDT
Marcelo, could you verify this bug so that we can close it? Thanks.
Comment 3 Marcelo Paternostro CLA 2011-09-21 15:24:41 EDT
Thanks.
Comment 4 Konstantin Komissarchik CLA 2011-09-21 15:55:17 EDT
Closing. Thanks.