Bug report for VCS plugin

ScottMattes

Member³
I saw this on both 5.1.3 and 5.1.2 versions running on Windows 2k Pro. I did get the newest version of the plugin

Right clicking in the package file will only show Add and Check out but not Check in like I expect. If I choose Check out and then cancel then right click again I now see Check in. The main menu VCS option is the same, until I choose Check out and cancel that the main menu will enable the Check in and some other options.

------------------
------------
Scott Mattes
 
I tried with the new version and had the same results. VCS / Preferences said v1.1.1 in the lower right.

------------------
------------
Scott Mattes
 
I cannot reproduce this, but I will send you a test version by e-mail.

------------------
Marco Kalter
Allround Automations
 
The new test version, 112, is worse in that now only Add shows up on the right click and I can't trick it into showing/enabling the Check In entry on either the main menu or right click menu.

------------------
------------
Scott Mattes
 
That would indicate that the file is not checked out in the VCS project that is currently opened...

------------------
Marco Kalter
Allround Automations
 
In the 111 version the Check Out was an option on the right click menu, it was not in the 112 version (only Add was).

------------------
------------
Scott Mattes
 
I just discovered a very distrubing 'feature' of v111. I was making changes to a package and had gotten a clean compile and decided to check it in. Since the first time Check In isn't available I started my fake out of clicking the main menu VCS / Checkout and low and behold it didn't prompt me for 'you have made changes and will lose them, do you want to continue' it just checked out the latest and there went the work from the last hour. Ouch.

------------------
------------
Scott Mattes
 
It seems to me that the local path of your VCS project is not the same location where you edit the files. This would explain a lot of the behavior.

This would mean that the local path is directory A, and your are working with files in directory B. As a result, you do not get the check-in/out status you expect because directory B is not under control, and files are checked out to directory A where you are not actually working.

If I want to edit a file that is not checked out, it is read-only and I cannot change it.

If I try to check-out a file over a changed version, I get a message from my VCS that a writable/modified copy of the work file exists.

Please verify the Local Path of your VCS project and your actual working directory.

------------------
Marco Kalter
Allround Automations
 
Back
Top