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.

CCS: After F3 to "Jump to definition" how can I "go back" to the previous edit point? CCS Web and/or Windows

Tool/software: Code Composer Studio

I'm new to Code Composer Studio, and currently using the online version at https://dev.ti.com/ide/

I can select any function or variable and press F3 to jump to the definition. But once I'm done, how can I jump back,

returning to where I started from?

  • Bryce,

    In the desktop version of Code Composer Studio there are back/forward buttons on the toolbar that you can use for this:

    In CCS Cloud there is no equivalent that I am aware of.  If the definition is in a separate file then it would have opened a new tab in the editor and you could select the previous tab to go back.  However if it is in the same file then there is no way to automatically go back.

    I looked through the keybindings and didn't see anything that matched:

    Regards,

    John

  • I'd love to click "this resolved my issue", but that's not quite right.  Thank you however for the well researched answer.

  • No problem.  Overall CCS Cloud is a much more limited environment and today it is really meant for initial evaluation and development.  Once you get beyond that then it is time to migrate to CCS Desktop for more functionality.  Down the road we hope to have much more equivalent Cloud and Desktop environments but that is still in the future.

    Regards,

    John

  • CCS cloud quite frankly is pretty darn functional.  Give it a little love, and it can fly.
    Perhaps the biggest thing I feel with CCS web is the inability to background the build/load process.  The entire GUI locks up, and I can't browse code or whatever until the build/load completes.

  • Try hitting build first and then click debug when it is done.  If you do it this way the GUI is still usable while during the build and only disabled when you do the shorter debug launch afterwards.

    John