Set Program's Behaviour window

[JYM]

At least under ubuntu 10.10, CB 10.05 window to set up arguments to be passed to your compiled projects is unreadable.
Unfortunately, I could not find a way without recompiling. It seems that there is a problem with multilines text controls.
A work around is to modify the select_target.xrc file in /src/sdk/resources, suppressing the folowing line
<style>wxTE_MULTILINE</style>
which is below <object class="wxTextCtrl" name="txtParams">
recompile...
You will then get a single line, visible and usable...
By the way, do not transmit your parameters using options defined with a "-" prefix: they would be interpreted by your terminal as undefined options.. -- works well with xterm.
Hope this may be usefull!

[oBFusCATed]

I've just fixed it yesterday. It will be in the next nightly or you could apply the patch yourself (I've done so:) ).
Just replace the file in the /usr/share/codeblocks/manager_resources.zip and it the problem will be gone.

By the way, do not transmit your parameters using options defined with a "-" prefix: they would be interpreted by your terminal as undefined options.. -- works well with xterm.

What? Can you give better explanation of the problem?

[Jenna]

By the way, do not transmit your parameters using options defined with a "-" prefix: they would be interpreted by your terminal as undefined options.. -- works well with xterm.

I do this every day, and I have used different terminals on lxde, xfce, kde and gnome, but never had any problems with parameters, that allow a single "-".

[JYM]

"-" story:
If you pass arguments with "-" in the argument window of code blocks, then it is taken as an argument of the terminal command issued by codeblocks. xterm, at least, expects that the last argument is -e folowed by the code to execute. Of course, outside code blocks, no problem...

[oBFusCATed]

Hm, you've set your terminal command wrong.
Goto the Settingws->Environment->General and there is a setting for the command used to launch the terminal.
Mine is "xterm -T $TITLE -e" and it works perfectly.

[JYM]

Mine is the same (without the double quotes) and run results in a crash if I use -whatever options.... By the way if I paste the content of what follows -e on execution in a terminal, I get the help content on the valid options.
JY

[oBFusCATed]

Does "xterm -e sleep 100000" works?
If it doesn't your xterm is broken!
Then check the options and see which is the correct switch you have to use.