As has been said, control key combinations are a pain in Mac OS X, but
can be done, by defining a new set of modifiers.
That said, if you've got a working resource-based keyboard layout, you
can convert that to an XML keyboard layout. The simplest way is to open
Ukelele, make your resource-based keyboard layout the current input
source, and then choose New From Current Input Source. That will create
a new keyboard layout that you can edit in Ukelele and save wherever you
want.
If the old keyboard layout doesn't work on your system, then it's
possible to do it with the command line, using one of the tools that is
bundled with Ukelele. If you need to go down this route, ask, as it's a
little complicated to explain.
John
--
John Brownie, john_b...@sil.org or j.br...@sil.org.pg
Summer Institute of Linguistics | Mussau-Emira language, Mussau Is.
Ukarumpa, Eastern Highlands Province | New Ireland Province
Papua New Guinea | Papua New Guinea
Why do you insist in using ctrl key as modifier key when working with keylayouts? What is the clue? (sorry, perhaps you explained it, but I do not remember). In my view, you uselessly complicate your life. This would make sense if you are very happy after that hard work.
Best
> --
> You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
> To post to this group, send email to ukelel...@googlegroups.com.
> To unsubscribe from this group, send email to ukelele-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ukelele-users?hl=en.
>
> Thank you for your help. Unfortunately, my resource based layout has
> stopped working with Leopard (or Snow Leopard, I just tested it), so
> this is not a solution, unless you help me with the command line
> tools.
OK, that's a possibility, but it might be possible to do it with
Ukelele, as I describe below.
> The problem I have been having with Ukelele is that when I create the
> various modifiers Control, Control-Shift, Control-Option and Control-
> Shift-Option, every time I create a new key in one of them, it changes
> the same key in at least one of the others. I have tried several times
> and have the same problem. I could understand this behavior if I had
> not created ALL of the modifier combinations (because things would
> then be duplicated in some way in the not created ones), but it seems
> to happen even when they are all created.
It looks as though what is happening is that the new key maps are linked
to the old ones. There are a number of ways this can happen, but you
don't need to know about that.
One way to fix this is that, when you create a new modifier combination,
choose "Copy of an existing key map" and check the "Unlinked" check box.
That will give you an independent set there, though you would have to
then change any existing outputs to what you want.
A second is to create the new modifier combination, and then explicitly
unlink it with the "Unlink Modifier Set" command, which unlinks all keys
with that modifier combination.
It's a puzzling thing when it happens, but it's not that hard to get
around when you know what has caused the strange behaviour.
Hope that helps!
John
--
John Brownie, john_b...@sil.org or j.br...@sil.org.pg