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.

DSS script within CCS scripting console 2 questions

Hi everyone!

I am writing a DSS script (Java Script) which runs within CCS scripting console.


Is it possible to figure out the name of the project, which is currently marked as Active 
in the Project Explorer, within the script?
I need this to call debugProject(projname) on the current active project.
 

Furthermore i want to install my script persistent so that i do not need to call loadJSFile() 
everytime i restart CSS.
I tried loadJSFile(..., true) but this does not work, 
i get this error "path does not contains a valid JavaScript file".
When i call loadJSFile() without the second parameter it loads and works as expected.
Is there something to consider, like the path the script is located?


I am using CSS 5.1.1.00031 on WinXP SP3 and to run the DSP C programm i am using the 
TMS320C66xx simulator.

Thanks Juergen
  • Hello Jeurgen,

    J��rgen Zopf said:
    Is it possible to figure out the name of the project, which is currently marked as Active 
    in the Project Explorer, within the script?

    There is no scripting console / DSS API for this. They may be another way to do this but I'm trying to understand your use case. Why do you need to know the currently active project? debugProject() can take in any project name, it doesn't have to be the active one. Is it to avoid any hardcoded names in your console script?

    J��rgen Zopf said:
    I tried loadJSFile(..., true) but this does not work, 

    Try removing the comma and see if that helps.

    Thanks

    ki

  • removing the comma worked. 

    The use case for the first question is that i have a bunch of projects in workspace which all can be debuged using the script.

    But i found out that that my problem can be solved by letting the user start the debug session (with the project he wants) and

    then call the script instead of call the script and let the script start the debug session.

    Thanks Jürgen