Tagged value notes in 15

[Uffe]

Hey people,


In 13.5 you could see tagged value notes in a separate area of the tagged value window. This no longer seems to be an option in 15, I seem to have to open the notes in a separate window.

Is there a way to get that integrated notes view back?


Cheers,


/Uffe

[Geert Bellekens]

Uffe,

I can still see the notes of my tagged values, both from MDG tagged values (that end up in the properties) as individual tagged values.

But you can alter the size of the notes field at the bottom of the tagged values view. Maybe you simple made it so small you can't see it anymore and you need to drag it back up?

Geert

[Uffe]

I can still see the notes of my tagged values, both from MDG tagged values (that end up in the properties) as individual tagged values.

But you can alter the size of the notes field at the bottom of the tagged values view. Maybe you simple made it so small you can't see it anymore and you need to drag it back up?

That's just it -- I can't. Not in 15. I can't find any pane for the notes in either the properties dialog, or the Tags section of the properties window.

Undocking doesn't help, resizing doesn't help.

/U

[Geert Bellekens]

Just to assure you that I'm not joking.
Here's an image of a tagged value with notes in v15.0.1513
https://imgur.com/EjKFqps

Geert

[Uffe]

Thanks Geert, I found it at last.

It's actually in the manual. 

Assign Notes to a Tagged Value

The notes are displayed in the lower portion of the Properties window only if the 'Hide Properties Info Section' checkbox is not selected in the 'Window Behavior' tab of the 'Preferences' dialog (select the 'Start > Desktop > Preferences > Preferences ribbon option and the 'General > Window Behavior' tab); if you change the setting of this option, you might have to restart Enterprise Architect to make the change take effect

And you do need to restart.


/U

[Geert Bellekens]

Wow, I'm glad it was enabled by default, or I would have never found that option 

Geert

[Uffe]

Wow, I'm glad it was enabled by default, or I would have never found that option 

I didn't disable it, but we upgraded from 13.5 so maybe that's a factor.

Well actually, it's a negative option meaning that when you enable it (tick the box) you disable ("hide") the integrated notes view, so strictly speaking I didn't not disable it, but instead didn't enable it, but it was enabled by default after the upgrade -- "it" meaning the option, not the visibility of the notes. Which was disabled, and which I re-enabled by disabling the option.

One for Paolo there.

/Uffe

[Paolo F Cantoni]

[NOTE: The original post has been modified as a result of input from KP]

Wow, I'm glad it was enabled by default, or I would have never found that option 

I didn't disable it, but we upgraded from 13.5 so maybe that's a factor.

Well actually, it's a negative option meaning that when you enable it (tick the box) you disable ("hide") the integrated notes view, so strictly speaking I didn't not disable it, but instead didn't enable it, but it was enabled by default after the upgrade -- "it" meaning the option, not the visibility of the notes. Which was disabled, and which I re-enabled by disabling the option.

One for Paolo there.

/Uffe

Duly noted!

As correspondents may have noticed, I use specific terms for dealing with so-called Check-boxes.   The boxes are either marked or unmarked (meaning that they do or don't have a mark - trick, cross, whatever).   The boxes (controls) are also either enabled or disabled to allow input (disabled ones are greyed out). The (underlying) variables they control are either set (true) or unset (false) and the boxes may be observed for their current state.  As far as I can tell, that provides precise information as to what we are talking about and gets around the "overloading" of the other terms to mean more than one of the options above.

I commend the above terminology to you all.

Paolo

[qwerty]

Did you notice the behavior of "Enable Security" in the menu? EA at it's best. And of course: that's a feature.

q.

[KP]

The options they control are either enabled or disabled

From a developer's point of view, enabled and disabled denote whether a control will allow user input, with disabled controls usually being "greyed out". Is that what you are referring to here?

[Paolo F Cantoni]

The options they control are either enabled or disabled

From a developer's point of view, enabled and disabled denote whether a control will allow user input, with disabled controls usually being "greyed out". Is that what you are referring to here?

Yes, KP,  I should have been more careful. 

We need to distinguish between the state of the visual control and the state of the underlying variable controlled by the control.

I'll amend my terminology.

Thanks for the catch...  I'm always trying to be as clear as I can - for my own sanity if nothing else...

Paolo