• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Command Prompt

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,335
Country
netherlands
Discussion thread for Command Prompt. If you would like to add a comment, click the Post Reply button.
 
Hi,

What was the thought behind creating this article and another one called Command Prompt Window? Would it not be easier for the user if all information was put in one article?

Let me know what kind of structure you had in mind for the information (which info in which article) and then I can help with filling it I guess.
 
Hi Folks

Arno -
I seperated the two

The Command Prompt Window is for the window that the user is working in, with whatever tool they are using.
This contains the history of actions carried out at the prompt, and their matching results.
This would be the main article.


The Command Prompt is for the prompt itself,
which is only the active line where the cursor is.
I intended this for only basic items, e.g. removing the path from the prompt.


HTH
ATB
Paul
 
Last edited:
I just added text in the other "Discussion Topic" describing "Four Methods" for adding the Command Prompt to the "Right Click Menu" in Windows Explorer, as this is not present by default (at least not in WinXP).

Being able to highlight any folder on the tree, right click and open a Command Prompt (Box) in that folder is very helpful.

I will leave it to the Wikian Experts to integrate any or all of it as they see fit. ;)
 
Hi Paul,

BASys said:
Arno -
I seperated the two

The Command Prompt Window is for the window that the user is working in, with whatever tool they are using.
This contains the history of actions carried out at the prompt, and their matching results.
This would be the main article.


The Command Prompt is for the prompt itself,
which is only the active line where the cursor is.
I intended this for only basic items, e.g. removing the path from the prompt.
Click to expand...

To me it sounds then that the second article is not really of interest to the average designer. Wanting to hide the path or so is not really something that is done in general. I guess most people want to know how to use it (how to use cd, how to call their compiler, etc).
 
Hi Folks

Arno -
I agree it's generally not of interest
but is nescessary to hold specific Command Prompt matters.

e.g. Path
For a default SDK installation,
the Bglcomp path is 104 chars long,
and thats before you start entering any command.

AFAIK the default Command Prompt Window is only ?80? chars wide.
(Can't remember as mine was modified years ago).

This wraps any input commands,
and makes it difficult to comprehend.

I intend to add other relevant items later.

ATB
Paul
 
Last edited:
You must log in or register to reply here.
Back
Top