• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 497 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Constant requests to make .project and .cproject files writable are annoying

Bill Etcheverry
Intellectual 345 points

Every time I open a project, I get 1 or 2 of these requests for every project built.  These files need to be under SCM control and should not be modified unless absolutely necessary.

These request block other operations and make your tool more difficult to use.

If the files get changed and the file is locked, the file could be saved under a different name (.project.bak) for comparison after the session.  If the saved changes are needed, the file could be checked out and replaced with the new file rather than having the changes lost.

Bill

  • 0
    Intellectual 345 points

    Please add the word writable in the posting title.

  • 0
    TI__Guru**** 476191 points

    Hi Bill,

    This is a known issue that has been fixed in CCS versions 5.1.1 and greater.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 345 points

    After a lengthy delay, I was able to get a second PC to try out CCS V5.1.1.  It has the same problem that V5.1 has.  A background task starts every time we import our projects to refresh the project files and I have to press a key over 100 times before I am able to do any work.  I can't even leave and come back when this foolishness is finished because because these tasks block until there is user input.  Yes/no, it doesn't matter because these files are locked under CM control.  I have to do this several times a day.  I can't believe that we are not going to lose customers over this issue.

    It is really unfortunate that the developer(s) who wrote this code and everyone in the review cycle for this code were completely unaware of the common microsoft practice of adding "yes to all" and "no to all" buttons for these kinds of user interfaces.