when opening via command-line with files specified, a new file is created too

[bfriedman]

This is a: is it a bug/feature/design change/user-error/etc? Question.

I am pipelining FreeCAD into a larger content management system.

I have it to the point that my system opens FreeCAD via command-line and specifies a file to open in that command-line.

However, when I open FreeCAD this way, it pedantically adheres to the preference for, "create new document at startup."

That is to say: I end up with two files open if this preference is set to True. First, the one I specified on the command-line, and also a new, "Unnamed" file. And yes, if I turn off that preference, I get just the file on the command-line without the "Unnamed" file.

My question: Shouldn't it only "create new document at startup" when no files are specified on the command-line? If I'm specifying files to open, you'd think there's no need to also create an empty one in most cases.

Or, perhaps a command-line flag for specifying the desire to create a new file, or not create a new file?

Or am I missing something?

Is this a bug or intended behavior? Feature request?

Thanks for taking a look.

-brad

[wmayer]

My question: Shouldn't it only "create new document at startup" when no files are specified on the command-line? If I'm specifying files to open, you'd think there's no need to also create an empty one in most cases.

I think you are right that when opening an existing project then no additional empty is needed.

Is this a bug or intended behavior? Feature request?

Feel free to open a feature request in the issue tracker.

[Kunda1]

OP opened issue #3443