This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to use Column Editing in uVision3.*

Does anyone know how to use column mode for editing source code within uVision3 IDE??? I am used to using Jens where I could insert text in a column format defined by the start and stop of the drag of my cursor. I could then right click and insert defined text on all lines simultaneously starting where my cursor orignated to the end of the highlighted segment area in a column format. Can anyone help with this??? I know how to use the Alt key and mouse to highlight text in a column format, but I can find a way to enter text on multiple lines in a column format. This is very annoying.

Parents
  • "I will just have to develop a work-around by hooking another editor into the uVision IDE to edit code with which I would be better served using the column mode feature that I like so much."

    you don't even need to hook in any external editors (you can but you don't have to): just edit your files in your editor and then switch over to the ide to compile.

    As I described in a post earlier in this thread, the benefit of "hooking" the editor into the uVision IDE when using an external editor is that the IDE can redirect the build results to the editor's build window. That way your editor can parse the errors (click on an error to go to the appropriate statement in the source code).

    -Walt

Reply
  • "I will just have to develop a work-around by hooking another editor into the uVision IDE to edit code with which I would be better served using the column mode feature that I like so much."

    you don't even need to hook in any external editors (you can but you don't have to): just edit your files in your editor and then switch over to the ide to compile.

    As I described in a post earlier in this thread, the benefit of "hooking" the editor into the uVision IDE when using an external editor is that the IDE can redirect the build results to the editor's build window. That way your editor can parse the errors (click on an error to go to the appropriate statement in the source code).

    -Walt

Children