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

Command line arguments evaluation

(1/2) > >>

danselmi:
Hi

Attached a patch to solve two issues:
1. The commandLine argument --file=c:\foo\bar.cpp:42
   should make CB open the file c:\foo\bar.cpp and show line 42.
   in fact it only opened the file without showing line 42.
   The reason for this is the colon after the drive letter.
2. If a cb instance is already running, the app of a second instance doesn't evaluate command line arguments given by plugins.
   With this patch, it becomes possible for plugins to receive command line arguments in the first instance (additional event).
   The realized solution does send the cmd line to the first instance where it is possible for plugins to check the Parse results.
   Patch to cbDiff-plugin http://forums.codeblocks.org/index.php/topic,12829.0.html to show the usage is also attached.

Any objections? If not, I will apply it in a few days.

wxWidgets bug which brings old arguments on new Parse() runs is already corrected, see here: http://trac.wxwidgets.org/changeset/77502

Is anbody maintaining the cbDiff plugin?

regards danselmi

MortenMacFly:

--- Quote from: danselmi on August 29, 2014, 02:47:28 pm ---Is anbody maintaining the cbDiff plugin?

--- End quote ---
Not to my knowledge. In fact I rarely used it... is it still working OK?

danselmi:

--- Quote from: MortenMacFly on August 29, 2014, 04:51:17 pm ---
--- Quote from: danselmi on August 29, 2014, 02:47:28 pm ---Is anbody maintaining the cbDiff plugin?

--- End quote ---
Not to my knowledge. In fact I rarely used it... is it still working OK?

--- End quote ---
Yes the version from https://github.com/ywx/cbDiff/trunk is still working.

MortenMacFly:
...btw: with respect to the patch:

This line:

--- Code: ---delete wxMessageOutput::Set(new cbMessageOutputNull); // no output
--- End code ---
in app.cpp will cause a compilation error:

app.cpp:1096:44: error: cannot allocate an object of abstract type '{anonymous}::cbMessageOutputNull'
app.cpp:297:7: note:   since type '{anonymous}::cbMessageOutputNull' has pure virtual functions

This should be fixed before a possible commit.

danselmi:

--- Quote from: MortenMacFly on September 05, 2014, 08:19:59 am ---...btw: with respect to the patch:

This line:

--- Code: ---delete wxMessageOutput::Set(new cbMessageOutputNull); // no output
--- End code ---
in app.cpp will cause a compilation error:

app.cpp:1096:44: error: cannot allocate an object of abstract type '{anonymous}::cbMessageOutputNull'
app.cpp:297:7: note:   since type '{anonymous}::cbMessageOutputNull' has pure virtual functions

This should be fixed before a possible commit.

--- End quote ---

Which wx version have you tested? 2.8 or 3.0?

Navigation

[0] Message Index

[#] Next page