[Bug 164274] allow users to create sets: layout and model

[Maciej Pilichowski]

https://bugs.kde.org/show_bug.cgi?id=164274





--- Comment #7 from Maciej Pilichowski <bluedzins wp pl>  2010-05-24 20:20:44 ---
> I am still a bit confused by what you're saying. From
> your earlier use case I saw this: two physical keyboards with
> different set of keys, which means that each keyboard needs to have
> its own keyboard model set.

One of the cases, yes. One note -- not needed, but useful because of
productivity.

> Currently setxkbmap allows to specify keyboard models (as well as
> layout set and xkb options per keyboard) and keyboard daemon can
> detect when new keyboard is hotplugged. 

Again, it is one of the case. Another is two keyboards are plugged in at the
same time.

> Thus it should be possible 
> to specify different configuration for each hardware keyboard and
> user does not have to switch it manually as keyboard daemon can
> detect new hardware and configure it appropriately.

Ok, but user could ALSO want to switch it manually. I don't want to unplug the
keyboard just to write in Russian (for example).

Btw. I edit keyboards so heavily that it is impossible for me to set all the
keys in layout (for example caps acting as alt) so I have to edit model too.
And then layout work the best only with connection with given model. 

https://bugs.kde.org/show_bug.cgi?id=177889

No. One thing is creating sets (layout+model), and another thing is adding
feature for _automatic_ switch. This report says nothing about automating
switches, detecting keyboard, and so on. It only says, user should be able to
switch it. Anything above is a nice bonus.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.