Bug 19183

Summary: [CVS UI] Strange workflow in Set Keyword Mode
Product: [Eclipse Project] Platform Reporter: Michael Valenta <Michael.Valenta>
Component: TeamAssignee: Platform-VCM-Inbox <platform-vcm-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 Keywords: readme, usability
Version: 2.0   
Target Milestone: ---   
Hardware: Other   
OS: other   
Whiteboard:

Description Michael Valenta CLA 2002-06-04 15:25:53 EDT
This is all post 2.0.

Here are some comments/problems with Set Keyword substitution:

1. The command is only enabled on a single item. Therefore I cannot select 
multiple files to set their type.

2. If you operate on a single file, you need to go though all the wizard pages 
to explicitly include it if it is already shared with the repository. In the 
single file case I just want to set it and be done. I don't want to go through 
a 3 page wizard.

3. It would be nice to change the mode being assigned to individual files in 
the wizard. (i.e. I know this ones not really binary but I don't want a global 
patterns for it).
Comment 1 Jean-Michel Lemieux CLA 2002-06-05 11:15:52 EDT
1. ack. although the current workaround is to select the parent folder.
2. ack.
3. on the summary page you can change the keyword type of individual files. 
The table has a drop-down combo box for the keyword type, you can overide any 
of the values.
Comment 2 Jean-Michel Lemieux CLA 2002-06-06 16:33:53 EDT
It turns out that multiple selection is allowed. Moving this PR to future to
address point 2.

Make it easier (e.g. less wizard pages) to set the keyword mode for one file.
Comment 3 Kevin McGuire CLA 2002-06-06 16:38:05 EDT
Re point 1: if you select a new unadded file, you can't do keyword subst., even 
thought the file's decorator indicates the subst mode the file *will* have.  
This is likely a bit confusing for people since they can't change it there, and 
may be the case why Mike thought it only worked on single selection.
Comment 4 Michael Valenta CLA 2002-09-09 15:13:08 EDT
Reopening
Comment 5 Michael Valenta CLA 2005-03-29 12:33:40 EST
Thee issues were addressed in 3.1