Originally posted by oiaohm
View Post
Being under resourced is a big problem.
The reality here is hard. There are many surveys on what setting users change with windows. In university and business computer networks its important to know what setting changes you can in fact disable and users will not notice. The reality is 90% of users have to have a use able default settings because they are not going to change the mouse/touch pad settings.
Hard fact just because Windows or any other OS provides a feature does not mean many users in fact use it. So out the box defaults on touchpads, mice. keyboards... have to be generically decent as majority of users need that as that the only setting they will be using.
Windows does not allow you to change everything with input devices. The changes you make in Windows is already have limits placed on it by the device profile.
Yes like it or not people to complain about Windows not providing enough options either. So windows does not allow you to make enough changes to fix touchpad issues either. Yes this is because you are stuck behind the limitations of the device profile that you cannot change and will not be changed by the vendor at all. Remember libinput you submit data on issue with a device profile new versions to come out fixing it.
Charlie68 reality here Linux and Windows sux in different ways with input devices.
1) Windows if the device profile in a input driver is wrong the vendor is 99.9% of the time never going to fix it. Why that driver that came with windows computer most likely no longer has a developer so is a completely dead not update able item. libinput we are lucky here is a device profile issue is fixable where windows users are stuck with broken device profiles and end up buying a new computer to fix. Yes needing to submit a bug report to fix your device is better than the Windows answer with device profile problems of go buy a new computer because there is no developer here to process you complaints or fix it.
2) Window provides a few minor alteration options with GUI that are not enough to deal with major touch pad issues.
So Windows does not display solution either.
The reality here the proper fix requires someone who is a developer who can make decent GUI tools to join libinput. Then processed to take the diagnostic tools that libinput provides and make a GUI interface to profile the device including create custom profile. A tool like this has to exceed what Windows offers because the Windows offering presumes you have a base device maker profile to work on top of that on Linux you don't have in a lot of cases and the provided base profile with windows can be horrible wrong with no way to fix it.
Yes who is going to pay or be that GUI developer to fix this problem properly.
The reality lot of the stuff you are being asked to-do with libinput command line tools to fix a touch pad you have to-do so you have a profile of the device. GUI walking you though the process could in a few places could be done into mini games to make the process more fun and still collect the need data.
Charlie68 the problem here is you have been very tunnel visioned when you step back look at input devices from a big picture point of view it does not matter if you look at Windows, Mac, Linux, Android... Its all broken just in different ways. No party at this stage has the complete fix. The complete fix will take serous resources that libinput is missing and will require a profile device tool as in all that debuging tool crud of libinput presenting in a user friendly way.
The reality here is hard. There are many surveys on what setting users change with windows. In university and business computer networks its important to know what setting changes you can in fact disable and users will not notice. The reality is 90% of users have to have a use able default settings because they are not going to change the mouse/touch pad settings.
Hard fact just because Windows or any other OS provides a feature does not mean many users in fact use it. So out the box defaults on touchpads, mice. keyboards... have to be generically decent as majority of users need that as that the only setting they will be using.
Windows does not allow you to change everything with input devices. The changes you make in Windows is already have limits placed on it by the device profile.
Yes like it or not people to complain about Windows not providing enough options either. So windows does not allow you to make enough changes to fix touchpad issues either. Yes this is because you are stuck behind the limitations of the device profile that you cannot change and will not be changed by the vendor at all. Remember libinput you submit data on issue with a device profile new versions to come out fixing it.
Charlie68 reality here Linux and Windows sux in different ways with input devices.
1) Windows if the device profile in a input driver is wrong the vendor is 99.9% of the time never going to fix it. Why that driver that came with windows computer most likely no longer has a developer so is a completely dead not update able item. libinput we are lucky here is a device profile issue is fixable where windows users are stuck with broken device profiles and end up buying a new computer to fix. Yes needing to submit a bug report to fix your device is better than the Windows answer with device profile problems of go buy a new computer because there is no developer here to process you complaints or fix it.
2) Window provides a few minor alteration options with GUI that are not enough to deal with major touch pad issues.
So Windows does not display solution either.
The reality here the proper fix requires someone who is a developer who can make decent GUI tools to join libinput. Then processed to take the diagnostic tools that libinput provides and make a GUI interface to profile the device including create custom profile. A tool like this has to exceed what Windows offers because the Windows offering presumes you have a base device maker profile to work on top of that on Linux you don't have in a lot of cases and the provided base profile with windows can be horrible wrong with no way to fix it.
Yes who is going to pay or be that GUI developer to fix this problem properly.
The reality lot of the stuff you are being asked to-do with libinput command line tools to fix a touch pad you have to-do so you have a profile of the device. GUI walking you though the process could in a few places could be done into mini games to make the process more fun and still collect the need data.
Charlie68 the problem here is you have been very tunnel visioned when you step back look at input devices from a big picture point of view it does not matter if you look at Windows, Mac, Linux, Android... Its all broken just in different ways. No party at this stage has the complete fix. The complete fix will take serous resources that libinput is missing and will require a profile device tool as in all that debuging tool crud of libinput presenting in a user friendly way.
you end up with this:
... it's regression.
Comment