`Command.RunCommand()` documented incorrectly

Help & Support
1

Command.RunCommand() is documented:

Calling this method is the equivalent of adding the single line with the AddLine method and then calling the Run method.

This isn't quite true:

// Goes down 2 items.
var cmd = DOpus.Create().Command();
cmd.RunCommand("Select NEXT");
cmd.RunCommand("Select NEXT");

// Goes down 3 items.
var cmd = DOpus.Create().Command();
cmd.AddLine("Select NEXT");
cmd.Run();
cmd.AddLine("Select NEXT");
cmd.Run();

RunCommand() is like calling Clear() also. (Even more internal calls?)

But since these go down just 2 items, it's better described as a nested layer, right?

// Goes down 2 items.
var cmd = DOpus.Create().Command();
cmd.RunCommand("Select NEXT");
cmd.AddLine("Select NEXT");
cmd.Run();

// Goes down 2 items.
var cmd = DOpus.Create().Command();
cmd.AddLine("Select NEXT");
cmd.Run();
cmd.RunCommand("Select NEXT");

PS: Maybe a new "documentation" category in "Help & Support" would be useful, so I don't have to label documentation bugs or imperfections as software bugs.

2

Equivalent doesn't mean "exactly the same in all ways". The outcome is equivalent.

In reality RunCommand() doesn't modify the object's command lines at all.

3

In your first example, it goes down 3 items because:

// Goes down 3 items.
var cmd = DOpus.Create().Command();
cmd.AddLine("Select NEXT");
cmd.Run();

That goes down 1 item.
Then

cmd.AddLine("Select NEXT");
cmd.Run();

You add a second time Select NEXT but when you Run that command, it now has 2 lines: The first Select NEXT you added before you ran it the first time, and the second one you added before the second run.
So that second Run goes down 2 lines.

4

Okay, "documented incorrectly" and "isn't quite true" probably was too strict. But I think it could be clearer. Maybe write:

Calling this method is the equivalent of adding the single line with the AddLine method and then calling the Run method, but without affecting the instruction lines of the command.