• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 959 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.

Code Composer V5 External Editor

Steve Streicher
Prodigy 10 points

Hi,

Looking to use an external editor for source code with CC V5. I went to preferences->general->editors->file associations, added *.c and *.h to "file types" window, added my editor executable to "associated editors" window and clicked default for each.

Now when I build, if I click on an error in the Problems window, it goes to the built in CC editor windtow. If I click on a warning, however, it does fire up my editor, though it does not go to the correct line number.

Why doesn't it work with the errors, but does with the warnings? Is there a way to get it to go to the correct line number, as it does in IAR?

Thanks

Steve

 

  • 0
    TI__Guru*** 130875 points

    Hi Steve,

    I have been trying to reproduce this and dig into this for you.   I also see some odd behaviour.   I find the following

    1 - it seems to me no matter what causes the external editor to launch .... you seem to land at the top of the document

    2 - I found I had to double click on the file in the project explorer the first time.   After this I did find click on an error in the problems view launched the external editor, but again with a cursor/focus at the top of the file

    I am going to pass this on to development to see if anything can be done and post feedback as soon as there is any.  Unfortunately it could well be the case this behaviour is coming from Eclipse.

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    TI__Guru*** 130875 points

    Hi Steve,

    sorry for some days in between repsonses here.  Feedback from development seems to be that this comes from default eclipse behaviour unfortunately.   I am afraid they were unable to really suggest any work arounds etc.

    A shame as I agree it would be nice to have this working.

    Sorry for the inconvenience and all the best with development.

    Best Regards,
    Lisa