Bug 44800 - [PropertiesView] Request for API's to customize property sheet view
Summary: [PropertiesView] Request for API's to customize property sheet view
Status: RESOLVED DUPLICATE of bug 1883
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Kim Horne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-14 04:50 EDT by Mark CLA
Modified: 2003-12-01 16:06 EST (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 Mark CLA 2003-10-14 04:50:22 EDT
The property sheet sorts the properties by default in lexicographical order.
A GEF graphical element i have created has 10 properties like this:

PropertyName    Value
  1              value1
  2              value2
  3              value3
  4              value4
  5              value5
  6              value6
  7              value7
  8              value8
  9              value9
  10              value10

Since the property sheet sorts the property in lexicographical order ,it will 
show these properties in the following order
  1              value1
  10              value10  [WRONG!!!!]
  2              value2
  3              value3
  4              value4
  5              value5
  6              value6
  7              value7
  8              value8
  9              value9

There are no API's exposed so that i can specify the sorting order,or tell the 
property sheet not to sort these properties..

I request a proper API to be exposed so that from GEF for a Graphical 
element ,i can tell GEF that for this particular graphical element, the 
properties should not be sorted.

Also u can refer discussion i had in newsgroup,on what to be made as an API.
sub: Dynamically adding rows to Property Sheets
Comment 1 Mark CLA 2003-12-01 00:14:26 EST
I think this bug is the same as Bug 1883.
Comment 2 Kim Horne CLA 2003-12-01 16:06:36 EST
Quite right.

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