Bug 5783

Could you please have a look at "cherrycyboard". It seems it has all the keys
you need. Also, what I can do without any harm - expant "microsoftpro" with
those two keys. Would it be ok for you?

(In reply to comment #1)
> Could you please have a look at "cherrycyboard". It seems it has all the keys
> you need.

I', sorry, but my X.org 6.8.2 doesn't include a symbol map for "cherrycyboard"
-- only for "cherryblue", "cherryblueb" and "cherrybluea". Some of them are
indeed called "CyBo@rd", but the symbol mappings are somewhat different from the
MS Nat. Erg. Kbd. 4000.

> Also, what I can do without any harm - expant "microsoftpro" with
> those two keys. Would it be ok for you?

Of course, thanks! -- I've already done so during testing. But anyway, will
those keys be included in the X.org distribution? Or are they already? (And,
BTW, how about the unsupported favorite keys and the zoom slider? -- Will they
be supported in 7.0?)

> I', sorry, but my X.org 6.8.2 doesn't include a symbol map for "cherrycyboard"
> -- only for "cherryblue", "cherryblueb" and "cherrybluea". Some of them are
> indeed called "CyBo@rd", but the symbol mappings are somewhat different from the
> MS Nat. Erg. Kbd. 4000.
Since this bug is filed agains xkeyboard-config - could you please try it? It
has this layout included.

> Of course, thanks! -- I've already done so during testing. But anyway, will
> those keys be included in the X.org distribution? Or are they already? (And,
> BTW, how about the unsupported favorite keys and the zoom slider? -- Will they
> be supported in 7.0?)
xkeyboard-config is not officially part of 7.0 - but most distros include it
anyway. And in 7.0 Release Notes it is recommended to use xkeyboard-config as
really maintained keyboard database.

Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler

No reply for 2 years

It seems that the original reporter got lost.
However I have the same problem. Microsoft Natural Keyboard 4000 is not supported even though it is probably one of the most sold natural keyboards.

In the current state only two problems exist:

1. Zoom keys are not supported
 That is not a problem that can be solved easy as the keyboard registers an additional USB device for them.

2. The Favorites keys on the top are not working.
 They are marked 1 to 5.

For the second problem I added the following keys to the evdev section in xkb/symbols/inet

    key <FK14>   {       [ XF86Launch3           ]       };
    key <FK15>   {       [ XF86Launch4           ]       };
    key <FK16>   {       [ XF86Launch5           ]       };
    key <FK17>   {       [ XF86Launch6           ]       };
    key <FK18>   {       [ XF86Launch7           ]       };

Note: I did not use XF86Launch1 and XF86Launch2 as they could not be grabbed under KDE for an unknown reason.
Also Qt adds 2 to the numbers anyway, so XF86Launch7 is displayed as "Favorite (9)"

It is still confusing that there is a Microsoft Natural Keyboard 7000 (which you can't buy anymore) and no 4000.

(In reply to comment #6)
> It seems that the original reporter got lost.
I'm back here, just hadn't kept track of this ticket for a long time.
> 1. Zoom keys are not supported
>  That is not a problem that can be solved easy as the keyboard registers an
> additional USB device for them.
Thanks for that background information!
> 2. The Favorites keys on the top are not working.
>  They are marked 1 to 5.
> 
> For the second problem I added the following keys to the evdev section in
> xkb/symbols/inet
> 
>     key <FK14>   {       [ XF86Launch3           ]       };
>     key <FK15>   {       [ XF86Launch4           ]       };
>     key <FK16>   {       [ XF86Launch5           ]       };
>     key <FK17>   {       [ XF86Launch6           ]       };
>     key <FK18>   {       [ XF86Launch7           ]       };
Thanks a lot!
> Note: I did not use XF86Launch1 and XF86Launch2 as they could not be grabbed
> under KDE for an unknown reason.
For me they worked (KDE 4.4.1).  But I have experienced similar problems.  My KDE does not recognize Ctrl+Shift+F1.
> Also Qt adds 2 to the numbers anyway, so XF86Launch7 is displayed as "Favorite
> (9)"
That also happens to me.
> It is still confusing that there is a Microsoft Natural Keyboard 7000 (which
> you can't buy anymore) and no 4000.
Indeed.  I'm using the "7000" layout for my 4000 keyboard now.

(In reply to comment #7)
> (In reply to comment #6)
> > Note: I did not use XF86Launch1 and XF86Launch2 as they could not be grabbed
> > under KDE for an unknown reason.
> For me they worked (KDE 4.4.1).  But I have experienced similar problems.  My
> KDE does not recognize Ctrl+Shift+F1.
I tried to debug the problem with XF86Launch1. 
The kglobalaccel does not get the key events even though it grabs them. My impression is that they are either already grabbed by somebody or for some unknown reason not be able to be grabbed.
Maybe Ctrl+Shift+F1 has the same problem.

> > Also Qt adds 2 to the numbers anyway, so XF86Launch7 is displayed as "Favorite
> > (9)"
> That also happens to me.
The reason is that Qt gives the numbers 1 and 2 to other favorite keys. Nothing that should be changed until Qt5 at least.

> > It is still confusing that there is a Microsoft Natural Keyboard 7000 (which
> > you can't buy anymore) and no 4000.
> Indeed.  I'm using the "7000" layout for my 4000 keyboard now.
I would propose to add the five favorites to the 7000 layout and change the description in xorg.xml to point out that this layout also works for the 4000.
A comment in the rules file should say the same.

I am not forgetting this and I still think it's quite important.
In my group three out of four people have 4000 keyboards.

Ralf, in the current symbols/inet(evdev) I see:
    key <FK13>   {      [ XF86Tools         ]       };
    key <FK14>   {      [ XF86Launch5       ]       };
    key <FK15>   {      [ XF86MenuKB        ]       };
What would you propose to do with existing mapping? Should we just add mappings for FK16-FK18?

I would appreciate the patch for symbols/inet (and rules/base.xml.in if you think that the info about 4000 model should be added).

The FK15 symbol was added to the symbols after my bug entry. 
Also I don't know what keyboard uses
    key <FK14>   {      [ XF86Launch5       ]       };
    key <FK15>   {      [ XF86MenuKB        ]       };

If they are valid (I assume they are) then we have a conflict.
As I am not expert in keyboard definitions I can't decide if adding a new model is really the way to go. It appears that there are too many models already.
I am sure that we could merge some of the Microsoft definitions and add the missing keys there.

Could you tell me what you think is the best solution:
1. adding the missing keys to inet
2. adding and merging existing MS keyboard definitions
3. creating a new keyboard

This mapping was a result of fixing #25835

I merged:

http://cgit.freedesktop.org/xkeyboard-config/commit/?id=01d742bc5cd22543d21edb2101fec6558d4075db

I hope it is ok for you

Perfect,
thank you.