OBSERVED ANNOYANCES/PROBLEMS:

-"undo checkout" is right below "checkin" on properties menu and command line menu. As such, is incredibly easy to hit undo when meaning to checkin. Tragically, the undo checkout will copy the latest version into the local file and does not check to see if that will cause loss of changes in the local file! Be warned.

- checking in a file can take a long time, proportional to the number of items in the project. as much as 35 seconds for a project with 109 files. Most were not checked out, marked read only. this is also the time needed to simply open the project in studio.

- one workaround, when checking in several files at once (but wanting to check them in individually to provide reason) is to check them in in Versions. It doesn't take any time. Then return to studio and hit F5 to refresh.

- I've noticed that the delay appears to be the profcess doing the equivalent of a refresh. Perhaps an option could be (on check in or for the project) to not do a refresh on check-in.

- versions (native and in studio) prompts for userid on every project open. no option to indicate that pc is not shared.

- studio interface very slow to open projects, check-in files (refreshes project file list), or even to move between folders in a project. Simply a factor of the number of files to be displayed.

-option in studio to synchronize with source control does not work: right click on project for "synchronize with source control", provides list of programs in source control but not in project and vice versa. Allows correction of this. But in my test, it showed all files in project as not in source control, though they are. One was even checked out and updates, and still showed up in "remove" list. (Note that in Versions, can use "files not in project" to achieve something close to this, but it's what's in the working dir that's not in the Versions project. It's what we'd like Studio to be able to do, but whereas versions maps a project to a working dir, studio's project is designed to allow files from multiple dirs. Would be nice to have option to designate that project maps 1-to-1.)

-studio interface presumes last project opened should be opened again. since project is slow to load, can be frustrating when working on multiple projects. (In native versions interface, can turn off that "remember last project" option using options>workstation options>display>restore projects at startup.)

-no easy way to cause new files to be placed in project (studio or scc). Need to add it using the steps offered above. No way to list files in dir but not in project. (Versions offers a "files not in project".)

-by using option to mark checked in files as readonly, if an extended search and replace finds file in that state, no easy way to edit them. No option provided to check them out, even if in project tab. Must manually check out.

-if you have a project open in studio and change the project's use of keywords in Versions, the change will not take place (keyword expansion will not happen on checkout) unless you reopen the project in Studio (can simply double-click on project in project list)

- show differences and show history are not on top line menu. only on context menu (right click)

-keywords won't be expanded if "check out immediately" option is used during checkin (log entry, for instance, won't reflect latest checkin reason). Could be a problem if that file is then uploaded to server. Will appear to not reflect changes: though changes will be in file, the log will not indicate that.

-versions Date keyword puts out time. Would be nice to have Dateonly, like in VSS.

-studio interface for selecting files in project view does not allow selection by pressing enter. Must double-click. (Not true in the "normal" local files interface.) Also, the source control dialogue box that opens does not support a keystroke for open/checkout/get. Must select radio button with mouse.

-versions native interface does not allow selection of a file in the file list by typing its first letter. Must select with mouse.

- fix terat2, pointing to wrong files

- what happens if you edit with normal tab (not projects)? if that's the workin directory, it just means that you're not checking in the changes. when you edit a file without using the version control, it's just like the old days. No tracking of edits. When you ftp that to the server (as you normally would), you're technically uploading a new version but if you don't use version control you just have no way to track that change. when you finally do "check in " that proc, it will just consider ALL the changes since the check out to be one change. Loses granularity, but at least better than nothing at all.

-in versions, may seem as if there's no way to delete versions (perhaps to remove several insignificant ones not worth keeping). turns out that you have to lock the file first

-in versions, the Merge command is not on the file context menu (right click). Only on file command menu (and then only if file is locked by you). Also, File command menu has some commands seemingly unrelated to the current file, including compress the vault and reports and charts.

-one might think that the Merge command will work to merge changes to a non-checked out file which has been updated, but it does not. Says "does not need to be merged". So how to merge these changes? (Does merge only work on "branched" files? That would be a pity.) The solution seems to be to lock the file from within Versions. Can then check it in from either versions or studio without forcing a checkout to overwrite them.

-in versions, the audit reports (in audit tab) have neat filters, but can only select one. Can't get "file activities by me in past 24 hours".

-in versions, you can use the workstation option to not lock files on check-out and still check them out and in. But there are some operations you can't do to a file unless you lock it. Even if you check it in.

-in versions, audit tab is nice to use filters like last 24 hours, etc, but can't see check-in reason on this screen. not even in file properties. and if you select the file in the left pane, that loses the setup you had in the right pane (it makes it a file audit for the selected file, even if you right-click on that file in the project tree).

-in versions, option to export a report using "mail" option and selecting html causes creation of directory, and even then gets file error

- in studio, sometimes when choosing source control>history and then close will cause an error. that error also removes the marking of the file as readonly.

-Studio doesn't remember change to project settings for column width. I don't need the description. I need the modified time. But that's off the screen to the right, and changing th edescription width is not remembered.

- in studio, highlighting an unlocked (therefore readonly) file in the "local files" tab and pressing enter generates 2 prompts to open as read only.

-in versions, would be nice to have option so that an open does a checkout, or at least a lock

Further details available for:

| Home | ColdFusion | Articles | Presentations
| User Groups | Other Resources | Press Releases | Company

© 1998-2024, Charles Arehart, SysteManage
Our Practice Makes You Perfect