Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 173004 - [PropertiesView] PropertyView does not handle multiple selection
Summary: [PropertiesView] PropertyView does not handle multiple selection
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 171498
  Show dependency tree
 
Reported: 2007-02-06 03:12 EST by Krzysztof Daniel CLA
Modified: 2019-09-06 04:24 EDT (History)
1 user (show)

See Also:


Attachments
Blanking not equal property values (7.17 KB, patch)
2007-02-06 03:16 EST, Krzysztof Daniel CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof Daniel CLA 2007-02-06 03:12:14 EST
Build ID: I20061214-1445

Steps To Reproduce:
1. Create GEF Project (Logic example).
2. Select multiple objects
3. See propertyView


More information:
Only the first selected object properties are displayed.
Comment 1 Krzysztof Daniel CLA 2007-02-06 03:16:40 EST
Created attachment 58319 [details]
Blanking not equal property values

Displays empty string when properties are not equal.
Comment 2 Eric Moffatt CLA 2007-02-06 11:53:11 EST
Daniel, is this a duplicate of the patch that you added to bug 15734 ?

If not then remove the un-dup this one with an explanation of how they're different.


*** This bug has been marked as a duplicate of bug 15734 ***
Comment 3 Eric Moffatt CLA 2007-02-06 11:54:16 EST
Ooops, just saw randy's comment and agree that this is a somewhat different case...
Comment 4 Lars Vogel CLA 2019-09-06 04:24:10 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.

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