matko

how can i write text in just one line of console?

I'm trying to make process indicator with rotatiting '/' '|' '\' '-' signs in the center of console.

I also have this problem: Can't compile this

ERROR: New line in constant.

How to override this?

Matko

L7Sqr

To address the first issue:
You need to output a backspace character each time you want to 'rotate' the bar. I think the backspace is \b, but not sure.
Notice that if you are not preforming any action other than spinning the bar output buffering will really screw with what you get, you will need to figure a way to 'not' buffer the output.

The second problem is the fact that '\' is an escape character.
Whatever follows it takes on special meaning (if any). In this case you are telling cout to output a '"' character which would normally terminate your string.
Try
And you should get better results.

__________________
"...and though our kids are blessed their parents let them shoulder all the blame."
- The Quiet Things That No One Ever Knows [BrandNew]

DaWei

You can set up your stream to be unbuffered. A quick way to see the influence on what you're trying is to use cerr instead of cout. It is unbuffered by default. With no buffering you don't have to call flush (or use endl).

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

matko

Tank's its worrking!
cerr<<" \\";

Matko

Ooble

Note that you should only use cerr for debugging, error messages, etc. cout is for output, cin for input, and cerr for error messages.

__________________
Me :: You :: Them

DaWei

Really? It's just an unbuffered stream, which one would want for errors, but I don't think it's written in stone anywhere. All these streams can be redirected (and their buffering altered, for that matter).

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Ooble

Of course. However, the main purpose of each is reflected in the name. It matters because other coders reading the code will expect to see output sent to the device using cout, and error messages using cerr.

__________________
Me :: You :: Them

DaWei

Don't think I don't see you point, Ooble, because I do. Of course their names are meant to be mnemonic, and they are provided to ease their use for the purposes listed, and the clarity of the code could be affected.

You will find, however, that I have a natural opposition to unilateral dicturms, as contrasted with suggestions. "...you should only use...", your words, are a dictum, but would better be phrased as a recommendation. I know people with more skill than I who deal in dictums. "You should only run your programs from the command line." Horse hockey.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Ooble

OK, I see where you're coming from. Yeah, when I say "you should", I mean "it's recommended that". Happy? :p

__________________
Me :: You :: Them

DaWei

My problem wasn't with the "should", but with the "only" :p. Sure, I'm a happy camper .

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers