Settings and activity
5 results found
-
19 votesTristan Grimmer supported this idea ·
-
16 votesTristan Grimmer supported this idea ·
-
20 votesTristan Grimmer supported this idea ·
-
19 votes
An error occurred while saving the comment Tristan Grimmer supported this idea · -
28 votes
An error occurred while saving the comment Tristan Grimmer commentedAll three should be editable... sometimes you want to merge 2 files into the base... sometimes during an integration you may want to 'merge a diff' from one codeline into another. In short, there are some real-world situations where I wouldn't want my tool restricting me. Let perforce / scm decide what files are read-only. The question then becomes how will you deal with the RO attribute. The answer should be a choice between a) allow editing in memory and ask when saving what to do (overwrite/cancel) (that's how I have my VS set) or b) Ask what do do on first edit. Visual Studio puts a little lock symbol by the filename. Please don't restrict editing ability based on the arbitrary 'slot' a file is loaded into!
Something like this could deal with all the other 'ignore comments / version text etc' requests.