> I would like to include the configuration GUI into the standard gpm > package. Ho I am affraid this is definitely not "ready enough" to be included anywhere right now !! :-) that was just a hack to study the possibilities/problems to get a GUI for touchpad/mouse interactive config, I think this is currently for gpm developpers only. > > I think your idea in general is really good and you should stick to > > it. Peter said it would be nice to have your gui to configure more > > than only synps2, but AFAIK there is no need to configure other > > protocols currently. > > To clear out any misunderstandnings: I think it is greate to have a gui to > the synps2. But I can definitly see the benifit of being able to configure > other mice, like swithing buttons, changing resolution, change one button > to a toggle scrollbutton etc. So I objected to the code was (as a hack) in > the synaptics.c file, instead of placing it in the fd loop i gpm.c, and > then communicate to the choosen mouse. This is right, the more generic way to perform dynamic interface with the driver is to include it directly at the level of the main loop in gpm.c One solution could be to add one more function field into Gpm_Type, like "C_<mousename>()", which woudl in turn call the driver-level config function. Anyways, this solution will still require to include changes in synaptics.c in order to perform the actual tunning of the parameters at the driver level. This also involves major changes in the main sources, I may give it a try but i have been quite busy lately and I wont be able to take care of it right now. Laurent