• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 99 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CODECOMPOSER: Separate CCS Theia Instances Conflict with Each Other's Open Workspaces

David Messerschmidt
Prodigy 10 points
Part Number: CODECOMPOSER

Tool/software:

As some background, I have several c2000 projects I work on concurrently, each with several generations.

My workflow typically has two instances of CCS, one on each monitor, and each opened to different projects to better search, compare, and debug simultaneously.

I've noticed that CCS 20.x has undesirable coupling between separate instances of CCS, detailed below. I would expect that each instance of CCS would only be coupled by global settings or similar, and if I was to open two separate workspaces, in two different instances of CCS, editing one would not affect the other, but it does.

I have tried the latest release in hopes this was fixed, but it was not. 

Version: 20.1.0.6__1.7.0

How to reproduce:

  1. Open an instance of CCS, and lets designate it CCS1
  2. Create an empty folder "dir1"
  3. CCS1:  Use File > Open Folder... to open dir1
  4. CCS1:  Inside dir1, create an universal c2000 project, named "Universal Project 1"
  5. CCS1:  Save the workspace as "ws1", and save the workspace file inside dir1
  6. CCS1:  Repeat steps 1-4, but name everything "2" (dir2, Universal Project 2, ws2)
  7. *
  8. CCS1:  File > Open Workspace from File... and open ws1
  9. Open an new instance of CCS, and lets designate it CCS2
  10. CCS2:  File > Open Workspace from File... and open ws2
  11. CCS1:  Notice on CCS1 that when trying to access Project > Properties, you get an error "Cannot read properties of undefined (reading 'activeBuildConfiguration')". Also, you cannot build, change configurations, or anything project specific.
  12. This can be fixed by removing and adding the project back, however, that creates further issues:
  13. CCS1:  Using "Remove Folder from Workspace", remove dir1 from ws1
  14. CCS1:  File > Open Folder... and open dir1 again
  15. Notice that this not only adds dir1, but also adds dir2 to ws1. It also adds dir1 to ws2. Removing and adding folders/projects will continue to affect both workspaces as long as both CCS instances are open.

*At step 7, the file system should look similar to:

How can I get around this, or can this be fixed to support multiple instances of the app?