Lines Matching refs:kbdfeed

81305     No point in setting sli before if (dev->kbdfeed->xkb_sli==NULL)
98824     xkb: after making changes to the xkb ctrls, copy them back into kbdfeed.
98829     XkbUpdateDescActions was not reflected in the kbdfeed ctrls.
98833     This mainly affected keyboard repeat control as XKB uses the kbdfeed ctrls,
98854     server, the change is not handed back to the kbdfeed struct and XKB will
98858     path may be hit before the CtrlProc for the kbdfeed struct is set.
115681     The copying of dev->key relies on dev->kbdfeed to be already set up. Hence
115682     the pointers need to be reset once _both_ kbdfeed and key have been copied
134453     Xi: If the MD doesn't have a key/kbdfeed class, init the keyboard.
150146     Xi: copy feedback classes first, in some cases xkb relies on kbdfeed.
150149     the devices kbdfeed struct, which is all nice and dandy if it is NULL. When
150150     copying the device classes however, kbdfeed may not be NULL and thus
150153     By copying kbdfeed first, we avoid XkbFSLI to reference the "old" kbdfeed
150627     Xi: remove duplicate copying of kbdfeed and ptrfeed.
151992       xkbi->kbdProc= pXDev->kbdfeed->CtrlProc;
151993       pXDev->kbdfeed->CtrlProc= XkbDDXKeybdCtrlProc;
151995     If we directly copy the device classes for the VCK, pXDev->kbdfeed->CtrlProc