Indeed, the Notes tab for File Versions appears differently…
That’s right…
Your only chance to define a Description for versions is via Check-In operation.
At the moment it seems a lock can be easily removed by anyone.
It can only be removed with Operating System function “Set read-only” attribute for the file outside the Version Manager. Otherwise you can only unlock files that you self have locked inside the Version Manager.
Perhaps I have overlooked something… how do you remove some one other’s lock?
I think these issues may be because the actual user is not used at the moment.
Scenario1:
User A opens TDM and lockas a version (blue padlock).
User B opens TDM and sees version locked with blue padlock.
Scenario2:
User A opens TDM, User B opens TDM.
User A locks a version (blue padlock).
User B refreshes VM (close/open VM dialog) sees yellow padlock.
User B selects Unlock version. Version is unlocked and can be checked out for editing.
Also:
User A opens TDM, User B opens TDM.
User A creates a new revision of a file (this can be sen in projects.xml).
User A closes TDM (projects.xml is updated again).
User B closes TDM (projects.xml is updated again WITHOUT the new revision).
User A opens TDM - the new revision is missing and has to be recovered from the OS file.
To perform the earlier tests I installed TDM on a PC next to my desk.
I set up the VM paths to point to the projects I’m using for testing.
VM did not see any projects.
Refreshed VM by close/open VM dialog a couple of times
Still no projects visible.
Closed TDM - at this point the projects.xml file was overwritten with no projects
Opened TDM - no projects.
Closed TDM
Went back to my PC, opened my TDM, recreated the projects from the individual files, closed my TDM.
Opened TDM on other PC - projects now found.
I seems that VM doesn’t see the files in the new location until TDM is restarted BUT when TDM is closed it writes the empty projects file back to the new location overwriting the real projects file.
Thanks for all your remarks on the Version Manager. Our tester have gone through all of them. You've helped us to find other bugs that need to be fixed. Thanks a lot for your great co-operation!
Lock problem (Scenario 1) - CR # 43 961.
Project.XML file update problem - CR # 43 962.
I seems that VM doesn't see the files in the new location until TDM is restarted BUT when TDM is closed it writes the empty projects file back to the new location overwriting the real projects file.
relates to problem 2.
I set up the VM paths to point to the projects I'm using for testing.VM did not see any projects. Refreshed VM by close/open VM dialog a couple of times. Still no projects visible.
Generally, the projects have to be created in Version Manager itself. Just to define path to projects in Options is not enough.
I set up the VM paths to point to theprojects I'm using for testing.VM did not see any projects. RefreshedVM by close/open VM dialog a couple of times. Still no projectsvisible.
Generally, the projects have to be created in Version Manager itself. Just to define path to projects in Options is not enough.
The scenario I was referring to was;
User A on PC1 had created the projects and versions of models in a shared area.
I was trying to set TDM for User B on PC2 to use the same projects and models.
I expected that pointing VM paths in TDM on PC2 to the shared area would be sufficient. Apart from the initial overwriting of the Projects file, this does set VM up to access the shared projects in the way we want to.