octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUI font and cursor location


From: Michael Goffioul
Subject: Re: GUI font and cursor location
Date: Sun, 29 Jul 2012 12:44:14 +0100

On Sun, Jul 29, 2012 at 12:18 PM, Doug Stewart <address@hidden> wrote:

Could you also provide a full description of the problem:
- the font you use
- the steps needed to reproduce the issue
- a screenshot of the issue

Jacob, is there a way to revert back to a block cursor? I've reverted my qterminal repo to 186cf3960cfa0c2752b77eba18af24cd0853c12a, but I can't change the cursor shape, it's always an Ibeam whatever I select in the preferences dialog (changing blinking works, though).

Michael.

I thought I did give a full description.

In qt
compile and run qterminal using the default font and font size
fill one line with characters, any characters.
using the left and right arrows move back and forth on the same line.
watch how the characters move left and right as the cursor moves past each character.

Now change the default font size to 8 and do the same
etc.

This does not tell me which font you're using. I can observe something similar when the terminal widget is using a non-monospace font. But that's not an issue, because the terminal widget is NOT supposed to be used with a non-monospace font (the problem here is that when the config file is empty, the GUI picks up a non-monospace font, and that's a bug, because it should pick up the system default monospace font).

Now when I open the preferences dialog and go to the terminal tab, I can change the font size, but as the font selector is now only filled with monospace fonts (defaults to "Courier New" on my system), this also change the font and the cursor behaves normally afterwards.

I've tried with 3 monospace fonts I have installed on my system and they all work fine. If you are able to reproduce the problem with a monospace font, could you tell me which one? (and a screenshot would also help)

Thanks,
Michael.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]