Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

"Detached" console_runner?

<< < (2/3) > >>

Pecan:

--- Quote from: MortenMacFly on June 22, 2006, 03:54:50 pm ---
--- Quote from: Vampyre_Dark on June 22, 2006, 05:28:26 am ---No, but it allows you to run more than 1 window at once, which is what you want...

--- End quote ---
I know, but I have only read access to the sources that I would have to change for this. That's why I asked if it isn't nice to have a detached console_runner in addition...?!
With regards, Morten.

--- End quote ---

You can always use menubar->tools as a console_runner.
Example:


Take out the "start" if you want the shell to wait, and choose the button options you like.

MortenMacFly:

--- Quote from: Pecan on June 22, 2006, 09:58:38 pm ---You can always use menubar->tools as a console_runner.

--- End quote ---
Thanks Pecan for the hint. But in fact I guess I didn't make myself very clear. Because I know a workaround for this issue. But my question was different:
I'd like to know if I'm the only one that would be glad if an application isn't "locking" C::B after being launched. This is a project related issue, just as command line parameters. I have quite some command line tools that all report it's calculations to the console. I often want to compare the output of these tools because e.g. they share classes in common. So for debugging purposes I want to check if all (15!) tools still calculate correctly.
For now I have to use e.g. several command shells that remain open after the tool is launched so that I can compare the outputs. This could be resolved easily eighther by e.g.:
1.) Allowing a flag to run the application detached (from the "Run menu")
2.) Adding another %PROJECT_OUTPUT_FILE% macro to the tools menu.
(The second one came to me after Pecans post BTW...)
This would allow what I want: Having the currently compiled application launched detached in a window that remains open. Meanwhile I like the second idea much more - so again my question: Any objections?
With best regards, Morten.

tiwag:

--- Quote from: MortenMacFly on June 22, 2006, 10:31:39 pm ---... I have quite some command line tools that all report it's calculations to the console. I often want to compare the output of these tools because e.g. they share classes in common. So for debugging purposes I want to check if all (15!) tools still calculate correctly...

--- End quote ---
i had a similar project and redirected the output of each tool to a file, which i could then analyse with the editor.

thomas:
I'd personally do it this way... needs no change at all and works fine (if I understand correctly what you want).

[attachment deleted by admin]

MortenMacFly:

--- Quote from: thomas on June 23, 2006, 01:30:54 pm ---I'd personally do it this way... needs no change at all and works fine (if I understand correctly what you want).

--- End quote ---
Nice one, too. But:
What my tools print out are matrices of quite some size. I would have to scoll a lot up and down to compare the outputs of all the (15!) tools. In addition besides the tool's output I don't care about the other C::B messages (e.g. from the build).
I guess I'll just try to implement the macros and propose a patch... we'll see if it gets accepted or not... ;-)
With regards, Morten.

Navigation

[0] Message Index

[#] Next page

[*] Previous page