![]() ![]() Edit the nf file by running the following command and pressing Enter ( Figure 2):.If it does disappear, and comes back after switching back, then creating a rule file in /etc/udev/rules.d directory should be all that is needed for full automation.NOTE: Your Id number is different as each computer pulls and assigns the ids differently. If that really ever happens, the current code will fail and we'll have to take a different approach and different code to automate the scroll speed.īut if our current approach is correct (which means your above statement is not correct in the example case of you last output of xinput), then just confirm whether the mouse disappears from the output of "lsusb" or not when you switch to the Windows PC via the KVM switch. Since the proposed code always picks the higher ID (under pointing device category), it will pick "11", not "10". Because the one immediately after the XTEST pointer (which according to the highlighted part of your above statement) has the ID "10", while the higher one is "11". However, if by the highlighted part you mean the entry immediately under the Virtual core XTEST pointer, then the code I proposed will fail in the scenario such as one which you have posted the last output of xinput from. I believe I've explained the first part of your above observation. Xendistar wrote:It is either one of the two ID's in the top section of the xinput response, normally just under the Virtaul core XTEST pointer. ![]() Even if you are not using the keyboard interface, it is there ready for use. ![]() Just in case there is any confusion remaining - you are seeing the same device name ("Microsoft.Transceiver") under "Virtual core keyboard" category also because your wireless receiver also provides an interface for the keyboard so the same receiver can be used to connect both a wireless mouse and a keyboard to the system. ![]() Therefore, when I say the "Higher ID", I mean the higher one under the "virtual core pointer" category, excluding the ID that is under the keyboard category because here we are talking about the mouse and keyboard is not our concern. mouse, trackball, light pen, touchpad etc. "Virtual core keyboard" is the category of keyboards, and so everything under that category is either a keyboard itself (real or virtual), or something that provides 'Keys' to control something.Įverything under "virtual core pointer" will be a pointing device, e.g. Xendistar wrote:What I have noticed is that the mouse ID that appears in the lower section of the xinput response (below virtual core keyboard), that one is never in control of the mouse and returns an error if I try to set the scroll speed I have put the command in the auto startup of XFCE which works, but as my PC runs 24\7 (currently 22day plus running) it is only any good on those rare occasion I reboot. (the picture is the older version with PS2, mine has USB) It is just a simple 4 port KVM (I can connect 3 PC's to one monitor, keyboard and mouse but only have three at the moment), there are four button numbered 1 to 4 I believe creating a custom udev rules file in /etc/udev/rules.d directory should work. Like Head_on_a_Stick, I also think we'll have to deal with udev in such case. In any case, both the rc.local or startup applications trick can set the speed only during the system startup, not after that. Can you check and confirm (or correct) that please? (hint: check xinput and the command suggested at the bottom of this post) If so, the xinput settings (and probably the device ID too in xinput) may be resetting everytime you switch back. And that guess is - it probably *disconnects* the keyboard/mouse (physically via bandswitch ICs, or logically via software control - I'm not sure) to connect it to the other computer when you switch, and reconnects back when you switch back. I have never used one, so can only guess how it works. However, I'm a bit unsure about the KVM (I'm assuming you mean a hardware KVM *switch*). But doesn't the Startup method you used earlier (as suggested by Head_on_a_Stick) work with this code? Alternatively, you can also add this code to your /etc/rc.local file (insert the code just before the last line - "exit 0") to run it during startup. Sometimes some settings could be stored in binary files, requiring us to modify the source code and compile it again (obviously an overkill for our purpose). I don't know where the defaults for pointer devices is stored. Xendistar wrote:Alternatively is there a way to automate the process so that everytime I come back into Linux the command is run or maybe, edit the default settings, there must be somewhere where the scroll wheel speed default is stored? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |