Incorrect name of input device for Aiptek HyperPen 12000U

Bug #1030756 reported by Enderlen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Low
Unassigned

Bug Description

Unable to take advantage of pressure measurement from input device

In old versions of Inkscape device was correctly recognized, with also its name correctly appearing in the input device list (see screenshot).

In latest versions of inkscape this is not working at all anymore, also name of input device not appearing correctly (2 different items labelled with sinograms appear in the list).

Input device is Aiptek HyperPen 12000U

Revision history for this message
Enderlen (enderlen) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Please provide information about your OS/platform and the version of Inkscape you have currently installed (see inkscape menu 'Help > About Inkscape').

Very likely this report is about the known regression with the GTK+ stack used with Inkscape 0.48.2, and a duplicate of
Bug #845354 “Critical Wacom tablet glitches (0.48.2)”
<https://bugs.launchpad.net/inkscape/+bug/845354>

Upcoming bug-fix release 0.48.3.1 will use a newer version of the Gtk+ toolkit which no longer exposes these regressions for tablets under Windows as seen with Inkscape 0.48.2.

The bug-fix release Inkscape 0.48.3.1 hasn't been officially announced yet on inkscape.org - until then you can download the installer for Inkscape 0.48.3.1 directly from here:
<http://sourceforge.net/projects/inkscape/files/inkscape/>

Changed in inkscape:
status: New → Incomplete
tags: added: tablet win32
Revision history for this message
Enderlen (enderlen) wrote :

OS: Win7 SP1
Inkscape: 0.48.2 r9819

Revision history for this message
su_v (suv-lp) wrote :

> OS: Win7 SP1
> Inkscape: 0.48.2 r9819

Would you be willing to test pressure sensitivity with Inkscape 0.48.3.1?

With regard to the second issue (garbled device names), probably best to start with fresh default preferences, and reconfigure the extended input devices [1]:

Quit all running instances of Inkscape and rename (or backup) the current the preferences file [2] (it will be recreated with default settings the next time you launch Inkscape). You can restore the older version if needed, if the error persists with the latest stable version (0.48.3.1).

---
[1] see also <http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Paths-Creating.html#Paths-Calligraphy-Tablet> which describes both the old and new input devices dialog.

[2] The location of the preferences file ('preferences.xml') on Windows:
%APPDATA%\inkscape\preferences.xml

%APPDATA% on Windows 7 defaults to:
C:\Users\{username}\AppData\Roaming

Revision history for this message
Enderlen (enderlen) wrote :

Ok I will test that with 0.48.3.1 version when back from holidays

Revision history for this message
Enderlen (enderlen) wrote :
Revision history for this message
Enderlen (enderlen) wrote :

Fortunately pressure is recognised with 0.48.3.1 version of Inkscape contrary to Inkscape 0.48.2.

Device name still appearing with sort of sinograms characters (I have attached the screenshot that allow to compare with Inkscape 0.46 that was successfully displaying the device name).

su_v (suv-lp)
Changed in inkscape:
status: Incomplete → New
Revision history for this message
su_v (suv-lp) wrote :

Thanks for testing and providing feedback! The issue with pressure sensitivity with older versions of the Windows GTK+ stack is tracked in bug #845354 - let's use this report to track the issue with the incorrect device names listed in the new 'Input Devices' dialog.

summary: - Pressure not recognized with Aiptek HyperPen 12000U
+ Incorrect name of input device for Aiptek HyperPen 12000U
tags: added: regression
Revision history for this message
jazzynico (jazzynico) wrote :

Related or duplicate: Bug #403678 "Invalid characters in input device dialog"
<https://bugs.launchpad.net/inkscape/+bug/403678>

Changed in inkscape:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.