digimend-users Mailing List for DIGImend (Page 9)
Brought to you by:
spb_nick
You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
From: Nikolai K. <sp...@gm...> - 2015-01-12 18:56:43
|
On 01/12/2015 08:43 PM, Thierry FOX wrote: > how do I do that? I'm not much of a linux geek. I'll try to explain, but I won't be able to go into much detail. To get "/sbin/modinfo hid-huion" output, open the terminal program, paste that command at the prompt and press enter. Copy and paste the output into the message. To get "/var/log/syslog", simply attach the "syslog" file from "/var/log" directory to the message. Nick On 01/12/2015 08:43 PM, Thierry FOX wrote: > how do I do that? I'm not much of a linux geek. > > On Mon, Jan 12, 2015 at 4:23 PM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > On 01/12/2015 06:07 PM, Thierry FOX wrote: > > no, it didnt, I may have not installed them properly, is there anyway to > verify its installation? > > > Yes. For a start, please send the contents of "/var/log/syslog" after you plug > in the tablet. And also the output of "/sbin/modinfo hid-huion". > > Thank you. > > Nick > > |
From: Thierry F. <thi...@gm...> - 2015-01-12 16:07:08
|
no, it didnt, I may have not installed them properly, is there anyway to verify its installation? On Sun, Jan 11, 2015 at 7:48 PM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Thierry, > > Please keep the maillist in the CC by replying using "Reply to All". This > way > others can benefit from our conversation. Thank you. > > > On 01/11/2015 09:44 PM, Thierry FOX wrote: > >> Hi, I installed the drivers now (I think) how do I access it to make it >> map >> my whole screen? I'm not good at understanding complicated things so try >> to >> make it simple. >> > > If the driver is being used, the tablet should cover the entire screen, > unless > you have some specific settings to do otherwise. Did the tablet behavior > change after you installed the driver? > > Nick > |
From: Nikolai K. <sp...@gm...> - 2015-01-11 19:48:51
|
Hi Thierry, Please keep the maillist in the CC by replying using "Reply to All". This way others can benefit from our conversation. Thank you. On 01/11/2015 09:44 PM, Thierry FOX wrote: > Hi, I installed the drivers now (I think) how do I access it to make it map > my whole screen? I'm not good at understanding complicated things so try to > make it simple. If the driver is being used, the tablet should cover the entire screen, unless you have some specific settings to do otherwise. Did the tablet behavior change after you installed the driver? Nick |
From: Nikolai K. <sp...@gm...> - 2015-01-10 21:54:38
|
Hi Thierry, On 01/10/2015 11:25 PM, Thierry FOX wrote: > I tried to install the drivers and I got two errors, I will show the error > but before I do can I ask if the driver helps to map the tablet properly, > because I'm going to try use the huion drivers for my huion 540 (and the > drivers are for ones like the huion 580) and I'm hoping it has some way to > map it properly instead of the tablet not covering the whole screen. If the driver works, then you'll be able to use the whole area. If not, we'll try to fix that. > code - > > thierry@thierry-Presario-CQ62-Notebook-PC:~/Desktop/digimend-kernel-drivers-5$ make install > make -C /lib/modules/3.13.0-32-generic/build SUBDIRS=/home/thierry/Desktop/digimend-kernel-drivers-5 modules_install > make[1]: Entering directory `/usr/src/linux-headers-3.13.0-32-generic' > mkdir: cannot create directory ‘/lib/modules/3.13.0-32-generic/extra’: Permission denied > make[1]: *** [_emodinst_] Error 1 > make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic' > make: *** [modules_install] Error 2 This happens because make doesn't have enough permissions to install the driver. Run "make install" under the root account. Like this: sudo make install Nick |
From: Thierry F. <thi...@gm...> - 2015-01-10 21:26:01
|
I tried to install the drivers and I got two errors, I will show the error but before I do can I ask if the driver helps to map the tablet properly, because I'm going to try use the huion drivers for my huion 540 (and the drivers are for ones like the huion 580) and I'm hoping it has some way to map it properly instead of the tablet not covering the whole screen. code - thierry@thierry-Presario-CQ62-Notebook-PC:~/Desktop/digimend-kernel-drivers-5$ make make -C /lib/modules/3.13.0-32-generic/build SUBDIRS=/home/thierry/Desktop/digimend-kernel-drivers-5 modules make[1]: Entering directory `/usr/src/linux-headers-3.13.0-32-generic' CC [M] /home/thierry/Desktop/digimend-kernel-drivers-5/hid-huion.o Building modules, stage 2. MODPOST 1 modules CC /home/thierry/Desktop/digimend-kernel-drivers-5/hid-huion.mod.o LD [M] /home/thierry/Desktop/digimend-kernel-drivers-5/hid-huion.ko make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic' thierry@thierry-Presario-CQ62-Notebook-PC:~/Desktop/digimend-kernel-drivers-5$ make install make -C /lib/modules/3.13.0-32-generic/build SUBDIRS=/home/thierry/Desktop/digimend-kernel-drivers-5 modules_install make[1]: Entering directory `/usr/src/linux-headers-3.13.0-32-generic' mkdir: cannot create directory ‘/lib/modules/3.13.0-32-generic/extra’: Permission denied make[1]: *** [_emodinst_] Error 1 make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic' make: *** [modules_install] Error 2 Thanks in advance |
From: Nikolai K. <sp...@gm...> - 2015-01-08 22:23:27
|
Hi Dan, On 01/08/2015 11:51 PM, Dan Roberts wrote: > I don't really understand this behavior, I didn't think Gtk+ (well, Gdk) did > much more than wrap X11/XInput into a common interface. Is it possible this > is actually due to GIMP inconsistencies that coincidentally didn't work on > Gnome but worked on Xfce? Because the current driver exposes multiple > pointer interfaces (at least for the Huion driver), I've found GIMP doesn't > always select the correct one, and doesn't appear to accept input (but since > Gimp still receives input from the master virtual pointer, it will still > receive generic pointer input, so you get motion and button presses, but no > pressure). I hacked my driver to ignore one of the interfaces, so > xf86-input-evdev never sees it, and in turn Gimp doesn't see it. It could be that. The GIMP was very quirky in that regard. I can only suggest trying an experimental version of the driver, which has pen and frame buttons together on the same, single interface: https://github.com/DIGImend/digimend-kernel-drivers/archive/huion-abstract-keyboard.zip Nick On 01/08/2015 11:51 PM, Dan Roberts wrote: > Nick, > I don't really understand this behavior, I didn't think Gtk+ (well, Gdk) did much more than wrap X11/XInput into a common interface. Is it possible this is actually due to GIMP inconsistencies that coincidentally didn't work on Gnome but worked on Xfce? Because the current driver exposes multiple pointer interfaces (at least for the Huion driver), I've found GIMP doesn't always select the correct one, and doesn't appear to accept input (but since Gimp still receives input from the master virtual pointer, it will still receive generic pointer input, so you get motion and button presses, but no pressure). I hacked my driver to ignore one of the interfaces, so xf86-input-evdev never sees it, and in turn Gimp doesn't see it. > > Hi Marcus, > In GIMP if you go to Windows->Dockable Dialogs->Device Status Gimp will create a small window which is titled "Devices" (or it may immediately show up as a tab in another Gimp window). This window will show you the devices currently configured in Gimp. When you draw in Gimp, it will highlight which device is active. If my above theory is correct, I believe the "Core Pointer" device will remain highlighted, and your tablet device will never be highlighted. Do you mind trying that? If you are up to it, I'd also be interested to see if you can definitely correlate the problem to Gnome but not Xfce, I wonder if Gimp's inconsistency just coincidentally appeared that way at first. Trying multiple times in both DEs could show it one way or the other. > > > Cheers, > Dan > > On Thu, Jan 8, 2015 at 2:58 AM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: > > In XFCE some applications, like GIMP, don't work with pressure sensivity(I > > did the same adjustments). In Gnome, the same application works very well. > > In some applications this feature is working in both XFCE and Gnome, e. g.: > > Krita. > > I guess Krita works because it doesn't use GTK. I would say this issue should > be reported to distribution maintainers. > > Nick > > > And I'd like to know if Is there some way to set the tablet shortcut buttons > > and adjust the tablet active area? > > > > Thanks in advance, Marcus. > > > > > Date: Wed, 7 Jan 2015 11:10:55 +0200 > > > From:sp...@gm... <mailto:sp...@gm...> > > > To:mvr...@ho... <mailto:mvr...@ho...>; dig...@li... <mailto:dig...@li...> > > > Subject: Re: [DIGImend-users] (no subject) > > > > > > Hello Marcus, > > > > > > On 01/07/2015 03:09 AM, Marcus Vinicius R wrote: > > > > Hello. I have a Huion H610 pro and I was trying to make it works on Fedora > > > > 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but that's a > > > > very important information: The driver doesn't work well on Xfce+Fedora! In > > > > Gnome it worked very well, pressure sensivity works in all applications > > > > tough I'm still trying to put the tablet shortcuts to do their job. > > > > > > If it works in Gnome, it should work in XFCE as well. > > > How exactly it doesn't work? > > > > > > Nick > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > DIGImend-users mailing list > DIG...@li... <mailto:DIG...@li...> > https://lists.sourceforge.net/lists/listinfo/digimend-users > > |
From: Dan R. <ade...@gm...> - 2015-01-08 21:51:09
|
Nick, I don't really understand this behavior, I didn't think Gtk+ (well, Gdk) did much more than wrap X11/XInput into a common interface. Is it possible this is actually due to GIMP inconsistencies that coincidentally didn't work on Gnome but worked on Xfce? Because the current driver exposes multiple pointer interfaces (at least for the Huion driver), I've found GIMP doesn't always select the correct one, and doesn't appear to accept input (but since Gimp still receives input from the master virtual pointer, it will still receive generic pointer input, so you get motion and button presses, but no pressure). I hacked my driver to ignore one of the interfaces, so xf86-input-evdev never sees it, and in turn Gimp doesn't see it. Hi Marcus, In GIMP if you go to Windows->Dockable Dialogs->Device Status Gimp will create a small window which is titled "Devices" (or it may immediately show up as a tab in another Gimp window). This window will show you the devices currently configured in Gimp. When you draw in Gimp, it will highlight which device is active. If my above theory is correct, I believe the "Core Pointer" device will remain highlighted, and your tablet device will never be highlighted. Do you mind trying that? If you are up to it, I'd also be interested to see if you can definitely correlate the problem to Gnome but not Xfce, I wonder if Gimp's inconsistency just coincidentally appeared that way at first. Trying multiple times in both DEs could show it one way or the other. Cheers, Dan On Thu, Jan 8, 2015 at 2:58 AM, Nikolai Kondrashov <sp...@gm...> wrote: > On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: > > In XFCE some applications, like GIMP, don't work with pressure > sensivity(I > > did the same adjustments). In Gnome, the same application works very > well. > > In some applications this feature is working in both XFCE and Gnome, e. > g.: > > Krita. > > I guess Krita works because it doesn't use GTK. I would say this issue > should > be reported to distribution maintainers. > > Nick > > > And I'd like to know if Is there some way to set the tablet shortcut > buttons > > and adjust the tablet active area? > > > > Thanks in advance, Marcus. > > > > > Date: Wed, 7 Jan 2015 11:10:55 +0200 > > > From: sp...@gm... > > > To: mvr...@ho...; dig...@li... > > > Subject: Re: [DIGImend-users] (no subject) > > > > > > Hello Marcus, > > > > > > On 01/07/2015 03:09 AM, Marcus Vinicius R wrote: > > > > Hello. I have a Huion H610 pro and I was trying to make it works on > Fedora > > > > 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but > that's a > > > > very important information: The driver doesn't work well on > Xfce+Fedora! In > > > > Gnome it worked very well, pressure sensivity works in all > applications > > > > tough I'm still trying to put the tablet shortcuts to do their job. > > > > > > If it works in Gnome, it should work in XFCE as well. > > > How exactly it doesn't work? > > > > > > Nick > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > DIGImend-users mailing list > DIG...@li... > https://lists.sourceforge.net/lists/listinfo/digimend-users > |
From: Nikolai K. <sp...@gm...> - 2015-01-08 14:22:15
|
On 01/08/2015 03:50 PM, Christopher Barry wrote: > On Thu, 08 Jan 2015 13:00:35 +0200 > Nikolai Kondrashov <sp...@gm...> wrote: > >> On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: >>> And I'd like to know if Is there some way to set the tablet shortcut >>> buttons and adjust the tablet active area? >> >> By shortcut buttons do you mean physical buttons, or button pictures >> on the tablet surface? The active area is relatively easily adjustable. >> >> See http://localhost:4000/support/howto/drivers/evdev/#calibration >> >> Nick > > > pretty sure that link will be invalid everywhere except maybe your > house... :) Argh! Here's the correct link: http://digimend.github.io/support/howto/drivers/evdev/#calibration Sorry. Nick |
From: Christopher B. <chr...@gm...> - 2015-01-08 13:52:19
|
On Thu, 08 Jan 2015 13:00:35 +0200 Nikolai Kondrashov <sp...@gm...> wrote: >On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: >> And I'd like to know if Is there some way to set the tablet shortcut >> buttons and adjust the tablet active area? > >By shortcut buttons do you mean physical buttons, or button pictures >on the tablet surface? The active area is relatively easily adjustable. > >See http://localhost:4000/support/howto/drivers/evdev/#calibration > >Nick pretty sure that link will be invalid everywhere except maybe your house... :) -- -C |
From: Nikolai K. <sp...@gm...> - 2015-01-08 11:00:47
|
On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: > And I'd like to know if Is there some way to set the tablet shortcut buttons > and adjust the tablet active area? By shortcut buttons do you mean physical buttons, or button pictures on the tablet surface? The active area is relatively easily adjustable. See http://localhost:4000/support/howto/drivers/evdev/#calibration Nick |
From: Nikolai K. <sp...@gm...> - 2015-01-08 10:59:05
|
On 01/08/2015 05:07 AM, Marcus Vinicius R wrote: > In XFCE some applications, like GIMP, don't work with pressure sensivity(I > did the same adjustments). In Gnome, the same application works very well. > In some applications this feature is working in both XFCE and Gnome, e. g.: > Krita. I guess Krita works because it doesn't use GTK. I would say this issue should be reported to distribution maintainers. Nick > And I'd like to know if Is there some way to set the tablet shortcut buttons > and adjust the tablet active area? > > Thanks in advance, Marcus. > > > Date: Wed, 7 Jan 2015 11:10:55 +0200 > > From: sp...@gm... > > To: mvr...@ho...; dig...@li... > > Subject: Re: [DIGImend-users] (no subject) > > > > Hello Marcus, > > > > On 01/07/2015 03:09 AM, Marcus Vinicius R wrote: > > > Hello. I have a Huion H610 pro and I was trying to make it works on Fedora > > > 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but that's a > > > very important information: The driver doesn't work well on Xfce+Fedora! In > > > Gnome it worked very well, pressure sensivity works in all applications > > > tough I'm still trying to put the tablet shortcuts to do their job. > > > > If it works in Gnome, it should work in XFCE as well. > > How exactly it doesn't work? > > > > Nick |
From: Marcus V. R <mvr...@ho...> - 2015-01-08 03:07:08
|
In XFCE some applications, like GIMP, don't work with pressure sensivity(I did the same adjustments). In Gnome, the same application works very well. In some applications this feature is working in both XFCE and Gnome, e. g.: Krita. And I'd like to know if Is there some way to set the tablet shortcut buttons and adjust the tablet active area? Thanks in advance, Marcus. > Date: Wed, 7 Jan 2015 11:10:55 +0200 > From: sp...@gm... > To: mvr...@ho...; dig...@li... > Subject: Re: [DIGImend-users] (no subject) > > Hello Marcus, > > On 01/07/2015 03:09 AM, Marcus Vinicius R wrote: > > Hello. I have a Huion H610 pro and I was trying to make it works on Fedora > > 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but that's a > > very important information: The driver doesn't work well on Xfce+Fedora! In > > Gnome it worked very well, pressure sensivity works in all applications > > tough I'm still trying to put the tablet shortcuts to do their job. > > If it works in Gnome, it should work in XFCE as well. > How exactly it doesn't work? > > Nick |
From: Nikolai K. <sp...@gm...> - 2015-01-07 09:11:04
|
Hello Marcus, On 01/07/2015 03:09 AM, Marcus Vinicius R wrote: > Hello. I have a Huion H610 pro and I was trying to make it works on Fedora > 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but that's a > very important information: The driver doesn't work well on Xfce+Fedora! In > Gnome it worked very well, pressure sensivity works in all applications > tough I'm still trying to put the tablet shortcuts to do their job. If it works in Gnome, it should work in XFCE as well. How exactly it doesn't work? Nick |
From: Marcus V. R <mvr...@ho...> - 2015-01-07 01:09:34
|
Hello. I have a Huion H610 pro and I was trying to make it works on Fedora 20, linux kernel 3.18.1 and xfce 4. I didn't find it anywhere but that's a very important information: The driver doesn't work well on Xfce+Fedora! In Gnome it worked very well, pressure sensivity works in all applications tough I'm still trying to put the tablet shortcuts to do their job. |
From: Nikolai K. <sp...@gm...> - 2015-01-03 20:03:21
|
Hi Christopher, Please keep the maillist in the CC, so others can benefit from our discussion as well. On 01/03/2015 09:56 PM, Christopher Hanna wrote: > On 01/03/2015 07:01 AM, Nikolai Kondrashov wrote: >> Hi Christopher, >> >> On 01/03/2015 08:35 AM, Christopher Hanna wrote: >>> Hello there, I recently got the tablet listed in the subject line, and >>> out of the box the pen was able to click things and the buttons worked >>> (both on the pen and the tablet), but it can't move the cursor. It was >>> also able to make a dot in any drawing program. I tried to fix it using >>> the wizardpen solution, but it didn't change anything, however the >>> wizardpen calibration program recognized the tablet area and gave a >>> reasonable output. Can you help me get it to work in some way? Will it >>> ever be supported in the near future? >> >> There is a development version of digimend-kernel-drivers which adds support >> for your tablet: >> >> https://github.com/DIGImend/digimend-kernel-drivers/archive/twha60.zip >> >> Could you please try it? >> >> The support for your tablet is to be in the next version, released within the >> next two months, perhaps. >> > > The driver you sent me makes the cursor move as it should, and all the > functions it had before are retained! Thanks Nick! Doesn't seem to be any > pressure sensitivity though. It's not terribly important, but any tips on > getting that to work? You can verify if the X server gets any pressure information by using "xinput test" with your tablet and seeing if you get anything in the third valuator. Otherwise, try following some of our (a bit dated) HOWTOs: http://localhost:4000/support/ I would welcome any fixes or updates to them, BTW. Nick |
From: Nikolai K. <sp...@gm...> - 2015-01-03 17:26:24
|
On 01/03/2015 07:04 PM, Vince Herried wrote: > OK sorry to pester you with dumb question before digging. No problem, but it's generally better to try to find the answer by yourself first :) > I had tried setting the /etc/X11/xorg.conf.d > parm file to use wacom driver earlier and didn't realize it was working. > > I'm not much of a gimp user, but making headway. > Any clue what the icons for - pencil, +pencil and hand should be? These icons are geared towards Windows applications which don't necessarily have similar controls. Feel free to choose whatever shortcuts you would use yourself. That said, the pencil +/- probably mean brush size, or next/previous brush. > I made a stab at a shell tool to set the values for gimp to match the > icon printed on the buttons It looks reasonable. > # debug help > #set -x > > # The /etc/X11/xorg.conf.d/50-huion.conf needs to have > # driver(wacom) for this to work. > # if the driver is not recognized then "xsetwacom --list" returns nothing > > #find the device ID for "Huion PAD" > PAD= > > getPAD (){ > PAD=`xsetwacom --list | grep pad | awk '{print $5 }'` > } > > # get the PAD id # > getPAD You don't really need getPAD as a function just write this: PAD=`xsetwacom --list | grep pad | awk '{print $5 }'` > if [ X$"PAD" == X ] ; then > echo "No wacom pad defined" > exit 16 > fi > > # setup for gimp > xsetwacom set $PAD button 1 key ctrl z # undo > xsetwacom set $PAD button 2 key shift e # eraser > xsetwacom set $PAD button 3 key n # pencil > > # > # strange how the button number skips here > # This is likely due to some special meaning that is assigned to buttons 4-7 and/or xf86-input-evdev behavior. > xsetwacom set $PAD button 8 key shift = # zoom in > xsetwacom set $PAD button 9 key - # zoom out > xsetwacom set $PAD button 10 key # + pencil > xsetwacom set $PAD button 11 key # - pencil > xsetwacom set $PAD button 12 key # hand I would guess every user would like to have their own mappings. Additionally, they can change GIMP shortcut assignments and other applications would use different shortcuts. There's also the imwheel tool which can remap buttons to actions/shortcuts but it is quite old, doesn't seem to support buttons past #9 and I didn't manage to make it work. Nick |
From: Vince H. <Vi...@Pl...> - 2015-01-03 17:04:50
|
OK sorry to pester you with dumb question before digging. I had tried setting the /etc/X11/xorg.conf.d parm file to use wacom driver earlier and didn't realize it was working. I'm not much of a gimp user, but making headway. Any clue what the icons for - pencil, +pencil and hand should be? I made a stab at a shell tool to set the values for gimp to match the icon printed on the buttons # debug help #set -x # The /etc/X11/xorg.conf.d/50-huion.conf needs to have # driver(wacom) for this to work. # if the driver is not recognized then "xsetwacom --list" returns nothing #find the device ID for "Huion PAD" PAD= getPAD (){ PAD=`xsetwacom --list | grep pad | awk '{print $5 }'` } # get the PAD id # getPAD if [ X$"PAD" == X ] ; then echo "No wacom pad defined" exit 16 fi # setup for gimp xsetwacom set $PAD button 1 key ctrl z # undo xsetwacom set $PAD button 2 key shift e # eraser xsetwacom set $PAD button 3 key n # pencil # # strange how the button number skips here # xsetwacom set $PAD button 8 key shift = # zoom in xsetwacom set $PAD button 9 key - # zoom out xsetwacom set $PAD button 10 key # + pencil xsetwacom set $PAD button 11 key # - pencil xsetwacom set $PAD button 12 key # hand ## end ## |
From: Nikolai K. <sp...@gm...> - 2015-01-03 12:01:58
|
Hi Christopher, On 01/03/2015 08:35 AM, Christopher Hanna wrote: > Hello there, I recently got the tablet listed in the subject line, and > out of the box the pen was able to click things and the buttons worked > (both on the pen and the tablet), but it can't move the cursor. It was > also able to make a dot in any drawing program. I tried to fix it using > the wizardpen solution, but it didn't change anything, however the > wizardpen calibration program recognized the tablet area and gave a > reasonable output. Can you help me get it to work in some way? Will it > ever be supported in the near future? There is a development version of digimend-kernel-drivers which adds support for your tablet: https://github.com/DIGImend/digimend-kernel-drivers/archive/twha60.zip Could you please try it? The support for your tablet is to be in the next version, released within the next two months, perhaps. Nick |
From: Christopher H. <shi...@gm...> - 2015-01-03 06:35:31
|
Hello there, I recently got the tablet listed in the subject line, and out of the box the pen was able to click things and the buttons worked (both on the pen and the tablet), but it can't move the cursor. It was also able to make a dot in any drawing program. I tried to fix it using the wizardpen solution, but it didn't change anything, however the wizardpen calibration program recognized the tablet area and gave a reasonable output. Can you help me get it to work in some way? Will it ever be supported in the near future? |
From: Nikolai K. <sp...@gm...> - 2014-12-29 04:26:07
|
Hi everyone, I just finished moving the project website to http://digimend.github.io/. The old wiki is no more, replaced by redirects to the new website. Thanks to Dan Roberts for the help moving the Vocabulary! Please try the new website and report any problems you can find, either using the page "report button" (beside the page title), or by replying to this message. Any feedback is appreciated, thank you. Nick |
From: Vince H. <Vi...@Pl...> - 2014-12-14 18:43:39
|
I had told myself if the problem happened again I would try to document it and send it to the GIMP folks. Then along comes your kernel update. If it fixes it. I'm not sure I want to fight the battle. I see gimp now only sees a single interface and the pressure curve seems much better. Inkscape is happy also. Blender seems to work, but I'm not so comfortable with pressure sculpting with blender. --- Vince On Sun, Dec 14, 2014 at 12:19 PM, Nikolai Kondrashov <sp...@gm...> wrote: > On 12/14/2014 07:16 PM, Vince Herried wrote: >> >> I thought I had resolved the gimp settings. >> The other day I tried to use it and nothing would draw. >> The mouse and stylus both were not working to draw. > > > Well, this really has to be reported to GIMP or at least distro developers. > > Using the modified driver I just sent you a link to (which only uses one > evdev > device) might help, though. > > Nick > > > On 12/14/2014 07:16 PM, Vince Herried wrote: >> >> I thought I had resolved the gimp settings. >> The other day I tried to use it and nothing would draw. >> The mouse and stylus both were not working to draw. >> >> I tried: >> >> select none >> select all >> Nope. >> >> turn off dynamics >> nope. >> >> open a previously known editable file >> nope. >> >> Create a new file from template >> nope. >> >> >> >> >> Again I ended up deleting >> >> >> $HOME/.gimp-2.8//devicerc >> >> problem gone. >> >> >> >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> >> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> DIGImend-users mailing list >> DIG...@li... >> https://lists.sourceforge.net/lists/listinfo/digimend-users >> > |
From: Nikolai K. <sp...@gm...> - 2014-12-14 17:19:11
|
On 12/14/2014 07:16 PM, Vince Herried wrote: > I thought I had resolved the gimp settings. > The other day I tried to use it and nothing would draw. > The mouse and stylus both were not working to draw. Well, this really has to be reported to GIMP or at least distro developers. Using the modified driver I just sent you a link to (which only uses one evdev device) might help, though. Nick On 12/14/2014 07:16 PM, Vince Herried wrote: > I thought I had resolved the gimp settings. > The other day I tried to use it and nothing would draw. > The mouse and stylus both were not working to draw. > > I tried: > > select none > select all > Nope. > > turn off dynamics > nope. > > open a previously known editable file > nope. > > Create a new file from template > nope. > > > > > Again I ended up deleting > > > $HOME/.gimp-2.8//devicerc > > problem gone. > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > > > > _______________________________________________ > DIGImend-users mailing list > DIG...@li... > https://lists.sourceforge.net/lists/listinfo/digimend-users > |
From: Vince H. <Vi...@Pl...> - 2014-12-14 17:16:42
|
I thought I had resolved the gimp settings. The other day I tried to use it and nothing would draw. The mouse and stylus both were not working to draw. I tried: select none select all Nope. turn off dynamics nope. open a previously known editable file nope. Create a new file from template nope. Again I ended up deleting $HOME/.gimp-2.8//devicerc problem gone. |
From: Vince H. <Vi...@Pl...> - 2014-11-29 23:27:25
|
I'm brain dead. I seem to finally be making some progress and can see the tablet pressure in action. I poked around with my HUION tablet and the gimp settings. I've seen settings that were reported previously in this forum where the stylus just would not draw anything. I found myself deleting .gimp-2.8/devicerc several times. Then I finally thing I stumbled on inputdevice settings that actually use tablet x,y, and Z inputs. In the Axes window I don't know what the 1,2, and 3 refer to. With Pressure set to 1, or 2, it didn't work at all. With it set as above pressure (the z axis ) then worked. Recently I was watching a blender tutorial where they used tablet pressure and I could not get it to work there either. I switched over to windows and blender still did notrespond to pressure. with blender still running I opened gimp ( again this is on windows ) and thought pressure was working. Then switched back to blender and yes it started working. After setting this up you then have to look at the dynamics settings. I created my own dynamics profile so I could experiment with it. The dynamics profile relates the pressure with brush features such as opacity or size. In blender when pressure is enabled by clicking on the icon that looks like a finger to make it gray in my default theme. In the paint mode it gives you two circles. The inner one changes size with as you change your stylus pressure. ---------------- Vince |
From: Nikolai K. <sp...@gm...> - 2014-11-23 15:44:35
|
Also, Vince, could we please continue the discussion in dig...@li...? DIGImend-users is not really appropriate for this sort of discussion. Thank you. Nick On 11/23/2014 05:17 PM, Nikolai Kondrashov wrote: > On 11/16/2014 10:31 PM, Vince Herried wrote: >> to me I was not able to understand the output it generated except the output >> when I pressed buttons or moved the stylus. >> >> I found the following webpage that helped a lot >> http://eleccelerator.com/usbdescreqparser/ >> >> I copied and pasted the output from the dump(s) into this tool >> and it converted the output into readable reports. Well still cryptic :) > > I assume you mean "report descriptors". Thanks, I didn't know about that tool. > You could have used my hidrd-convert as well. > > To make sense of report descriptors you should read the Device Class > Definition for HID 1.11 (http://www.usb.org/developers/hidpage/HID1_11.pdf). > > Nick > > [1] https://github.com/DIGImend/hidrd |