Is Package.Flags safe to use?

[Uffe]

Hello all,


Let's say I've got some information I want to store relating to a root node.

Root nodes, unlike other packages, are not shadowed by an element but exist only in t_package. This means they can't have tagged values assigned to them.

However, there is a field Package.Flags (t_package.PackageFlags), which contains not binary flags but various properties. It is documented thusly:
    String
    Read/Write
    Extended information about the Package.

It doesn't say that this field is Sparx, for the exclusive use of.

So if I add a custom "flag" here, will EA leave it alone and let me play with my own toys in peace?
Or will it get deleted because some sub-function in some dark corner of the codebase doesn't recognize it?

Cheers,


/Uffe

[qwerty]

Use the notes. They even make their way to the XMI. I once had an application for that but then disaster broke and it's only just on my mind. So no test on bejond V13.5.

q.

[Uffe]

Huh. I thought Notes were also a property of the element, but no, you're right, it's in t_package as well.

And you can update a root node's Notes from the API, and it doesn't show up in the GUI.

Bit of a hack, but sounds workable. Thanks!

/U

[qwerty]

That's what I am: a hacker :-)

q.

[Geert Bellekens]

Yep, I've used that exact "trick" in the past as well 

Geert

[Uffe]

Yep, I've used that exact "trick" in the past as well 

Geert

Hmm... So maybe we need some way of co-ordinating our hacks...

[qwerty]

Damn. And I thought I had the "copyright"!

q.

[Geert Bellekens]

Damn. And I thought I had the "copyright"!

q.

I might have started doing it after you suggested it . I'm not sure, must be like 10 years ago or something.

Geert

[qwerty]

Then you're the owner. I stumbled over that for a project 2 years ago. I guess you had the need for it earlier.

q.