XKB: Don't send unnecessary NewKeyboardNotifies
In the XKB GetKeyboardByName handler, we had the following pseudocode:
if (device was last slave of its MD) {
XkbCopyDeviceKeymap(master, slave);
XkbSendNewKeyboardNotify(slave, ¬ify);
}
Even if the SendNewKeyboardNotify line nominated the correct device,
which it didn't, it's unnecessary as XkbCopyDeviceKeymap already sends a
NewKeyboardNotify on the destination device.
Signed-off-by: Daniel Stone <daniel@fooishbar.org>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
70cef8d8ba
commit
72b6639c83
|
|
@ -5902,10 +5902,8 @@ ProcXkbGetKbdByName(ClientPtr client)
|
|||
|
||||
if (!IsMaster(dev)) {
|
||||
DeviceIntPtr master = GetMaster(dev, MASTER_KEYBOARD);
|
||||
if (master && master->lastSlave == dev) {
|
||||
if (master && master->lastSlave == dev)
|
||||
XkbCopyDeviceKeymap(master, dev);
|
||||
XkbSendNewKeyboardNotify(dev,&nkn);
|
||||
}
|
||||
}
|
||||
}
|
||||
if ((new!=NULL)&&(new!=xkb)) {
|
||||
|
|
|
|||
Loading…
Reference in New Issue