V16 (1602) Legend name in Project Browser

[Ian Mitchell]

I'm sure that in V15 the name of a Legend could be seen in the Project Browser. Made it much easier to maintain a list of useful ones to re-use in multiple diagrams (thanks Paolo..).
In V 16 - 1602, I can still give it a name via the Properties, but that name can't be seen in the PB. But when I F2 the PB entry, it can be seen and edited, then disappears again.
If this a new feature ?

[Paolo F Cantoni]

I'm sure that in V15 the name of a Legend could be seen in the Project Browser. Made it much easier to maintain a list of useful ones to re-use in multiple diagrams (thanks Paolo..).
In V 16 - 1602, I can still give it a name via the Properties, but that name can't be seen in the PB. But when I F2 the PB entry, it can be seen and edited, then disappears again.
If this a new feature?

Depends on your point of view, Ian.  What is being output in the browser is the Notes contents (ask me how I know).  Since F2 shows the name, and on the diagram, you can't see the notes ANYWHERE, I'd say it's a bug, .  (It's also in 1603)

HTH,
Paolo

[Ian Mitchell]

Ah - how right you are.
But is this different to v15? There, the name was displayed in the PB, not the notes?
(but why the notes ?)
OK.
"Paolo, how do you know that..."

[Modesto Vega]

All our legends in v15.2 appear in the browser without a name. Being able to name legends will be in my opinion a nice to have functionality improvement.

[Paolo F Cantoni]

All our legends in v15.2 appear in the browser without a name. Being able to name legends will be in my opinion nice to have functionality improvement.

Ours have names because we gave them names (in the browser or Properties window).
Being good boys and girls, we also gave some of them some descriptions.  This is what appears in the 1602 browser - for those that have them.

So, you can decide if it's a bug or not.  But to me, it looks like one, smells like one, is one.

Paolo

[Geert Bellekens]

But to me, it looks like one, smells like one, is one.

The problem is that Sparx doesn't have that same definition.
For them it seems to be "if it works as designed, it's not a bug" even if it's designed objectively wrong.

Geert

[Modesto Vega]

[SNIP]
For them it seems to be "if it works as designed, it's not a bug" even if it's designed objectively wrong.

This is the perfect definition of a probably unintended "design feature".

[Eve]

The problem is that Sparx doesn't have that same definition.
For them it seems to be "if it works as designed, it's not a bug" even if it's designed objectively wrong.

Not really. I won't try to argue that the behavior is good. It didn't matter before legends appear in the browser, but the 'name' in the dialog isn't stored in the same place as everything else. By the time we wanted it in the browser it would break too many existing models to change it. So, it stayed the same.

When v16 came along we also decided to include text, these don't normally have a name at all, so we chose to display their notes. Personally I think it's a bug that this overrides a non-empty name, but you'll need to send in a report if you want an official response.

[Ian Mitchell]

I'll report it as a bug. It's certainly different from all other EA elements.

[Paolo F Cantoni]

I'll report it as a bug. It's certainly different from all other EA elements.

We observed that Legends had captions, not names.  But when we provided names, they appeared in the browser.  This was useful as it allowed more descriptive names (than the, usually simple, captions).  Consequently, this allowed us to re-use Legends much more easily.

If the user provides a name,  that's what should appear in the browser.  If notes are supplied, but no name, then I guess, you could display those.  What's happening now is so self inconsistent is is, by definition, wrong.

Paolo