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.
Hello!
I don't know if I am the only one having these problems (or thinking these are problems),
but here are a few ideas to improve CCS. I have been already writing about it in the past,
sorry about it, but I really think this could greatly improve the IDE.
1. Adding a linked source code folder:
Right-click the project, then choose new->folder. In the popup, choose "advanced" and then
choose the source folder from the file system.
At this point:
2. Compiling, loading, running
Apparently the load time improved in CCS vs CCE.
However, there is still something I have been wondering about: what is the purpose of launching the
program if the compilation / link failed? Is there any advantage of doing this? (just curious).
This was already the case in CCE3, so probably there is a sound technical reason to allow
to launch a failed program. Could anybody explain?
Now a related issue: in the preferences panel (that was also the case in CCE3), in Run/Debug->Launching,
there are launching options, all with 3 possible settings except one. Why does "Continue launch if project
contains errors" have only 2 possible settings (i.e no "never" option)?
3. Opening a project:
There is apparently only one way to open a project: start CCS, and choose "switch workspace"
to go to the relevant location. At this point, apparently the whole IDE is shut down and
restarted
I think it could be nice if a workspace could be opened by double-clicking the workspace
icon. And similarly it would be nice to open a specific project in the workspace the same
way: double click the project file opens the relevant workspace and sets the selected
project as active.
Pascal
**Attention** This is a public forum