Hi Peter, > ------------ Původní zpráva ------------ > Od: Peter Hutterer <[email protected]> > Předmět: Re: [Linuxwacom-devel] xsetwacom re-implementation available > Datum: 14.12.2009 07:13:20 > ---------------------------------------- > On Fri, Dec 11, 2009 at 09:53:04PM +0100, Oldrich Jedlicka wrote: > > Hi Peter, > > > > On Thursday 10 of December 2009 at 07:07:34, Peter Hutterer wrote: > > > As you may be aware, xf86-input-wacom utilises input device properties to > > > set a couple of driver-specific options at runtime. This is quite > > > different > > > to linuxwacom where run-time changing is performed via ChangeDeviceControl > > > requests. This difference in run-time parameter changes had the > > > side-effect > > > of a broken xsetwacom. > > > > > > I've just pushed the re-implementation of xsetwacom to the xsetwacom > > > branch > > > in my repository (it'd be a bit of a patchbomb sending all patches to the > > > list). > > > > > > It's not a 1:1 replacement yet but most commands are available and should > > > work as before. The user interface for most commands has stayed the same, > > > some commands (e.g. key mappings) have changed slightly or are available > > > in > > > multiple versions (e.g. GNU style parameters). > > > > > > I'll be merging this branch into master early next week. If you have the > > > time for testing already, feel free to give it a crack and complain to me > > > if your favourite command doesn't do what it used to do. > > > The code is fairly straightforward, so feel free to send patches to fix > > > whatever is broken. > > > > So I've heard you want somebody to complain :-) > > > > Actually the "key shift" doesn't work (the mouse button acts exactly as a > > shift key). > > can you give me some more info what exactly you're referring to here? you've > assigned the button to be "Shift"? is that correct?
Exactly. Assign a "Shift" key functionality to a button (button press=shift pressed,button release=shift released). I was using also the "Ctrl" key for another button. I think it would be sufficient to release all "forgetten" pressed keys automatically (in reversed order), when the button is released - that would sanitise the user's input too. > > I have also difficulties double-clicking Button 3, because it > > freezes any mouse/tablet clicks (no buttons react) until some key is > > pressed. > > just double-clicking the physical button or assigning doubleclick to it? Just double-click (Button 3) without any assigned functonality - just a pure button. I've tried it with tracing enabled, but I didn't see any difference from single click, only no mouse clicks accepted afterwards (also from normal mouse) - until the keyboard's key is pressed. I wanted to have a look at it during weekend, but I didn't have any free time for that... > Cheers, > Peter Cheers, Oldrich. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
