Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: Mr. Awesome on March 26, 2006, 08:25:26 am

Title: Using Custom Tools
Post by: Mr. Awesome on March 26, 2006, 08:25:26 am
In the Tools menu, I added a tool that is basically a shortcut to GIMP, and the link works fine.  However, I can not use any other tools until GIMP exits.  I would like to have multiple tools open at once, but this is not possible under the current circumstances.  Am I using the Tools option for the wrong reasons here?

Also, in a somewhat unrelated note, I made a tool that opens a Windows Explorer in the current project directory.  However, it does not work anymore (I can't remember exactly when it stopped working).  I looked at the error message and pasted the command into my own command prompt.  The Explorer opened perfectly.  So, I switched the option in the tool editor that runs the program from a command prompt and waits for a keypress to exit, and now it works fine.  Anyone know why it's doing that?

Thanks for your time.
Title: Re: Using Custom Tools
Post by: thomas on March 26, 2006, 03:00:43 pm
Quote
Am I using the Tools option for the wrong reasons here?
Yes, kind of... the tool menu is not though to be a launchbar where you put things like Gimp :)

We could of course modify the toolmanager so it allows to use several tools concurrently, but I am not sure if we really want to do that.
Title: Re: Using Custom Tools
Post by: Zlika on March 26, 2006, 03:22:20 pm
Hi
In the same spirit:
I wanted to add a shorcut to XRCed, which is a XRC editor. This tool is in Python. When I lauch it from the command line, it's ok, but when I put it in the CB Tools menu, it's not working!

Zlika
Title: Re: Using Custom Tools
Post by: Pecan on March 26, 2006, 03:35:21 pm
the tool menu is not though to be a launchbar where you put things like Gimp :)

We could of course modify the toolmanager so it allows to use several tools concurrently, but I am not sure if we really want to do that.

The toolmanager works wonderfully for launching all kinds of concurrent processes.

Just be sure to use a command sequence that releases the shell (e.g. cmd /c  with a "start" command).

Also, untick the "Launch....and wait" box.

(http://img111.imageshack.us/img111/9665/graphic326200682916am6ik.png)
Title: Re: Using Custom Tools
Post by: Zlika on March 26, 2006, 04:01:17 pm
Great! It's working now when I put "cmd /c" in "Executable" and the name of the python file in "Parameters".
Thank you!