[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]
RE: [XaraXtreme-dev] Substituted fonts and Bug 1057
- From: Alex Bligh <alex@xxxxxxxxxxx>
- Date: Mon, 22 May 2006 15:45:04 +0100
- Subject: RE: [XaraXtreme-dev] Substituted fonts and Bug 1057
--On 22 May 2006 15:40 +0100 Charles Moir <CharlesM@xxxxxxxx> wrote:
I don't think this should be a writable field, because it would allow
anything as you say. Again I'd revert to the Windows version: as you
type characters, the selected highlight jumps around the font menu and
the field shows the selected font. So typing 'T' - moves the menu
selection to Tahoma, typing 'I' then refines this to show Times.
You have to type reasonably rapidly. Pausing will case the next
character to be treated as the first.
So there is no editable field being filled with the characters you type.
This is slightly different to auto-completion that you see sometimes.
Sure, I'd envisaged what would happen is the typed characters would
have an orange background and the "completed" characters a white background
(assuming you are an Ubuntu Human person - else substitute Orange for
Blue) but the entire time (despite the "custom" background rendering)
exactly one of the combo choices is actually selected - i.e. this is
really just a mechanism to speed navigation rather than there being
any different "state" to the selection. To illustrate the difference,
things like capitalization would be taken from the font name, delete
forwards doesn't make sense etc.
I thought we could use this for the colour drop-downs too. In fact, thinking
about it, why not all read-only dropdowns?