Re: [Linuxwacom-devel] very enthusiastic about libwacom, but already made it to loop forever :)
about the path, I just found that there is pkg-config support so it
does not matter anyway - I just build with "gcc `pkg-config --cflags
--libs gobject-2.0 libwacom` test.c -o./test" now. Also, adding
g_type_init() at the beginning of test program made
libwacom_new_from_path work just like libwacom_new_from_usbid (giving
WERROR_UNKNOWN_MODEL for me) - so got some progress :) Just curious,
is the end user supposed to call this g_type_init(), or it got missing
from the source?
Anyway, now that I was able to get past this block, I allowed it to
fallback to generic, and tried doing some probes - it found stylus and
4 buttons even that it did not found the device type. I already see
how useful this will be in near future, when database will be more
complete.
On Sat, Dec 17, 2011 at 7:39 PM, Andrzej Giniewicz wrote:
> Hi,
>
> today I found libwacom 0.1 on sf.net page, it looks great and I
> already made an Arch Linux package so people can start using it in
> their projects. I also wanted to check if I will be able to find some
> details on my device using this lib (actually I made this as part of
> learning Python ctypes and calling functions from C libs, but that's
> another story :)) - anyway, I was unable to get device by path, is
> this already known thing? I did simple:
>
> #include "libwacom/libwacom.h"
>
> int main() {
> WacomError* error = libwacom_error_new();
> WacomDeviceDatabase* database = libwacom_database_new();
> WacomDevice* device = libwacom_new_from_path(database,
> "/dev/input/wacom", 0, error);
> return 0;
> }
>
> with device correctly created, connected and working (link made by
> udev, it is pointing to event7 which is stylus of my 0xD1 Bamboo
> Pen&Touch). I built it using "gcc -I /usr/include/libwacom-1.0 -lwacom
> test.c -o test" (btw, I believe the libwacom-1.0 could be removed from
> path, i.e. it would be easier to find if it was in
> /usr/include/libwacom/libwacom.h for example), anyway, it builds
> without issue, but when I run the simple thing that should return
> device or NULL on error, at least according to documentation, the app
> hangs forever with following output:
>
> (process:6319): GLib-GObject-CRITICAL **: gtype.c:2715: You forgot to
> call g_type_init()
>
> (process:6319): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
>
> (process:6319): GLib-GObject-CRITICAL **: g_object_new: assertion
> `G_TYPE_IS_OBJECT (object_type)' failed
>
> if this is new thing, I'd be happy in helping to track it down :)
>
> Cheers,
> Andrzej.
--
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] very enthusiastic about libwacom, but already made it to loop forever :)
Hi,
today I found libwacom 0.1 on sf.net page, it looks great and I
already made an Arch Linux package so people can start using it in
their projects. I also wanted to check if I will be able to find some
details on my device using this lib (actually I made this as part of
learning Python ctypes and calling functions from C libs, but that's
another story :)) - anyway, I was unable to get device by path, is
this already known thing? I did simple:
#include "libwacom/libwacom.h"
int main() {
WacomError* error = libwacom_error_new();
WacomDeviceDatabase* database = libwacom_database_new();
WacomDevice* device = libwacom_new_from_path(database,
"/dev/input/wacom", 0, error);
return 0;
}
with device correctly created, connected and working (link made by
udev, it is pointing to event7 which is stylus of my 0xD1 Bamboo
Pen&Touch). I built it using "gcc -I /usr/include/libwacom-1.0 -lwacom
test.c -o test" (btw, I believe the libwacom-1.0 could be removed from
path, i.e. it would be easier to find if it was in
/usr/include/libwacom/libwacom.h for example), anyway, it builds
without issue, but when I run the simple thing that should return
device or NULL on error, at least according to documentation, the app
hangs forever with following output:
(process:6319): GLib-GObject-CRITICAL **: gtype.c:2715: You forgot to
call g_type_init()
(process:6319): GLib-CRITICAL **: g_once_init_leave: assertion
`initialization_value != 0' failed
(process:6319): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed
if this is new thing, I'd be happy in helping to track it down :)
Cheers,
Andrzej.
--
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 0/4] xsetwacom: NVIDIA TwinView support for MapToOutput
Indeed, I must have been tired yesterday. I was doing autogen in git version of package but not in stable/patched release. It works now, thanks. Andrzej. On Mon, Jul 11, 2011 at 12:14 AM, Peter Hutterer wrote: > On Sun, Jul 10, 2011 at 03:47:32PM +0200, Andrzej Giniewicz wrote: >> Hi, >> >> are there some not so obvious dependencies for this patches (on top of >> 0.11.1)? I tried applying those 4 (versions from git) - they applied >> successfully (with some offsets), but during compilation I'm getting: >> >> make[2]: Wejście do katalogu >> `/home/giniu/arch/wacom/wacom-drivers/src/xf86-input-wacom-0.11.1/tools' >> CC xsetwacom.o >> CCLD xsetwacom >> xsetwacom.o: In function `set_output': >> xsetwacom.c:(.text+0x26d7): undefined reference to `XineramaQueryExtension' >> xsetwacom.c:(.text+0x2706): undefined reference to `XineramaQueryScreens' >> collect2: ld returned 1 exit status >> >> I looked at git log for configure and xsetwacom and didn't noticed >> anything wrong. it's on Arch current (64 bits), with latest nvidia >> driver and following versions of xinerama and nvidia related stuff: >> >> [giniu@raven3 tools]$ pacman -Qs xinerama >> local/libxinerama 1.1.1-1 >> X11 Xinerama extension library >> local/xineramaproto 1.2.1-1 >> X11 Xinerama extension wire protocol >> >> or maybe there is some library needed that is not checked / API >> incompatibilities? > > did you run autoreconf -ivf (or autogen.sh)? the configure.ac snippet in the > last patch adds a dependency on xinerama which should then be part of the > X11_LIBS. if you're just applying the patches from the tarball and you > didn't have --enable-maintainer-mode on the last configure run, it'll miss > those changes. > > Cheers, > Peter > > -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 0/4] xsetwacom: NVIDIA TwinView support for MapToOutput
Hi, are there some not so obvious dependencies for this patches (on top of 0.11.1)? I tried applying those 4 (versions from git) - they applied successfully (with some offsets), but during compilation I'm getting: make[2]: Wejście do katalogu `/home/giniu/arch/wacom/wacom-drivers/src/xf86-input-wacom-0.11.1/tools' CC xsetwacom.o CCLD xsetwacom xsetwacom.o: In function `set_output': xsetwacom.c:(.text+0x26d7): undefined reference to `XineramaQueryExtension' xsetwacom.c:(.text+0x2706): undefined reference to `XineramaQueryScreens' collect2: ld returned 1 exit status I looked at git log for configure and xsetwacom and didn't noticed anything wrong. it's on Arch current (64 bits), with latest nvidia driver and following versions of xinerama and nvidia related stuff: [giniu@raven3 tools]$ pacman -Qs xinerama local/libxinerama 1.1.1-1 X11 Xinerama extension library local/xineramaproto 1.2.1-1 X11 Xinerama extension wire protocol or maybe there is some library needed that is not checked / API incompatibilities? cheers, Andrzej. On Mon, Jun 20, 2011 at 6:01 AM, Peter Hutterer wrote: > > Subject says it all. I haven't actually tested this on account of not having > a server that has the transformation matrix _and_ uses the nvidia binary > driver but the matrix looks correct. Testing feedback would be appreciated. > > Cheers, > Peter > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH 1/2] Export the device node as property.
Hi,
with current git I'm getting error during build:
../src/wcmXCommand.c: In function 'InitWcmDeviceProperties':
../src/wcmXCommand.c:156:26: error: 'XI_PROP_DEVNODE' undeclared
(first use in this function)
../src/wcmXCommand.c:156:26: note: each undeclared identifier is
reported only once for each function it appears in
I guess it's related to this patch, or more exactly to this patch:
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=blobdiff;f=src/wcmXCommand.c;h=12ebe5da87f62939c73ed8231634b82d030282bb;hp=20e87af2d0e6e5778e0feabc32943f89f315c17e;hb=2e9972c4419cef47ac08528bbaf02846ae4fc915;hpb=8713d0c90b994b259f7c0430ac4726884c7e3d10
Probably XI_PROP_DEVNODE has been renamed to XI_PROP_DEVICE_NODE in
one place while left unmodified in place where it was used?
Cheers,
Andrzej.
On Fri, Jun 3, 2011 at 1:10 AM, Peter Hutterer wrote:
> On Thu, Jun 02, 2011 at 12:44:10PM +1000, Peter Hutterer wrote:
>> X doesn't provide a mapping between physical devices and X device IDs other
>> than what can be extrapolated from the device name.
>> Export the device node so clients that need e.g. sysfs or other information
>> from the kernel can map the devices.
>>
>> Signed-off-by: Peter Hutterer
>> ---
>
> I should note that I had a typo in the patch, the server's define is
> XI_PROP_DEVICE_NODE, not XI_PROP_DEVNODE. I fixed this up locally but it had
> no effect on its working otherwise since the _name_ of the property was
> identical. Even if we had ended up using two different defines, the only
> result would have been that the cpp gets a bit more exercise.
>
> Cheers,
> Peter
>
>> src/wcmXCommand.c | 15 ++-
>> 1 files changed, 14 insertions(+), 1 deletions(-)
>>
>> diff --git a/src/wcmXCommand.c b/src/wcmXCommand.c
>> index 20e87af..65854b0 100644
>> --- a/src/wcmXCommand.c
>> +++ b/src/wcmXCommand.c
>> @@ -26,6 +26,10 @@
>> #include
>> #include
>>
>> +#ifndef XI_PROP_DEVNODE
>> +#define XI_PROP_DEVNODE "Device Node"
>> +#endif
>> +
>> static void wcmBindToSerial(InputInfoPtr pInfo, unsigned int serial);
>>
>> /*
>> @@ -72,6 +76,7 @@ int wcmDevSwitchMode(ClientPtr client, DeviceIntPtr dev,
>> int mode)
>> return wcmDevSwitchModeCall(pInfo, mode);
>> }
>>
>> +Atom prop_devnode;
>> Atom prop_rotation;
>> Atom prop_tablet_area;
>> Atom prop_pressurecurve;
>> @@ -144,6 +149,12 @@ void InitWcmDeviceProperties(InputInfoPtr pInfo)
>>
>> DBG(10, priv, "\n");
>>
>> + prop_devnode = MakeAtom(XI_PROP_DEVNODE, strlen(XI_PROP_DEVNODE),
>> TRUE);
>> + XIChangeDeviceProperty(pInfo->dev, prop_devnode, XA_STRING, 8,
>> + PropModeReplace, strlen(common->device_path),
>> + common->device_path, FALSE);
>> + XISetDevicePropertyDeletable(pInfo->dev, prop_devnode, FALSE);
>> +
>> if (!IsPad(priv)) {
>> values[0] = priv->topX;
>> values[1] = priv->topY;
>> @@ -597,7 +608,9 @@ int wcmSetProperty(DeviceIntPtr dev, Atom property,
>> XIPropertyValuePtr prop,
>>
>> DBG(10, priv, "\n");
>>
>> - if (property == prop_tablet_area)
>> + if (property == prop_devnode)
>> + return BadValue; /* Read-only */
>> + else if (property == prop_tablet_area)
>> {
>> INT32 *values = (INT32*)prop->data;
>>
>> --
>> 1.7.5.1
>>
>
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Discover what all the cheering's about.
> Get your free trial download today.
> http://p.sf.net/sfu/quest-dev2dev2
> ___
> Linuxwacom-devel mailing list
> Linuxwacom-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
>
--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] input-wacom 0.11.0 - empty tar.bz2 on sf.net
On Tue, Apr 26, 2011 at 5:47 PM, Jason Gerecke wrote: > A new copy has just been uploaded to SF -- hopefully this one works better :) better, but still differently than older versions (36kb vs 465kb) :) Looks like autogen.sh wasn't issued? -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] input-wacom 0.11.0 - empty tar.bz2 on sf.net
not exactly zero size. When I go to: http://sourceforge.net/projects/linuxwacom/files/xf86-input-wacom/input-wacom/ it says it's 14 bytes (contains only header). Strange that it works for you... On Tue, Apr 26, 2011 at 2:27 AM, Chris Bagwell wrote: > Either it got fixed today or it wasn't really zero size. I just > downloaded it and viewed it. > > Chris > > On Mon, Apr 25, 2011 at 6:52 AM, Andrzej Giniewicz wrote: >> Hi, >> >> I noticed that new version of kernel driver have been released, wanted >> to package it, but noticed that source tarball uploaded on sourceforge >> is empty. Though I'd let you know :) >> >> Cheers, >> Andrzej. >> >> -- >> Fulfilling the Lean Software Promise >> Lean software platforms are now widely adopted and the benefits have been >> demonstrated beyond question. Learn why your peers are replacing JEE >> containers with lightweight application servers - and what you can gain >> from the move. http://p.sf.net/sfu/vmware-sfemails >> ___ >> Linuxwacom-devel mailing list >> Linuxwacom-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel >> > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] input-wacom 0.11.0 - empty tar.bz2 on sf.net
Hi, I noticed that new version of kernel driver have been released, wanted to package it, but noticed that source tarball uploaded on sourceforge is empty. Though I'd let you know :) Cheers, Andrzej. -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.2
On Fri, Apr 15, 2011 at 2:35 AM, Chris Bagwell wrote: > So in summary I think any double clicks are not considered regressions > and any cursor jumps may be unique to the patches not in git (or are > they? I've not been keeping up well this month). I will try this out again today evening on plain 0.10.99.2 and 0.10.11 to find out what exactly worked and now do not. Anyway I had feeling that before second finger taps were working slightly better. Andrzej. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.2
Hi, On Thu, Apr 14, 2011 at 5:12 PM, Jason Gerecke wrote: > I'm interested in knowing if you're seeing these behaviors with my RFC > gesture patch in place or not (and if so, whether you've remapped the > scroll direction). Its the only overt change to gesture code I can > remember off the top of my head, but wasn't included in the 0.10.99.2 > release. This is 0.10.99.2 + two patches, one from Chris to allow button 9 to work, second is from you, (well, actually bundle: the "1/2: Allow gestures to use action button maps" + "2/2: Fix cursor freeze after performing gesture - RFC"). I haven't tested it without them. And yes, the directions are reverted - I can't stand inverted scrolls, I just like them working like touchpad Andrzej. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.2
Some more tests done. First of all, I made tests for 2.6.38.2 and it seems to work just as well as on 2.6.37.5 which I had before. Anyway, when doing more tests I noticed few new odd things in gestures, things that as far as I remember worked better in 0.10.11 (better as in better than now, but not necessarily 100% correctly) so I believe this stuff can be labelled as regressions: First of all it's very very easy to generate multiple (usually 2 or 3) RMB events when tapping second finger. It happens almost every time for me. Is there some parameter to control it? LMB tapping works just well with my setup. (I'm doing simple tests with: "xev | grep Button"), maybe RMB events aren't respecting some parameters? Or maybe, after successful tap and RMB generated, it should wait another TapTime before accepting next event like that? Second thing is that when I align fingers correctly for scroll and start moving them, for some time (approx half, maybe quarter of second) the cursor moves and after that time, it starts to generate normal scroll events like it should. There is also one thing that was reported for earlier versions too, i.e. the jumps. Lets say I label fingers as A and B, If I put fingers on the tablet in order A then B I have to remove them in exactly reverse order, like B then A, or the cursor will jump by value that is I believe difference between place where finger A started gesture to on tablet where it is put now. Simple experiment: 1) Put finger A in top-right of tablet 2) Put finger B right to it 3) remove finger A from tablet 4) remove finger B from tablet (actually, no gesture or events have to be generated during this as far as I see) 5) put finger in bottom-left corner, you should observe very big absolute jump. The xev reports something like: MotionNotify event, serial 40, synthetic NO, window 0x181, root 0x15d, subw 0x0, time 1918061, (1654,22), root:(1654,43), state 0x0, is_hint 0, same_screen YES MotionNotify event, serial 40, synthetic NO, window 0x181, root 0x15d, subw 0x0, time 1919525, (1004,386), root:(1004,407), state 0x0, is_hint 0, same_screen YES MotionNotify event, serial 40, synthetic NO, window 0x181, root 0x15d, subw 0x0, time 1919561, (1004,386), root:(1004,407), state 0x0, is_hint 0, same_screen YES (those are 3 events, just before jump, the one generating jump and one after the jump. There are no other events in between) I will play with it more, but those are all odd things I found for now Cheers, Andrzej. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.2
On Fri, Apr 8, 2011 at 8:02 AM, Peter Hutterer wrote: > Just when you thought the first tarball has gotten cold, here is the second > snapshot for the upcoming 0.11 release, fresh out of the oven. > We're in bugfixing mode and no new features will be accepted. Please test > this and let us know about any bugs you experience. There are two known issues left from 0.10.99.1 which already have patches on list: - Button 9 does not work on Bamboo P&T - Buttons 4,5,6,7 generated by gestures are hardcoded and cannot be mapped (unless it's by design, but there is patch to enable it again like it worked before in 0.10.11) I found no new issues with this release. Updated Arch Linux package to 0.10.99.2+2 patches for above to see if people find more. Andrzej. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.1
I just applied Jasons patches and they work, to me it looks that after 4 patches the driver 0.10.99.1 regained functionality of 0.10.11 (at least from my point of view), yay! That's why I already uploaded the package with those into Arch and asked users of my package to find more regressions if they can :) Cheers, Andrzej. -- Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.1
> are you scrolling through gestures? afaict the scrolling code is hardcoded > to use 4/5 6/7 instead of the button mapping. yes, that was of course using gestures. It worked in 0.10.11 so I believe it was recent change to hardcode it? -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.1
On Sun, Apr 3, 2011 at 1:57 AM, Chris Bagwell wrote: > OK, found and emailed patches to fix those two issues. > > I know your much better then me at testing so if you get bored, please > apply those to 0.10.11 or git and see what else you find. I applied on top of 0.10.99.1 (I actually applied second one already with the line added by Ping in his reply). Now all 4 buttons on pad work, also pointer reacts to touch. For now I found that it's now impossible to revert the scroll directions like I did before. In both cases when I have: [giniu@raven3 ~]$ xsetwacom get "Wacom Bamboo 2FG 4x5 Finger touch" Button 4 button +4 [giniu@raven3 ~]$ xsetwacom get "Wacom Bamboo 2FG 4x5 Finger touch" Button 5 button +5 or [giniu@raven3 ~]$ xsetwacom get "Wacom Bamboo 2FG 4x5 Finger touch" Button 4 button +5 [giniu@raven3 ~]$ xsetwacom get "Wacom Bamboo 2FG 4x5 Finger touch" Button 5 button +4 when I scroll down touch generates button 4 and scroll up generates button 5. Ability to revert scrolls was removed on purpose or maybe the way to do it changed? Andrzej. -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [linuxwacom-announce] [ANNOUNCE] xf86-input-wacom 0.10.99.1
Hi, I just tested the 0.10.99.1 out using kernel 2.6.37.5+input-wacom-0.10.11 on Bamboo 2FG 4x5 (P&T). I noticed two regressions compared to 0.10.11, all on fresh setup without configuration changes: 1) Button 9 on finger pad no longer works for me - it doesn't generate any event in xev (other buttons 1, 3 and 8 works) 2) Even that I have gesture and touch set to "on", touchpad does not work at all (no tapping, moving, touching, etc - xev is silent for fingers) - was there any change to the touch features and something more needs to be enabled? Andrzej. -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] toggle scripts with notification version 2
It all depends on your desktop environment. My bindings on tablet side are like this: xsetwacom set "Wacom Bamboo 2FG 4x5 Finger pad" Button 3 "key rsuper t" xsetwacom set "Wacom Bamboo 2FG 4x5 Finger pad" Button 8 "8" xsetwacom set "Wacom Bamboo 2FG 4x5 Finger pad" Button 9 "3" xsetwacom set "Wacom Bamboo 2FG 4x5 Finger pad" Button 1 "1" (notice the numbers - 1,9,8,3 from bottom to top - not 1,2,3,4 - this is how the buttons are numbered on Bamboo with recent drivers, after mouse buttons events they generate by default). Then in my case - I use OpenBox - I just had to add: touchtoggle to openbox/rc.xml file. Each desktop environment/manager have it's own way to bind keys to commands, so you have to find proper way to do it on desktop manager side I believe. On Sun, Mar 6, 2011 at 11:08 AM, Pander wrote: > On 2011-03-03 00:24, Pander wrote: >> Hi all, >> >> Here is version 2 of my toggle scripts with notification. >> >> Now for the 100 virtual dollar question, how can I call then via my >> tablet with: >> - button 4 (or 8) >> - CTRL + button 4 (or 8) >> - ALT + button 4 (or 8) > > Who can help me out to start a shell script from button 4? > > Thanks, > > Pander > >> Regards, >> >> Pander >> >> >> >> -- >> Free Software Download: Index, Search& Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT data >> generated by your applications, servers and devices whether physical, virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> >> >> >> ___ >> Linuxwacom-devel mailing list >> Linuxwacom-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > > > -- > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > ___ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH] Make 1 finger tap work based on finger release.
Hi,
> Looks like you have tested this patch yourself. Can you report back here
> with your testing result and a "Tested-by" tag? I am willing to put
> "Acked-by" once I see "Tested-by".
well, indeed I tested it. About tagging, I'm not sure if this is what
you mean, but here goes a try. If this is done somehow else, would be
happy to do it differently, never tagged a thing here so I don't know
the rules yet :)
cheers,
Andrzej.
Tested-by: Andrzej Giniewicz
tested on kernel 2.6.37.1 with input-wacom 0.10.10_2 and
xf86-input-wacom 0.10.11, tapping with single now works.
> On Mon, Feb 21, 2011 at 12:49 PM, wrote:
>>
>> From: Chris Bagwell
>>
>> Previous behavior required a double-tap to get a single finger
>> tap to work and didn't always work for me. Its behavior was basically
>> tap-and-drag gesture instead of tap-to-click.
>>
>> Converted to standard touchpad behavior of single tap based on finger
>> release. This is arguely the more important gesture to users.
>>
>> Removed wcmTouchpadMode since it wasn't needed for simple tap-to-click
>> gesture. If tap-and-drag gets added back and needs a variable, it can
>> be added back with a name that has "drag" in it to understand its
>> intended usage.
>>
>> Signed-off-by: Chris Bagwell
>> ---
>> src/wcmCommon.c |3 --
>> src/wcmTouchFilter.c | 59
>> +
>> src/xf86WacomDefs.h |1 -
>> 3 files changed, 35 insertions(+), 28 deletions(-)
>>
>> diff --git a/src/wcmCommon.c b/src/wcmCommon.c
>> index 926fbc4..e469e15 100644
>> --- a/src/wcmCommon.c
>> +++ b/src/wcmCommon.c
>> @@ -1430,9 +1430,6 @@ void wcmSoftOutEvent(InputInfoPtr pInfo)
>>out.device_id = wcmGetPhyDeviceID(priv);
>>DBG(2, priv->common, "send a soft prox-out\n");
>>wcmSendEvents(pInfo, &out);
>> -
>> - if (out.device_type == TOUCH_ID)
>> - priv->common->wcmTouchpadMode = 0;
>> }
>>
>>
>>
>> /*
>> diff --git a/src/wcmTouchFilter.c b/src/wcmTouchFilter.c
>> index 793d649..093d91f 100644
>> --- a/src/wcmTouchFilter.c
>> +++ b/src/wcmTouchFilter.c
>> @@ -141,32 +141,45 @@ static void wcmFingerTapToClick(WacomDevicePtr priv)
>> }
>>
>>
>> -/* process single finger Relative mode events
>> - * if touch is not in an active gesture mode.
>> +/* A single finger tap is defined as 1 finger tap that lasts less than
>> + * wcmTapTime. It results in a left button press.
>> + *
>> + * Some work must be done to make sure two fingers were not touching
>> + * during this gesture. This is easy if first finger is released
>> + * first. To handle case of second finger released first, require
>> + * second finger to have been released before first finger ever touched.
>> + *
>> + * Function relies on ds[0/1].sample to be updated only when entering or
>> + * exiting proximity so no storage is needed when initial touch occurs.
>> */
>> -static void wcmFirstFingerClick(WacomCommonPtr common)
>> +static void wcmSingleFingerTap(WacomDevicePtr priv)
>> {
>> - static int tmpStamp = 0;
>> - WacomChannelPtr aChannel = common->wcmChannel;
>> - WacomDeviceState ds = aChannel->valid.states[0];
>> - WacomDeviceState dsLast = aChannel->valid.states[1];
>> - if (ds.proximity)
>> + WacomCommonPtr common = priv->common;
>> + WacomChannelPtr firstChannel = common->wcmChannel;
>> + WacomChannelPtr secondChannel = common->wcmChannel + 1;
>> + WacomDeviceState ds[2] = { firstChannel->valid.states[0],
>> + secondChannel->valid.states[0] };
>> + WacomDeviceState dsLast[2] = { firstChannel->valid.states[1],
>> + secondChannel->valid.states[1] };
>> +
>> + DBG(10, priv, "\n");
>> +
>> + if (!ds[0].proximity && dsLast[0].proximity && !ds[1].proximity)
>>{
>> - if (common->wcmTouchpadMode)
>> - /* continuing left button down */
>> - aChannel->valid.states[0].buttons |= 1;
>> - else if (!dsLast.proximity &&
>> - (abs(tmpStamp - ds.sample) <=
>> common->wcmGestureParameters.wcmTapTime))
>> + /* Single Tap must have lasted
Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
> As you said, the stylus buttons should be a different > problem. The button 2&3 of pen behaved different than in previous release. I.e. they worked only if the pen tip had pressure > 0, i.e. were not working when I was hovering the pen above the surface (and the light was red already), I had to press the tip to make them work. I later found out it was because I played with the "TabletPCButton" option. I believe it behaved how it should, so there is no case, sorry. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Retiring CVS
Good news, especially after later sf.net cvs troubles. Does it mean input-wacom is also moving to git, or just linuxwacom for now? On Thu, Feb 17, 2011 at 3:18 AM, Jason Gerecke wrote: > After consulting with Ping, the CVS repositories are going to be > retired. With SourceForge hinting at a possible end-of-life for CVS > service it seems like a good idea to take a preemptive step and > consolidate everything under Git. > > However, while preparing the pull the plug I've run into a small snag: > the legacy linuxwacom code is hosted in three repositories that all > disagree to some extent. The linuxwacom-dev and linuxwacom-prod > repositories on CVS are the most up-to-date as far as version tags go, > but have different histories and tags. The linuxwacom repository on > Git is slightly less up-to-date, but does have a few patches the > others don't -- including the complete removal of kernel code. > > Any thoughts on which version we want to use, or how we should merge > the code/commits/tags between them? > > Jason > > --- > Day xee-nee-svsh duu-'ushtlh-ts'it; > nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it. > Huu-chan xuu naa~-gha. > > -- > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > ___ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] bamboo p&t 0.10.11 regression. No one finger tap.
I believe there is one more regression, not sure if it's known thing. I cannot get one finger tap to generate Button 1 event. But if one finger is sitting on tablet, I can easily generate as many Button 3 presses as I want using second finger (sometimes - actually usually - it clicks twice, but it might be me not trained to use it yet). I believe it was working before, even double tap for selection/dragging. Or maybe the way to generate it changed? Cheers, Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
> OK, thats an important point. Let me think about that some. > > Can you also clarify which buttons work while fingers are off touch > pad? Stylus, pad, both? I started with fresh tablet config and found out that pen issue is orthogonal, I will identify it later. Let's assume we start from fresh setup: 1) touch is on by default. Everything works 2) if I used touch at least once and disable it, all 4 pad buttons stop working the exact moment when I disable it - they aren't even visible in xev (I have mapped the script to Super+T, I also tried to use "key rsuper t" to disable touch with button, if it's disabled using that button after touch was used the modifier isn't depressed, it stops working in the middle) 3) if I haven't used touch and disable it, buttons still work, but putting my finger on when it's disabled, makes the pad buttons stop working immediately. I haven't found any way to bring them back after they are gone other than restarting X. hope it helps, Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
> So check out the changes and see if that has something to do with it. nope, I adjusted my configuration already. Also, they work as long as I don't put my fingers on touch pad when it's off. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
> I'll see if I can reproduce it soon. In mean time, can you please > send command you use to disable touch. I do not normally do this. sure, here it goes: xsetwacom set "Wacom Bamboo 2FG 4x5 Finger touch" Touch "off" Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
actually, same goes for button 2 and 3 on pen, only pen tip works. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] bamboo p&t 0.10.11 regression. Pad keys stop sending events after Touch is used
Hi, I just installed 0.10.11 and noticed strange thing which is I believe regression (cause it worked on 0.10.10). If I use touch pad of my tablet when the Touch is set to off, buttons on Pad stops to send events. If I enable Touch and use it, then everything works OK. But it also stops to send events when I switch the Touch off after it was used on Touch on. I use just released xf86-input-wacom-0.10.11 and input-wacom-0.10.10_2. I'd be happy to provide more information to help getting rid of this (though now I feel mad at myself for not trying out git version yesterday when all fixes I depend on were merged in already :/ ) Cheers, Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] about ticket 3169815 (Cannot compile input-wacom on 2.6.37 (missing mt.h))
Hi, > input-wacom source is updated. Somehow I still can not tag and upload > the package (access timed out). You can get the source from sf.net by: > > cvs -d:pserver:anonym...@linuxwacom.cvs.sourceforge.net:/cvsroot//linuxwacom > co input-wacom > > Or I can email the tarball to you directly. Let me know if you need help. Nah, no need to. I use the package from my OS and I have it patched there already. I'm glad it will be fixed in next release, it will decrease number of patches needed on OS side. Actually from 10 patches we have there, only the xsetwacom fix for Super will have to remain after next release (just curious, would it be possible to still squeeze it into 0.10.11? I mean the issue fixed by Przemo on 4'th Jan: http://sourceforge.net/mailarchive/forum.php?thread_name=m3y6718oy1.fsf%40who-t.net&forum_name=linuxwacom-devel I know there are better solutions, but it would make it work) Cheers, Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] about ticket 3169815 (Cannot compile input-wacom on 2.6.37 (missing mt.h))
Hi, today I got information from sf.net that is was already closed ( https://sourceforge.net/tracker/?func=detail&atid=525124&aid=3169815&group_id=69596 ), because the file is present in http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=include/linux/input/mt.h;h=b3ac06a4435d1114fde8fad1bbd548874641915b;hb=d2478521afc20227658a10a8c5c2bf1a2aa615b3 but, isn't that current Linus branch? The file is missing from stable 2.6.37: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git;a=tree;f=include/linux/input;h=c17efad449c1d3fd1fbb78de75c6b966c7d6a77a;hb=HEAD and is missing from tarballs of 2.6.37 - and unmodified kernel package provided by Arch Linux too. Afaik, the file showed up in officially 2.6.38RC. I did not wanted to post new ticket about it and there is no reopen option, so I decided to post here. That's why patch I attached to ticket just changed the .37 to .38, because then it should be in stable. Or am I wrong? Cheers, Andrzej. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] using Super_L, correct keysym, bad keycode (off by 1)?
Hi, today I noticed one thing, I tried to set one of buttons to "key super t" - though when checking it in xev I found out, that the key being used instead of Super_L is: keycode 132 (keysym 0x0, NoSymbol) When I use the actual key on keyboard, it is reported as: keycode 133 (keysym 0xffeb, Super_L) I tried out xsetwacom with verbose option on, and got: ... Key map 65515 (132, 'Super_L') [press,release] ... Key map 116 (28, 't') [press,release] what is interesting, is that the keysyb is correct, but the keycode it got is off by one. Oh, and Super_R works: ... Key map 65516 (134, 'Super_R') [press,release] ... Key map 116 (28, 't') [press,release] and in xev I get same result with both button on tablet and key on keyboard: keycode 134 (keysym 0xffec, Super_R) Any idea how can this be debuged? I'd be happy to help. Thanks, Andrzej. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] new bamboo and 0.10.7, max pressure is cut?
patch fixes it - thanks :) Tomorrow will continue testing stuff out cheers, Andrzej. On Wed, Jul 7, 2010 at 11:44 PM, Andrzej Giniewicz wrote: > I will check it right away if it fixes it for me too > > On Wed, Jul 7, 2010 at 11:36 PM, Rumen Zarev wrote: >> On 07/07/2010 05:30 PM, Rumen Zarev wrote: >>> > The case is that when normally pen works, both stylus and eraser when >>> > pressed 100% report pressure 0 (in xidump for example). When I press >>> > it full, it jumps to 0 from around 2042, and when I slightly depress >>> > it goes to very high values again. All scale from 0 to 99% works, it >>> > only behaves like that for full pressure - I'd expect some thing >>> > related to scaling values from device accuracy to 2048 that occurred >>> > not so long ago? Anyway I wasn't looking into code yet, decided to >>> > find out if it's known thing or maybe something on my side. >>> >>> Hi, >>> >>> I believe this is fixed by the patch I submitted at >>> https://sourceforge.net/tracker/?func=detail&aid=3024929&group_id=69596&atid=525126 >>> . >>> >>> I wasn't sure what's the proper way to submit a patch, and my first >>> e-mail to linuxwacom-devel bounced (I hadn't subscribed). Hopefully this >>> one goes through. >>> >>> Rumen Zarev >> >> One more try. >> >> -- >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> ___ >> Linuxwacom-devel mailing list >> Linuxwacom-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel >> > -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] new bamboo and 0.10.7, max pressure is cut?
I will check it right away if it fixes it for me too On Wed, Jul 7, 2010 at 11:36 PM, Rumen Zarev wrote: > On 07/07/2010 05:30 PM, Rumen Zarev wrote: >> > The case is that when normally pen works, both stylus and eraser when >> > pressed 100% report pressure 0 (in xidump for example). When I press >> > it full, it jumps to 0 from around 2042, and when I slightly depress >> > it goes to very high values again. All scale from 0 to 99% works, it >> > only behaves like that for full pressure - I'd expect some thing >> > related to scaling values from device accuracy to 2048 that occurred >> > not so long ago? Anyway I wasn't looking into code yet, decided to >> > find out if it's known thing or maybe something on my side. >> >> Hi, >> >> I believe this is fixed by the patch I submitted at >> https://sourceforge.net/tracker/?func=detail&aid=3024929&group_id=69596&atid=525126 >> . >> >> I wasn't sure what's the proper way to submit a patch, and my first >> e-mail to linuxwacom-devel bounced (I hadn't subscribed). Hopefully this >> one goes through. >> >> Rumen Zarev > > One more try. > > -- > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ___ > Linuxwacom-devel mailing list > Linuxwacom-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel > -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] new bamboo and 0.10.7, max pressure is cut?
Hi, I finally finished semester and got time to update OS and test out wacom tablet - woohoo, esp I updated to new driver. Anyway I noticed one thing and wonder if what I noticed is a bug or misconfiguration. The case is that when normally pen works, both stylus and eraser when pressed 100% report pressure 0 (in xidump for example). When I press it full, it jumps to 0 from around 2042, and when I slightly depress it goes to very high values again. All scale from 0 to 99% works, it only behaves like that for full pressure - I'd expect some thing related to scaling values from device accuracy to 2048 that occurred not so long ago? Anyway I wasn't looking into code yet, decided to find out if it's known thing or maybe something on my side. My current setup is as follows: hardware: Bamboo Pen&Touch - CTH460 software: Arch current with linuxwacom-bamboo-cth-ctl package, that is kernel 2.6.34.1 x server 1.8.1.902 wacom.ko built from linuxwacom 0.8.8-4 xf86-input-wacom 0.10.7 rules file provided by OS: http://aur.archlinux.org/packages/linuxwacom-bamboo-cth-ctl/linuxwacom-bamboo-cth-ctl/10-wacom.rules I remember it working with my previous setup, that is linuxwacom 0.8.8-4 and xf86-input-wacom 0.10.6 - there full pressure reported 100%, don't remember exact value as wasn't looking at xidump back then as it was working (it was also kernel 2.6.33 and x server 1.7 - had big update cause of lots of tasks at uni). Do you need any more information to trigger what's up with it? I will happily provide all requested informations :) Cheers, Andrzej. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
linuxwacom-devel@lists.sourceforge.net
Hi, >>> Three finger tap for middle mouse button click is not on my schedule >>> (trust me, I've already been fully scheduled into somewhere next year >>> :). But, anything is possible with open source. Maybe you can submit >>> a patch for us. Contributions are always welcome. Also, I think if >>> we could add those 2 and 3 finger taps feature into X server, it would >>> benefit all Input device drivers, which is the way I would love to >>> see. But, someone has to have the time and interest to work on it. >> >> Everything is possible, as long as it's supported by hardware... so... >> do CTH460 read more than 2 fingers? > > Short answer - no. Only two fingers are supported by the hardware. > > Long answer: you could translate the second finger single tap into > right click (as we do now) and the second finger double tap as middle > click if middle click is an important feature to you. Does this make > a bit sense to you? > > All Wacom devices only support up to 2 fingers, as far as I know. sure thing, makes sense now - that's what I didn't knew. So when I get my hands on one I will look into it thanks for your time Andrzej. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
linuxwacom-devel@lists.sourceforge.net
Hi, > Three finger tap for middle mouse button click is not on my schedule > (trust me, I've already been fully scheduled into somewhere next year > :). But, anything is possible with open source. Maybe you can submit > a patch for us. Contributions are always welcome. Also, I think if > we could add those 2 and 3 finger taps feature into X server, it would > benefit all Input device drivers, which is the way I would love to > see. But, someone has to have the time and interest to work on it. Everything is possible, as long as it's supported by hardware... so... do CTH460 read more than 2 fingers? If yes I will be happy to work on something when I get the device - so maybe somewhere soon :), if not, I wouldn't be able to test it, as this family of tablets is most I will probably able to afford - so in that case it would be better done by someone else cheers, Andrzej. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
linuxwacom-devel@lists.sourceforge.net
Hi, I wonder if it's supported by device and planned for driver to have middle mouse button with for example 3 finger tap (like for example default in many synaptic multitouches, like those from Asus eee)? I've seen code in git for buttons 1,2,4,5,6,7 and didn't noticed anything for button 3 - though the truth is I didn't looked for too long. If 3 finger tap is not supported by device, is it possible to (by quickly tapping with one then two fingers) to emulate middle mouse button like on old mouses that don't have it? I would probably test and see, but unfortunately I don't have the device yet (aiming for CTH460) cheers, Andrzej. PS.: small off topic, but it's my first post on this list - always wanted to say, that you all are doing great work with linux driver, I wish all hardware had such complete and professional linux support like Wacom tablets does -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
