#181 Xournal does not save touch screen device name with comma properly

[Saku Aura]

I have a Lenovo Yoga X1 with Ubuntu 16.10. Xinput lists the relevant touchscreen device as:
"Wacom Co.,Ltd. Pen and multitouch sensor Finger touch". If I save my preferences, it will be saved as "Wacom Co..Ltd. Pen and multitouch sensor Finger touch" (period instead of comma) and ignored on restarting Xournal.

Editing .xournal/config and putting the comma in works, but it will get overwritten on any saving of preferences with the improper string.

Xournal version 0.4.8, standard Ubuntu build.

[Denis Auroux]

This has been fixed in upstream (cvs/git repository). Recompiling from
cvs/git should fix the issue.

Or, in the meantime, you can work around the bug by taking advantage of
another mis-feature of the base 0.4.8 version: the touch device name is
matched as a substring rather than exact match. So: if you change the
entry in the config file manually to a unique substring such as "Finger
touch" (rather than the whole device name), then it should still work,
and shouldn't get corrupted when the config file is saved (as long as
you don't use the "Designate as touchscreen" dialog box to change the
touch device name).

Denis

[Saku Aura]

Thank you, the substring trick worked like a charm.

[Denis Auroux]

On 01/31/2017 01:54 PM, Saku Aura wrote:

Thank you, the substring trick worked like a charm.

Great! Just keep in mind, though, that the latest upstream version no
longer allows substrings and wants the exact device name (to avoid yet
another bug when the touch device name is a substring of another device
name) -- but no longer suffers from the bug where "," gets converted to "."

So at some point in the future, when Ubuntu's xournal package picks up
the changes in the upstream version, your touch device might not get
recognized correctly anymore and you'll need to change your config file
again to the full device name (or just use the dialog box).

Best,
Denis

[Denis Auroux]

Release 0.4.8.2016 is up to date with cvs/git repositories, and should include a fix for this bug. Please reopen if problems persist with 0.4.8.2016 or with the current cvs/git code.