User forums > Using Code::Blocks

COM server

(1/2) > >>

daniloz:
Does CB provides a COM server at all? OR just a DDE server?

oBFusCATed:
C::B is portable, COM is not :)

Why would you need C::B as a COM object?

Jenna:
Partly
http://www.codeblocks.org/docs/main_codeblocks_en3.html#x3-230001.11.2

daniloz:
Because I use C::B to edit and navigate through my code, but use VisualDSP++ to do the compiling and debug (DSP embedded C++ code).

So, I'd like to have a easy way to jump from one editor to the other. I already have a VBscript that I can call from C::B that sends me to he same file and line on the VisualDSP++ IDE.

Now I want to do the inverse, from the VisualDSP++ IDE have a script to jump to the same line and file on C::B...

Any ideas?

Jenna:

--- Quote from: daniloz on November 25, 2010, 11:09:12 am ---Because I use C::B to edit and navigate through my code, but use VisualDSP++ to do the compiling and debug (DSP embedded C++ code).

So, I'd like to have a easy way to jump from one editor to the other. I already have a VBscript that I can call from C::B that sends me to he same file and line on the VisualDSP++ IDE.

Now I want to do the inverse, from the VisualDSP++ IDE have a script to jump to the same line and file on C::B...

Any ideas?

--- End quote ---
You can do it with DDE or more easy with calling C::B directly.

If you uncheck "Settings -> General settings -> Allow only one running ..." and check "Settings -> General settings -> Use an already running ..." and "Settings -> General settings -> Bring it on ...", you just have to call C::B with the appropriate parameters (e.g. --file=name[:line] to open a file in a running instance of C::B).
In this case all the DDE-stuff is done by C::B itself and you don't have to care about it.

The same also works on linux (but IPC via unix-socket is used in this case).

Navigation

[0] Message Index

[#] Next page

Go to full version