How do i disable this in VS2005? i really wanna use my own not the default one
Printable View
How do i disable this in VS2005? i really wanna use my own not the default one
Huh?
It's a convenience since console apps are supposed to be run from a command prompt.
Plus I would disagree on using "your own solution."
That "press any key..." message is not there in your final EXE anyway, so what does it matter?
You can also run with debug, and it won't display that message.
I think the OP wants to use a different message instead of the standard one.
You can't really do that. In standard C++, the best you could get away with would be to print a message with cout or whatever, and then wait for input. Unfortunately, the user would have to hit enter to continue, not just any key, since C++ input is line-buffered.
Also see
http://faq.cprogramming.com/cgi-bin/...&id=1043284385
http://faq.cprogramming.com/cgi-bin/...&id=1043284385
For non-standard solutions, see
http://faq.cprogramming.com/cgi-bin/...&id=1043284392
For the heck of it, our own article :)
http://apps.sourceforge.net/mediawik...=Pause_console
You can include <conio.h> in your program. You could then do something like this:
Of course you can use whatever message you want in the cout().Code:cout<<"Press any key to continue"<<endl;
_getch();
Conio.h is non-standard, however, and thus should be avoided.
This "press any key ... " can be inconveniencing. On my console app, i have define a box area where inputs are entered ad out puts are shown. This bl##dy press any key just appears at the wrong places and messes up everything
Then just run in debug-mode and it will never appear.
And when the application runs in real life?Quote:
Originally Posted by Elysia
It is not part of your application at all - it is part of the runtime environment that MS Visual Studio creates for your application to run in - it adds the "pause" command to the end of your application OUTSIDE of the application. If you run it from a command prompt window, then you won't see it (because it's not there).Quote:
Originally Posted by csonx_p
--
Mats
Oh! and what if i needed it? I mean i'm writing an application assuming that everything which shows now will show as is on the user side .. If i'm hearing you correctly you state that the "press any key.." message wont show when running the exe file ...Quote:
Originally Posted by matsp
It will not, simply because command line apps are not supposed to be run from the shell. They are supposed to be run from the cmd, if anything.
Ok, i've learnt that i could just use getch() instead of system("pause") which causes "press any key ..." .. But both seem not to be a good idea from few ... any ideas as to which function to call instead of the two to pause/halt ?
The real question here is "why do you want to do that..."Quote:
Originally Posted by csonx_p
--
Mats
Working with console applications, sometimes you need to echo somethingQuote:
Originally Posted by matsp
What do you mean?Quote:
Originally Posted by csonx_p
--
Mats
Well for some strange reasons the text on the screen would pass without you seeing it, especially if you clearing screens for new text. I need pause for thatQuote:
Originally Posted by matsp
NOT clearing the screen would solve that particular problem.Quote:
Originally Posted by csonx_p
But if you are doing screen clearing, then you are using non-portable code [or calling system() - which I think is worse], so you may as well throw in a a "getch" into the mix of non-portable functions. Just make sure that you put it in a special place, so that when you try to do the same thing on a different OS, you can easily replace what the actual function is.
--
Mats
Mhh, its good that i raised this issue then because a friend told me its not good to clear screens, but he didn't explain why. Exactly how do i transfer outputs on new screens? Obviously i can put the entire program on the same screen ... I would like to write portable code, so help me please!!!!Quote:
Originally Posted by matsp
If you want to write portable code, you should probably give up on console apps.
Typically, whatever you do, you cannot clear the screen is a truly portable way. Here's more info anyway:
http://faq.cprogramming.com/cgi-bin/...&id=1043284385
My guess is you are suggestion that i useQuote:
Originally Posted by Elysia
over system("cls");, which am happy to do if it means portability .....Code:#include <windows.h>
void clear_screen ( void )
{
DWORD n; /* Number of characters written */
DWORD size; /* number of visible characters */
COORD coord = {0}; /* Top left screen position */
CONSOLE_SCREEN_BUFFER_INFO csbi;
/* Get a handle to the console */
HANDLE h = GetStdHandle ( STD_OUTPUT_HANDLE );
GetConsoleScreenBufferInfo ( h, &csbi );
/* Find the number of characters to overwrite */
size = csbi.dwSize.X * csbi.dwSize.Y;
/* Overwrite the screen buffer with whitespace */
FillConsoleOutputCharacter ( h, TEXT ( ' ' ), size, coord, &n );
GetConsoleScreenBufferInfo ( h, &csbi );
FillConsoleOutputAttribute ( h, csbi.wAttributes, size, coord, &n );
/* Reset the cursor to the top left position */
SetConsoleCursorPosition ( h, coord );
}
The part that means portability is the abstraction of clearing the screen to a function, in this case one named clear_screen. You could also have written:Quote:
Originally Posted by csonx_p
To actually be portable, you would need to implement clear_screen() differently as required by each supported platform, and then build the program such that the correct version of clear_screen() is chosen for the given platform.Code:void clear_screen()
{
system("cls");
}
There's no way to do it portable since C/C++ lacks facilities to clear the screen.
Everything you do will be unportable, relying on some platform-specific API.
But that mentioned, the best thing to do is take laserlight's advice. This is typically how big libraries make themselves portable, including Boost I would think.
Downloaded pdcurses, just by including <curses.h>, i get strange compile warnings & errors...
some here ..
etc...Code:warning C4005: 'MOUSE_MOVED' : macro redefinition
error C2059: syntax error : '('
error C2039: 'usr_iter' : is not a member of 'std::vector<_Ty>'
error C2668: 'std::vector<_Ty>::end' : ambiguous call to overloaded function
anyone????????????
Or is it because i have windows.h included somewhere?
Might be #define clashes, or some such. It is difficult to say.
The "macro redefined" usually tells you where it was previously defined [although sometimes you have to look at the raw compiler output rather than the error summary to see that].
Including windows.h should be limited to places where you REALLY have to do that - if nothing else because it is really large and it takes quite some time to compile lots of files that include windows.h.
You probably do not want to include curses.h and windows.h in the same source file - there should be no need to use windows.h in a curses application - if you are calling some windows function that curses doesn't have it's own version of, then you probably want to isolate that, as described previously, in a "windows stuff" source file, and then include a header file like "osindeps.h" that define the OS dependant functions in a OS-independent way [for example, if you need a delay/sleep function, Windows and Linux do different variants here, so you'd put your own os independent function declaration in osindeps.h, and then make the translation in your widnows_stuff.c or linux_stuff.c].
--
Mats