Why is editing of names in the project browser gone in V14?

[André de Carvalho]

I'm actually quite happy that the edit-by-double-click is gone.

Hated it when I double-clicked to open a package but clicked to slowly so it went into edit mode. Happens to me all the time.

F2 is such a widely used shortcut that I guess almost everybody knows it. And if not you can use the Properties view or the properties dialog anyway...

Just my $ 0.02...

Benno

Being able to quickly rename in Project Browser is an essential feature for instance when you need to renumber a large set of requirements after final review and restructure.
To remove features in a professional tool that has users for more than 10 years is not the right thing to do. I could understand if it was the result of an architectural constraint but this is just an arrogant, arbitrary decision that does not take into consideration the real use that is made of the tool.
If someone is annoyed by the feature or is not able to control its invocation it should be made configurable.

best regards
André de Carvalho

[Geert Bellekens]

André,

I'm not saying you are wrong, but quickly renaming a set of requirements is much easier when you do "View as List"

Geert

[Sunshine]

...
Of cause this is not a show stopper, but it was there, and I love it, and it is MS-Windows standard somehow.

UI Standards seem to have gone out of the window now with every UI designer seeming to think they can do whatever they want. Kind of makes life a little more difficult for the user with an inconsistent experience loosing the whole spirit of what a Graphical User Interface was design for in the first place.
Think we've slipped into an alternative universe where chaos is the way to go.

[Sunshine]

André,

I'm not saying you are wrong, but quickly renaming a set of requirements is much easier when you do "View as List"

Geert

Absolutely or the specification view as yet another alternative.
... But its always nice to have the feature to edit in the view the user is using so the they have the option. I always like to enable users to work with tools on how it suits them rather than constraining them. But hey that might be old fashioned thinking.
The new approach seems to be make em do it our way. Let's see how that plays out.

[Paolo F Cantoni]

[SNIP]
But hey that might be old-fashioned thinking.
The new approach seems to be make 'em do it our way. Let's see how that plays out.

Dare I say we might be moving into "Post Consistency?"   

Paolo