TPos bug

[twin]

Hello,
I have an EAP repository, and when I export it to a dbms (the dbms has the schema specific for Automation Interface), TPos field for the objects in t_object table is either 0 , or null. Only when I do a move up/down from EA the fields are updated. Is this the normal behaviour, or it is a bug for exporting?

Also, if I copy an UML element, like a UseCase from a diagram, into another diagram, the value of the TPos is also copied. I think, this one should at least be reset to 0, or to null, or in the best case, it can be updated with a new value, according to the position in the new diagram.

What do you think about this?

Thank you,
twin

[smendonc]

...it can be updated with a new value, according to the position in the new diagram.
I think the purpose of TPos is to indicate the position within the Project Browser not a specific diagram, hence it shouldn't change unless its position in the project browser has been changed.

Stan.

[twin]

Yes,you are right, i did not paid attention when I wrote. I wanted to say that when I do a copy paste of an UML element, TPos value is also copied, instead of being null or being update with a new value that represents the position of the copied element in the tree. For ex, if i have an UseCase with TPos=3, if I copy and then paste the UseCase, the new one will also have TPos=3, even if he is not the third in the tree (the third in the tree is the original UseCase).

Thx,
twin

[«Midnight»]

Hi Twin,

If I understand you correctly this sounds like a bug. The target project could end up with more than one element with the same TPos value, which certainly does not sound correct.

First, make sure you are using the most recent build of EA - that would be 845 as I write this, but 846 could come out very soon.

If the bug persists in either of the above builds I suggest you report this as a bug. Use the Report a Bug link near the bottom of any forum page. If you are a registered user, then instead of filling out the (first) bug report form you can click the link to the registered version (the link is above the form); that version will allow you to attach sample files that exhibit the bug. [Remember to compress the files into an archive first.]

David

[twin]

Hi,

Thank you for your reply. No, I am not using the last build. I have an older build (7.1.831). Probably I should talk with my company to provide me with the last updated version they have. I also reported this as a bug, and now I am waiting for an answer from the guys.

Thx,
twin