Some of the less intuitive parts of MSKLC's user interface

by Michael S. Kaplan, published on 2007/08/10 02:04 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/08/09/4318216.aspx


A while back, Giovanni asked me via the contact link:

Hi Michael,

I am writing this to you because I have found your blog and you seem pretty well informed about MSKLC.

Using MSKLC (a tool I've long waited for!), I've been trying to create a windows keyboard layout that duplicates the very convenient "italian pro" layout of Mac OS X, in which the Alt key allows to enter a wide selection of unicode characters.

But now I have a problem: MSKLC seems not to allow me to define a AltGr state as a dead key. In AltGr state, the "set dead key" menu entry is shadowed.

For example, I would like to use AltGr+u as a dead key for umlauts, etc, the way macintoshes do.

Do you know if this is possible?

Thanks!

I do fear that I may have taken too long to get back to Giovanni, especially since the answer is that it is quite possible and works quite well! :-(

First I had better explain.

Let's say that you load up MSKLC and get to be looking near that VK_U key in the ALTGR shift state:

As Giovanni indicated, the dead key choice is disabled:

However, the truth is that the option is also disabled in every other shift state too!

The problem here is that you have to make sure a Unicode code point is assigned to the key before the option is enabled. So one can assign (for example) U+00a8 (DIAERESIS) to the key:

and then once a single code point is assigned:

the menu option is enabled:

Now note that if at any time you chose that Properties for VK_U in all shift states you would always have the dead key option available once you added a character.

The particular bit of non-intuitivosity of the shortcut menu item is a side effect of the MSKLC development process I first described in this post:

...it highlighted the pattern of those weekly meetings. I would show the current state of the UI, Simon or Cathy would bring up a feature they felt was crucial, I would push back and explain why it was not feasible, they would grudgingly accept this, but the issues they brought up would keep bothering me until I thought of a way to make it feasible. Then I would show it to them the next week. I am pretty sure that was how the meeting became known as D&P in the first place....

The particular problem they had was how hard it was to go to the full dialog and hit the dead key button -- they wanted a way to get there more directly.

Finally, I put in that shortcut menu item and all it required to work was a key assignment. They loved it, since it was so much easier to reach than the other way (and in out informal usability testing it seemed much more discoverable).

However, I'll admit that it is really only intuitive for people who would naturally be putting in the character assignment first; for people who go into it wanting to assign a dead key, it is too easy to run into the same problems as Giovanni did.

I had prototyped a separate dialog popping up to let you enter the dead key first, but this appeared less intuitive and more complex to people (not to mention the extra test cost), so in the end this idea was scrapped.

Though perhaps it could be considered for a future version....

 

This post brought to you by ยจ (U+00a8, a.k.a. DIAERESIS)


no comments

referenced by

2007/08/10 I've been to the desert on a dead key with no name

go to newer or older post, or back to index or month or day