Bug 415211 - [Profiles] Cannot check version etc. of currently edited profile
Summary: [Profiles] Cannot check version etc. of currently edited profile
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Views (show other bugs)
Version: 0.10.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: SR1   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 408316 435103
Blocks:
  Show dependency tree
 
Reported: 2013-08-16 05:28 EDT by Toni Siljamäki CLA
Modified: 2014-07-23 07:25 EDT (History)
2 users (show)

See Also:


Attachments
Profile definition window (55.10 KB, image/jpeg)
2013-08-16 05:28 EDT, Toni Siljamäki CLA
no flags Details
Profile definition in .uml file (56.85 KB, image/jpeg)
2013-08-16 05:29 EDT, Toni Siljamäki CLA
no flags Details
Screen shot of deninitions (24.86 KB, image/jpeg)
2013-09-03 06:01 EDT, Toni Siljamäki CLA
no flags Details
Screenshot Profile Definition Stopped Working (134.72 KB, image/jpeg)
2014-04-28 00:57 EDT, Toni Siljamäki CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toni Siljamäki CLA 2013-08-16 05:28:10 EDT
Created attachment 234476 [details]
Profile definition window

When defining a new version of a profile you get a pop-up window where
you can fill in all sorts of information, ending up in the profile.uml file.

This information can not be viewed/checked while editing the profile in Papyrus.
Comment 1 Toni Siljamäki CLA 2013-08-16 05:29:12 EDT
Created attachment 234477 [details]
Profile definition in .uml file
Comment 2 Toni Siljamäki CLA 2013-08-20 07:16:28 EDT
Also see Bug 408316 regarding the
additional "details" button described in Comment 2.
Comment 3 Camille Letavernier CLA 2013-08-28 11:40:48 EDT
Implemented in ff0da7327419c8e3c4aa16b5060bbd16a2b2e82d
Pushed to master

- A new tab has been added to the Profile properties view. It displays the list of existing definitions, with their name and version
- It is possible to see the details (Author, Copyright, ...) for each non-legacy definition
- It is now possible to remove an existing definition. Not sure whether this is a good idea however. This is useful to cleanup profiles, but is also a dangerous operation for compatibility.
Comment 4 Toni Siljamäki CLA 2013-09-03 05:55:23 EDT
OK, the information can be viewed now, but...

It would be better if this new tab had different columns in it,
instead of (in a non-intuitive way) having to double-click on
a profile definition to view it in a pop-up window, which btw
does not work for the listed definition with version (0,0,0),
and where the pop-up window is saying "Edit an element".
Comment 5 Toni Siljamäki CLA 2013-09-03 06:01:00 EDT
Created attachment 235094 [details]
Screen shot of deninitions

The definition for the irst definition which cannot be viewed.
Comment 6 Toni Siljamäki CLA 2013-09-03 06:01:38 EDT
Reopening this bugzilla.
Comment 7 Toni Siljamäki CLA 2013-09-03 06:14:59 EDT
When defining a new version of the profile this new list of definitions
does not get updated. One has to close and open the profile to see it.
Comment 8 Camille Letavernier CLA 2013-09-06 07:56:25 EDT
> One has to close and open the profile to see it.

Actually, you can also refresh the selection (Reselect the profile).

There's a missing listener on the list of definitions (Actually, this is not specific to profiles, but for most collections in the properties view).

I can fix it, but then there will be another refresh issue, on the Profile's label (Which will display 0.0.0 as its version, until the view is refreshed). And this one is much more difficult to fix.

> which btw
> does not work for the listed definition with version (0,0,0),
> and where the pop-up window is saying "Edit an element".

These profiles do not have a version/comment etc., but I could still display the (empty) fields for them. This would reduce the confusion.
Comment 9 Camille Letavernier CLA 2013-09-06 11:52:18 EDT
> There's a missing listener on the list of definitions (Actually, this is not specific to profiles, but for most collections in the properties view).
> 
> I can fix it, but then there will be another refresh issue, on the Profile's label (Which will display 0.0.0 as its version, until the view is refreshed). And this one is much more difficult to fix.

Fixed in 16dea8a59cc96fa80d15beb66989741ecd469a62; pushed to master.
Fixed in cf3cb29928b7b8fb4c9730c2892f362addad973d; pushed to 0.10-maintenance
Comment 10 Toni Siljamäki CLA 2013-09-09 09:01:49 EDT
Just edited a profile model to test the latest nightly build.
I cannot see and do not understand what has been fixed.
Comment 11 Camille Letavernier CLA 2013-09-09 11:42:11 EDT
Hi,

> I cannot see and do not understand what has been fixed.

This part of the bug has been fixed:

> When defining a new version of the profile this new list of definitions
> does not get updated. One has to close and open the profile to see it.

(Except that the version number of the new definition is invalid, and this cannot be fixed easily)
Comment 12 Toni Siljamäki CLA 2013-09-16 07:43:04 EDT
OK, now I see what was fixed.
The new definition get listed, but the version number is (0,0,0).
The correct version number get displayed after opening and closing the new definition.

If I immediately after create a new version of the profile
the definition for this new version does not get listed.
Comment 13 Toni Siljamäki CLA 2014-02-01 04:31:19 EST
This one has been fixed, right?
The profile I'm just looking at has the correct number on the version list.
Comment 14 Toni Siljamäki CLA 2014-04-28 00:57:11 EDT
Created attachment 242371 [details]
Screenshot Profile Definition Stopped Working

The Profile.Definition in Properties got blank in the attached version.
Comment 15 Toni Siljamäki CLA 2014-05-16 17:19:27 EDT
I open a new bug for this one to get attention or this issue.
Comment 16 Toni Siljamäki CLA 2014-05-27 17:36:01 EDT
Bug 435103 is fixed so this one works again.
Tested version is 1.0.0.v201405271626
Comment 17 Camille Letavernier CLA 2014-07-23 07:25:06 EDT
> Bug 435103 is fixed so this one works again.
> Tested version is 1.0.0.v201405271626

I close the task