Linked Notes - where?

[Paolo F Cantoni]

Linked notes are a marvellous feature of EA.

In particular, you can copy a note from one diagram and place it in another.

However, if, for various reasons, you don't show the linked element (or diagram) on the same diagram or you suppress the NoteLink connector, you have no means of determining:
1) if the Note is linked
2) which Element the Note is linked to.

I propose that if you select the Note, that the Hierarchy Diagram [Ctrl+Shift+4] be used to display the Note linkages.

Similarly, any linked Note(s) would be visible from the hierarchy of the selected Element.

Votes?
Paolo

[size=0]©2006 Paolo Cantoni, -Semantica-[/size]

[SF_lt]

add my vote

Also, note should identify, whereto it belongs - if class has property Load and method Load() - currently notes for these two will be the same - Load

Propose to use identifacators as property, method, attribute. In a case of method, full method name with parameters should be shown. Examples:

property Load:

method Load(int inLoad):

attribute sum:


Attribute and method rendering when their type isn't specified
should be more inteligent -
right now if type is left blank, attributes and methods are rendered as attribute1: and Method1(): - should be attribute1 and Method1(). Use colon for rendering only if type field is not blank

[«Midnight»]

IMHO an excellent suggestion!

I too have had quite a time finding misplaced notes. Worse still when I delete the diagram they first appear on, leaving a rather odd variant of an orphan element floating around the model.

Add my vote please.

[Eve]

Attribute and method rendering when their type isn't specified
should be more inteligent -
right now if type is left blank, attributes and methods are rendered as attribute1: and Method1(): - should be attribute1 and Method1(). Use colon for rendering only if type field is not blank

What build are you using?  Right now (build 799) attributes behave as you say, but methods only include the colon if a type is specified.

[SF_lt]

simonn, in 799 build it's opposite than you say - methods render correctly, without colon; attributes - not, they are rendered with colon ;-)

[Eve]

I'd recommend reading my post again.  That's what I said.

[SF_lt]

interesting, why attributes are exception?

[SF_lt]

another attribute rendering issue - if attribute is set to be derived, then we see:

+/    memberName : String
-/    weight :

maybe it would be better, more natural to render:

+     /memberName : String
-      /weight
OR
+/memberName : String
-/weight

more suggestions? votes?

[Paolo F Cantoni]

My vote is for no spaces...  Thus: -/weight

Paolo