Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327285 - [PropertiesView] Property editor value is applied twice to a property source.
Summary: [PropertiesView] Property editor value is applied twice to a property source.
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-07 16:56 EDT by Maksym Bykovskyy CLA
Modified: 2021-05-30 08:49 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maksym Bykovskyy CLA 2010-10-07 16:56:23 EDT
Build Identifier: 20100617-1415

There's a situation when an editor value is applied twice to a property source. When a user changes the value inside a TextCellEditor and presses return, PropertySheetEntry applies editor value to a property source and deactivates editor control. However, PropertySheetViewer will still think that a TextCellEditor is active. So, when a user tries to select a different property, PropertySheetViewer intercepts a widgetDefaultSelected and handles the selection by first applying old editor value to previous property then deactivating it and activating a new cell editor.

In my opinion, applying editor value inside PropertySheetViewer is unnecessary as PropertySheetEntry applies it already plus editor itself will decide when to apply the value. For example, TextCellEditor applies value on widgetDefaultSelected().

Reproducible: Always
Comment 1 Eclipse Genie CLA 2021-05-30 08:49:12 EDT
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.