Re: [Gimp-developer] new xinput device: no movement when button down
Michael Natterer wrote: This is as good a point to ask as any; in following the latest incarnation of the crazy dep-chain I ran into a dead-end finding the mysterious 'fontconfig' (fontconfig is needed by pango is needed by gtk2 is needed by gimp). Anyone know where I can find such a thing? I thought that it sounded like it was probably part of pkgconfig (pkgconfig is needed by... etc) but it doesn't seem to be. Hi Adam, It's just the HEAD version of pango which requires fontconfig, you probably wanted to checkout the pango-1-0 branch. The branches are glib-2-0, pango-1-0, atk HEAD, gtk-2-0. Thanks! Got fontconfig now. The reason I was trying pango HEAD was that pango-1-0 does not compile for me. However, the same problem (below) occurs for me on HEAD too. D'oh. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\/usr/local/etc\ -DLIBDIR=\/usr/local/lib\ -DG_DISABLE_DEPRECATED -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/X11R6/include -I../.. -g -O2 -Wa ll -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -Wp,-MD,.deps/pango-ot-info.pp -c pa ngo-ot-info.c -fPIC -DPIC -o pango-ot-info.o In file included from /usr/local/include/glib-2.0/gobject/gboxed.h:26, from /usr/local/include/glib-2.0/glib-object.h:25, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/gtype.h:92: syntax error before `typedef' @@gtype.h:91:#if GLIB_SIZEOF_LONG == GLIB_SIZEOF_SIZE_T @@gtype.h:92:typedef gulong GType; /usr/local/include/glib-2.0/gobject/gtype.h:167: syntax error before `gchar' @@gtype.h:167:G_CONST_RETURN gchar* g_type_name (GType type); /usr/local/include/glib-2.0/gobject/gtype.h:335: syntax error before `gchar' /usr/local/include/glib-2.0/gobject/gtype.h:336: syntax error before `gchar' In file included from /usr/local/include/glib-2.0/glib-object.h:25, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/gboxed.h:28: parse error before `G_BEGIN_DECLS' /usr/local/include/glib-2.0/gobject/gboxed.h:36: syntax error before `typedef' In file included from /usr/local/include/glib-2.0/glib-object.h:26, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/genums.h:28: parse error before `G_BEGIN_DECLS' /usr/local/include/glib-2.0/gobject/genums.h:46: syntax error before `typedef' In file included from /usr/local/include/glib-2.0/gobject/gobject.h:27, from /usr/local/include/glib-2.0/glib-object.h:27, from pango-ot-private.h:27, [cut -- lots more like this] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, Adam D. Moss [EMAIL PROTECTED] writes: Thanks! Got fontconfig now. The reason I was trying pango HEAD was that pango-1-0 does not compile for me. However, the same problem (below) occurs for me on HEAD too. D'oh. You expect the HEAD branch to compile if you can't get the stable version to build??? gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\/usr/local/etc\ -DLIBDIR=\/usr/local/lib\ -DG_DISABLE_DEPRECATED -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/X11R6/include -I../.. -g -O2 -Wa ll -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -Wp,-MD,.deps/pango-ot-info.pp -c pa ngo-ot-info.c -fPIC -DPIC -o pango-ot-info.o In file included from /usr/local/include/glib-2.0/gobject/gboxed.h:26, from /usr/local/include/glib-2.0/glib-object.h:25, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/gtype.h:92: syntax error before `typedef' @@gtype.h:91:#if GLIB_SIZEOF_LONG == GLIB_SIZEOF_SIZE_T @@gtype.h:92:typedef gulong GType; looks like glibconfig.h hasn't been generated properly. Are you sure you didn't overlook and errors when configuring glib? Perhaps take a look at /usr/local/lib/glib-2.0/include/glibconfig.h. It should have lines that say something like this: #define GLIB_SIZEOF_VOID_P 4 #define GLIB_SIZEOF_LONG 4 #define GLIB_SIZEOF_SIZE_T 4 Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Adam D. Moss [EMAIL PROTECTED] writes: Philip Brown wrote: BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. I feel your pain. This is as good a point to ask as any; in following the latest incarnation of the crazy dep-chain I ran into a dead-end finding the mysterious 'fontconfig' (fontconfig is needed by pango is needed by gtk2 is needed by gimp). Anyone know where I can find such a thing? I thought that it sounded like it was probably part of pkgconfig (pkgconfig is needed by... etc) but it doesn't seem to be. Hi Adam, It's just the HEAD version of pango which requires fontconfig, you probably wanted to checkout the pango-1-0 branch. The branches are glib-2-0, pango-1-0, atk HEAD, gtk-2-0. ciao, --mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Philip Brown [EMAIL PROTECTED] writes: On Wed, Jun 05, 2002 at 09:19:07PM +0200, Michael Natterer wrote: .. I find it somewhat irritating, for example, that a button3 on my pen will bring up a menu, that I can do nothing with , with the pen. Not only can I do nothing with it: I have to grab the core mouse to get rid of it. Yes, i have the same effect. We could check if the device which sent button3 is the core pointer... Okay, glad to see someone else sees that problem is a problem :-) BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. With the similar effect that the required libraries dont build well on Solaris. To be explicit, I cannot build the required libraries for gimp 1.3.7 on Solaris, my development platform. What library exactly are you unable to build? We resolved some Solaris build issues the night before the 1.3.7 release on irc... ciao, --mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, Philip Brown [EMAIL PROTECTED] writes: BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. With the similar effect that the required libraries dont build well on Solaris. I don't think it is as worth as you describe it here. We have been very careful about choosing our dependencies. The only dependency that was added to GIMP-1.3 that wasn't part of GIMP-1.2 or hasn't been introduced by GTK+-2.0 is libart2. To be explicit, I cannot build the required libraries for gimp 1.3.7 on Solaris, my development platform. you should file bug-reports against the required packages then. Solaris is very special in lots of places and you can't expect free software developers to know and care about these little details by themselves. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, Adam D. Moss [EMAIL PROTECTED] writes: I feel your pain. This is as good a point to ask as any; in following the latest incarnation of the crazy dep-chain I ran into a dead-end finding the mysterious 'fontconfig' (fontconfig is needed by pango is needed by gtk2 is needed by gimp). Anyone know where I can find such a thing? I thought that it sounded like it was probably part of pkgconfig (pkgconfig is needed by... etc) but it doesn't seem to be. you shouldn't be using unstable development versions of glib, pango and gtk+. If you are using CVS, please make sure that you checkout the stable branches, glib-2-0, pango-1-0 and gtk-2-0. If you insist on working with the unstable versions, subscribe to gtk-devel-list where this stuff is being discussed in all details. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Philip Brown [EMAIL PROTECTED] writes: Well, I commented out the pointer_grab/ungrab in paint_core_button_press() and release() in app/paint_core.c (gimp 1.2.3) and that makes my tablet work. I literally only have a few minutes every other day to poke at this, so I dont really have a chance to fully examine the code, and find out what a proper patch is. Could someone who is more intimately familiar with gimp internals (and has a tablet :-) please look into this? I am guessing that all you have to do is take OUT the 'AlwaysCore' hack for the wacom tablet, and you will see the same problems. Hi, this seems related to http://bugzilla.gnome.org/show_bug.cgi?id=6901 Did you try to remove just the GDK_POINTER_MOTION_HINT_MASK? XInput drivers are known to send wrong motion hints so this may well be the reason for your problem. (Checking Perfect but slow Pointer Tracking in preferences does the same without patching the source, but will work only for the paint tools) ciao, --mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
On Wed, Jun 05, 2002 at 11:23:02AM +0200, Michael Natterer wrote: this seems related to http://bugzilla.gnome.org/show_bug.cgi?id=6901 Did you try to remove just the GDK_POINTER_MOTION_HINT_MASK? XInput drivers are known to send wrong motion hints so this may well be the reason for your problem. Hmm. I read the bugid, but it didnt really tell me what gimp is expecting in this case. Can you enlighten me? I didnt see anything about 'motion hint' in the xinput 'port' document. (Checking Perfect but slow Pointer Tracking in preferences does the same without patching the source, but will work only for the paint tools) It was already checked, under Interface-Image Windows. I unchecked it in a vanilla gimp1.2.3, with no difference. The grab still stops anything getting drawn except a single dot. Also - you seem to imply that it is possible to use a non-core xinput device for things other than plain drawing. I'd like to know how. I find it somewhat irritating, for example, that a button3 on my pen will bring up a menu, that I can do nothing with , with the pen. Not only can I do nothing with it: I have to grab the core mouse to get rid of it. It seems like there has been too much of an assumption that the user will run their xinput device with the 'AlwaysCore' hack. I think it should be quite possible to have a very usable interface,even when the pen is non-core. Making that menu traversable would be a great start. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hmmm. Another piece of wierdness : my commenting out the gdk_pointer_grab makes the airbrush, pencil, and paintbrush work. But NOT the 'ink' drawing tool. any ideas? ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Philip Brown [EMAIL PROTECTED] writes: On Wed, Jun 05, 2002 at 11:23:02AM +0200, Michael Natterer wrote: this seems related to http://bugzilla.gnome.org/show_bug.cgi?id=6901 Did you try to remove just the GDK_POINTER_MOTION_HINT_MASK? XInput drivers are known to send wrong motion hints so this may well be the reason for your problem. Hmm. I read the bugid, but it didnt really tell me what gimp is expecting in this case. Can you enlighten me? GIMP just expects that the motion events' is_hint boolean is set correctly. Motion hints are used to reduce the number of motion events X delivers. I didnt see anything about 'motion hint' in the xinput 'port' document. Which is probably the reason why at least the wacom driver sets them wrongly and thus breaks software which request hints. It should just choose to not send hints at all end everything would be fine (at least on the motion hint front :-) (Checking Perfect but slow Pointer Tracking in preferences does the same without patching the source, but will work only for the paint tools) It was already checked, under Interface-Image Windows. I unchecked it in a vanilla gimp1.2.3, with no difference. The grab still stops anything getting drawn except a single dot. Then, unfortunately, the bug you see seems not to be related to the hints. Also - you seem to imply that it is possible to use a non-core xinput device for things other than plain drawing. I'd like to know how. Nope, I just wanted to make clear that only the paint tools have the builtin possibility to switch hints on/off. Other tools like the rect_select tool don't have this. I find it somewhat irritating, for example, that a button3 on my pen will bring up a menu, that I can do nothing with , with the pen. Not only can I do nothing with it: I have to grab the core mouse to get rid of it. Yes, i have the same effect. We could check if the device which sent button3 is the core pointer... It seems like there has been too much of an assumption that the user will run their xinput device with the 'AlwaysCore' hack. There is no such assumption. I think it should be quite possible to have a very usable interface,even when the pen is non-core. Making that menu traversable would be a great start. I don't understand what you mean by this. BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( ciao, --mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
On Wed, Jun 05, 2002 at 09:19:07PM +0200, Michael Natterer wrote: .. I find it somewhat irritating, for example, that a button3 on my pen will bring up a menu, that I can do nothing with , with the pen. Not only can I do nothing with it: I have to grab the core mouse to get rid of it. Yes, i have the same effect. We could check if the device which sent button3 is the core pointer... Okay, glad to see someone else sees that problem is a problem :-) BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. With the similar effect that the required libraries dont build well on Solaris. To be explicit, I cannot build the required libraries for gimp 1.3.7 on Solaris, my development platform. [PS: I am on the list. No need to Cc me] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Philip Brown wrote: BTW, would you try gimp 1.3.7 (or CVS) and try if the problem still persists there? If they behave different we'd have a hint how to fix 1.2. If 1.3.7 has the effect too, we have a bug on both branches :( I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. I feel your pain. This is as good a point to ask as any; in following the latest incarnation of the crazy dep-chain I ran into a dead-end finding the mysterious 'fontconfig' (fontconfig is needed by pango is needed by gtk2 is needed by gimp). Anyone know where I can find such a thing? I thought that it sounded like it was probably part of pkgconfig (pkgconfig is needed by... etc) but it doesn't seem to be. Thanks, --Adam -- Adam D. Moss . ,,^^[EMAIL PROTECTED]http://www.foxbox.org/ co:3 zing thro===Even when I ch== skin is === === just bare don't = get puls== Still = unusua==fever ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
At 21:37 05.06.02 +0100, Adam D. Moss wrote: I already tried. I was very disappointed to see that you guys seem to be following in GNOME's footsteps, and suddenly requiring 3 times the amount of library dependancies. I feel your pain. This is as good a point to ask as any; in following the latest incarnation of the crazy dep-chain I ran into a dead-end finding the mysterious 'fontconfig' (fontconfig is needed by pango is needed by gtk2 is needed by gimp). Anyone know where I can find such a thing? I thought that it sounded like it was probably part of pkgconfig (pkgconfig is needed by... etc) but it doesn't seem to be. The info was on gtk-devel just a few days ago. I'm pasting it here while trying to no comment on cvs gtk/pango brokeness for other backends as X11 ... Hans At 11:44 04.06.02 -0400, Owen Taylor wrote: Pango HEAD now is using fontconfig and Xft2: Notes: * A 'fcpackage' source tarball containing both of these can be found at: http://keithp.com/fonts/ * Red Hat RPMS can be found at: http://people.redhat.com/otaylor/xft-rpms/ * If you aren't interested in bleeding-edge Pango developement, you should be using use the pango-1-0 branch of Pango. * Until we get a Win32 port of fontconfig, the pango-1-0 branch will also be needed on Windows. * The fontconfig library is now used for both the Xft and FT2 backends. mini-xft is gone. The font configuration file is found in /etc/fonts/fonts.conf Hans at Breuer dot Org --- Tell me what you need, and I'll tell you how to get along without it.-- Dilbert ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
On Wed, Jun 05, 2002 at 10:57:13PM +0200, Hans Breuer wrote: ... The info was on gtk-devel just a few days ago. I'm pasting it here while trying to no comment on cvs gtk/pango brokeness for other backends as X11 ... Hans At 11:44 04.06.02 -0400, Owen Taylor wrote: ... * If you aren't interested in bleeding-edge Pango developement, you should be using use the pango-1-0 branch of Pango. Unfortunately, that isnt very informative for people who are downloading tarfiles, rather than using CVS. :-( We need only use pango x.y.z tarball ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Well, I commented out the pointer_grab/ungrab in paint_core_button_press() and release() in app/paint_core.c (gimp 1.2.3) and that makes my tablet work. I literally only have a few minutes every other day to poke at this, so I dont really have a chance to fully examine the code, and find out what a proper patch is. Could someone who is more intimately familiar with gimp internals (and has a tablet :-) please look into this? I am guessing that all you have to do is take OUT the 'AlwaysCore' hack for the wacom tablet, and you will see the same problems. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, Philip Brown [EMAIL PROTECTED] writes: I'm writing a new xinput extension module. I'm implementing support for my device as a *NON-CORE* device. [...] Can anyone suggest what I need to do, to make gimp happy? I'm not following the gimp code very well. I'd try to make GTK+ happy in the first place. As a side-effect this should as well satisfy The GIMP. I wanted to use an alternate, 'pure X11' program like xink to do more direct testing... except I CANT FIND xink any more :-( kiwi.cs.berkeley.edu no longer exists what about using testinput as found in the GTK+ source in the tests directory ? Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
On Sun, Jun 02, 2002 at 02:53:57PM +0200, Sven Neumann wrote: Philip Brown [EMAIL PROTECTED] writes: I'm writing a new xinput extension module. I'm implementing support for my device as a *NON-CORE* device. [...] Can anyone suggest what I need to do, to make gimp happy? I'm not following the gimp code very well. I'd try to make GTK+ happy in the first place. As a side-effect this should as well satisfy The GIMP. I just tried gsumi, and IT is happy. which by definition means GTK+ is happy. So it seems to be entirely a GIMP issue. what about using testinput as found in the GTK+ source in the tests directory ? thanks for the pointer - i didnt notice that before. it is also happy and works fine with my tablet. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] new xinput device: no movement when button down
I'm writing a new xinput extension module. I'm implementing support for my device as a *NON-CORE* device. [This is for gtk compiled with --xinput=xfree ] I've got cursor movement working just fine. Plus, when I press on the pen, an appropriately dark splotch appears on the canvas. However... gimp wont allow for any movement while a pen button is down. I press down, and a mark is made. I move the pen, and nothing happens until I stop pressure. At which point, the cursor appears in the spot I have moved the pen to, with no interveaning trail. Debug output from my driver confirms that the driver is still sending MotionNotify events, while the button is down. Can anyone suggest what I need to do, to make gimp happy? I'm not following the gimp code very well. I wanted to use an alternate, 'pure X11' program like xink to do more direct testing... except I CANT FIND xink any more :-( kiwi.cs.berkeley.edu no longer exists ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
