Hari Krishna Dara wrote:
On Wed, 25 Oct 2006 at 11:33pm, Mikolaj Machowski wrote:
On ¶ro pa¼ 25 2006, Mikolaj Machowski wrote:
In Linux terminal and GTK2 versions cursor is stuck in command line
and don't at its real position making inserting of text almost random.
Getting stuck at command-line is normal, as it is always waiting on
getchar(). I realize will not be suitable for all applications, but
works well for what I am trying to achieve. I don't however understand
the random part that you are mentioning. What exactly is happening? Is
the position where the text is inserted random?
No, just impression of randomness - user is accustomed to cursor and
when doesn't see it he is lost. In heavily restricted environment like
forms this is not so important.
m.
Yes, I agree, without cursor there is not much use for general
application. What would be nice is to have an option for getchar() that
will not move the cursor to the bottom, that way you can at least see
where the cursor is (even if that means it is not blinking).
In the meantime, I guess it wouldn't be hard to modify the function so that it
inserts a "black box" character (if available in the current 'encoding'), or
even an underscore, at the current cursor position while it is waiting for
input. This would tell the user where the cursor is. It would be non-blinking
of course, but it would be better than nothing.
Best regards,
Tony.
