Hi there, It seems that most of your problems are exactly what's been fixed in the CVS/GIT code repositories since release 0.4.8. The simplest solution for you is to uninstall the Ubuntu package, download the GIT repository, and compile. Roughly:
- go to http://sourceforge.net/p/xournal/code/ci/master/tree/ click on "download snapshot" in the gray bar at the top of the list of files (or run the "git clone" command shown if you have git). - make sure you have the development packages for gtk2, libgnomecanvas and poppler installed (add the packages in your package manager if needed) (in Fedora these are called gtk2-devel, libgnomecanvas-devel, poppler-glib-devel; not sure what they're called in Ubuntu). - in the xournal source code directory, run "./autogen.sh". See if there's error messages about missing libraries or packages, install them if needed. - run "make" Try going into the src directory and running ./xournal to see if things seem to work. - finally, as root, run "make install" and "make desktop-install" (xournal will then live in /usr/local/src/xournal, and might or might not need to be manually added to your launcher menus). You could also request from the Ubuntu package maintainer an update to the latest GIT code base because of these bugs. More in detail: > 1) I'd like to obtain a setup like the one one-note has, in which I > use the hand to move around (hand mode). So, I'm trying to use the > button `Designate as touchscreen`, for which I have a number of > options: > > - Virtual Core XTEST pointer > - Crucialtek co.,LTD Optical Track Pad > - N-Trig Duosense Pen > - N-Trig Duosense > - Core Pointer > > I tried to set `N-Trig Duosense` as the touchscreen, but then the > option `Touchscreen as Handtool` turns *both* the touch and the pen in > the handtool. I'd like the pen to remain usable to write. This is fixed in the CVS/GIT. Release 0.4.8 checked only whether the touch device name is a *substring* of the device that is drawing currently (so that the default choice "touch" would catch most touchscreens), but since "N-Trig Duosense" is a substring of "N-Trig Duosense Pen", the pen also gets caught. Because too many users were affected by this problem, we removed the behavior and now we need an exact match. So: once you install the latest version, select "N-Trig Duosense" and it should work. > 2) Button 3 mapping. I don't seem to be able to change the function of > my third button, which does always what the primary pen is > doing. Button 2 map works fine. Are there any ways in which I could > troubleshoot this? Do you mean the menu entries under Options just don't work, or do you mean that what you select for "Button 3 mapping" doesn't affect what your "third button" is doing? The latter is more logical, and would indicate that what you think of as your "third button" is not configured as button 3 for XInput. It's very crude, but run "xev" from a terminal, and click with your various buttons in the xev window but outside of the small rectangle. It should give things like: ButtonPress event, serial 36, synthetic NO, window 0x1600001, root 0xa1, subw 0x0, time 217099480, (114,126), root:(122,210), state 0x0, button 1, same_screen YES ButtonRelease event, serial 36, synthetic NO, window 0x1600001, root 0xa1, subw 0x0, time 217099576, (114,126), root:(122,210), state 0x100, button 1, same_screen YES Here "button 1", meaning the button I just pressed is configured as "button 1". There may or may not be configuration options for your device to configure the "third button" as a "button 3", look into the xinput options and commands. (E.g. start with "xinput --list-props (the device id)"). Or you might have a user-friendly configurator in your system config menus, but it might not have all the options. > 3) When I set pen pressure to on, the pen outputs a streak of pressure > when I'm about to lift my pen from the tablet (see the attached > pdf). This happens if I try to draw a very low pressured line, when I > lift the pen from the tablet, and when I handwrite (the end of the > letter display a sharp trait). Especially the second problem is a bit > unsettling. So, is there a way in which I could tweak the pen output > to avoid that? (I could always keep pen pressure off, but that's a > shame). This sounds identical to a bug that was fixed since release 0.4.8. Switching to the GIT/CVS version should also fix that. Hope this helps, Denis > > Thanks in advance > Carlo Nucera > > > > ------------------------------------------------------------------------------ > 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/ > > > > _______________________________________________ > Xournal-devel mailing list > Xournal-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xournal-devel > -- Denis Auroux UC Berkeley, Department of Mathematics aur...@math.berkeley.edu Institut Henri Poincare, Paris aur...@ihp.fr ------------------------------------------------------------------------------ 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/ _______________________________________________ Xournal-devel mailing list Xournal-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xournal-devel