Re: [Gimp-developer] workaround to bad pixmaps on solaris
On Sun, Jun 09, 2002 at 01:00:27PM +0200, Sven Neumann wrote: Hi, Philip Brown [EMAIL PROTECTED] writes: Just FYI: Xsun with XFree extensions is known to have a problem with certain video cards, which makes some gtk programs that use pixmaps, not display properly. ... I think this may be the GDK bug that Federice fixed some days ago: no, I dont think so. I was re-reminded of it today, so I'll email the workaround: compile gtk with --disable-shm, if and only if you see the bad pixmaps. since this is definitely not a GIMP problem, your report is slightly off-topic though. Please test such things with testgtk and if you can reproduce them, report them as GTK+ bug using Bugzilla. yes, its true it is not a gimp problem. But if people compile gimp and see wierd stuff, they'll wonder whats going on. So I think it is good to have this in the archive, and also to let you guys know in case anyone else bothers you about it :-) ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
On Fri, Jun 07, 2002 at 11:02:02PM -0700, Akkana wrote: I just wrote up a page listing the packages I installed to build various versions of the gimp on my Redhat and Debian machines (in addition to whatever I previously had installed). ... Fortunately the 1.3.7 tarball builds fine, so the CVS problem isn't a big problem for me. Phil, have you tried building a tarball rather than CVS? You might have an easier time of it. Thanks for checking and making the list. Actually, I used all tarballs. I did not use CVS for any of it. So now I have an executable built. It just doesnt work properly, and makes my regular mouse unusable :-/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Ah, durnit... I forgot which part of things I was building, and just cut-n-pasted. i thought I was building gimp at that point. sorry folks ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
On Sat, Jun 08, 2002 at 05:51:29PM +0200, Sven Neumann wrote: Hi, Philip Brown [EMAIL PROTECTED] writes: Thanks for checking and making the list. Actually, I used all tarballs. I did not use CVS for any of it. So now I have an executable built. It just doesnt work properly, and makes my regular mouse unusable :-/ I'm sure you've tried some simpler GTK+-2.0 applications first, like the test applications and demos that come with the GTK+-2.0 source? Hmm. well, this is interesting... I nuked everything, and did a complete rebuild today (as you might hve guessed :-) and... now it seems to work normally. So you have one confirmed it works with solaris 8 (x86) now, with a regular mouse. however, its a smidge worrying why it went nuts before. My computer blew up, and I reinstalled it. Which means there may be a specific patch level that causes problems. And related to that... there is a 'bug' with certain versions of Xsun, which means that gimp wont work correctly with it, yet other programs will. Just FYI: Xsun with XFree extensions is known to have a problem with certain video cards, which makes some gtk programs that use pixmaps, not display properly. This used to be a problem with mozilla. Oddly enough, mozilla works fine now on this box. But gimp.1.3.7 exhibits this problem. a precompiled binary of gimp1.2.1, linked agaist libgtk-1.2.so.0 = /opt/sfw/lib/libgtk-1.2.so.0 libgdk-1.2.so.0 = /opt/sfw/lib/libgdk-1.2.so.0 libgmodule-1.2.so.0 = /opt/sfw/lib/libgmodule-1.2.so.0 libglib-1.2.so.0 = /opt/sfw/lib/libglib-1.2.so.0 does not have this problem either. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
On Fri, Jun 07, 2002 at 02:21:39AM -0400, Carol Spears wrote: So far, I just see extra hassle, to what is already a big hassle tracking down umpteen different new packages if you're not running linux or something that has them already. you make the best arguement for yourself not delving into development. maybe you should take this to the user list. I'm trying to encourage the developers, to make it easy for future users. That should be the goal of good software development: to make it easier for users, rather than easier for the programmers. That is to say, making things easier for the programmers is great, as long as it doesnt come at the EXPENSE of the users. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
On Thu, Jun 06, 2002 at 11:08:36AM +0200, Sven Neumann wrote: Philip Brown [EMAIL PROTECTED] writes: Which is a really good reason to not do this sort of nonsense. Just use autoconfig like always, instead of this silly pkgconfig. It's too redhat, for a software tool that's supposed to be cross-UNIX compatible. you obviously didn't understand what pkg-config does since it does a completely different thing than autoconf and in no way intents to replace it. From the pkgconfig README: pkg-config is a script to make putting together all the build flags when compiling/linking a lot easier. Sounds a whole like like autoconf to me. Or at most, autoconf plus libtool. Which you guys already use. So pkg-config is redundant. To put the same thing another way: autoconf+libtool seemed to work fine for gimp1.2.3. So if it wasnt broke, why are you trying to 'fix' it? ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Another dependancy issue: In the INSTALL file, #5, you MAY want to install other third party... stuff, should be reworded to we EXPECT the following third-party libraries to be installed. may implies an optional thing, that configure will automatically figure out and work around. expect indicates that configure expects these things by default, and breaks if they are not installed. [like libgimpprint, in addition to all the other stuff like libpng. etc] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp1.3.7,solaris8, Xsun
So after adding the freetype2 lib,and others, i finally managed to get gimp to compile and link. But now there's a huge problem - it messes up my X server. I start it up, the new installation dialog comes up with [continue] [cancel] at the bottom... and it has screwed up my mouse. The mouse does not respond properly any more, even after I cancel out of the dialog using the keyboard. Note that this is on a *vanilla* solaris 8 system, not one with my xinput drivers. So this is a definate solaris compatibility problem, vs a tweaked system problem. I'd be happy to help work through the problem, and submit patches, etc. But I need a better idea of what to look at. I have no idea what the heck could be messing up the mouse like that. ___ 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
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] dependancies (used to be xinput)
On Wed, Jun 05, 2002 at 11:35:25PM +0200, Christian Rose wrote: ons 2002-06-05 klockan 23.28 skrev Philip Brown: seems that the latest version of pkgconfig is not compatible with the latest version of pango. Which is a really good reason to not do this sort of nonsense. Just use autoconfig like always, instead of this silly pkgconfig. It's too redhat, for a software tool that's supposed to be cross-UNIX compatible. Good conspiracy theory or troll, but the problem is that fontconfig has nothing to do with pkgconfig, so that puts your little offtopic rant at shame. Actually, fontconfig has nothing to do with the issues *I* had compiling (as far as I know). That was the original poster's problem. My problems hit because of 'pangoft2', which is required by gtk1.3.7, but is NOT INSTALLED by pango1.0.2, the latest version of pango. Here's a fuller list of all the issues I have compiling the various dependancies under solaris, for the curious: == glib2.0 fails with non-GNU make: ... Making all in docs Making all in reference Making all in glib make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/glib-2.0.3/docs/reference/glib GNU make is 'recommended', but not stated as required. The really stupid thing is, its a bogus dependancy. Doing gmake at that point, doesnt seem to actually compile anything extra. Similar problem with atk 1.0.2. however, GNU make is not mentioned at all, recommended or otherwise make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/atk-1.0.2/docs pango suffers from similar GNU-make-itis pkg-config when called from other libraries' configure scripts, keeps whining about 'sh: gnome-config: not found' eg: checking for libpng12... sh: gnome-config: not found gtk+-2.0.3 README claims that png, jpg, and tiff libraries are optional. However, in gtk+-2.0.3/gdk-pixbuf /usr/ccs/bin/ld -G -h libpixbufloader-png.so -o .libs/libpixbufloader-png.so io-png.lo -R/home/phil/build/gtk+-2.0.3/gdk-pixbuf/.libs -R/directio/lib -R/directio/lib -L/directio/lib -lpng -lz ./.libs/libgdk_pixbuf-2.0.so /directio/lib/libgmodule-2.0.so -ldl /directio/lib/libgobject-2.0.so /directio/lib/libglib-2.0.so -lm -lc ld: fatal: library -lpng: not found ld: fatal: File processing errors. No output written to .libs/libpixbufloader-png.so Similarly for -ljpeg, once I get over the png error. Similarly for -ltiff, once I get over the jpeg error. In gtk/stock-icons, failed to load ./stock_add_16.png: Failed to load image './stock_add_16.png': Fatal error in PNG image file: Incompatible libpng version in application and library *** Error code 1 [This was with libpng1.2; downgraded to 1.0.2, and reconfigured... ] Hit another GNU-make-ism in docs/reference/gdk-pixbuf Making all in gdk-pixbuf make: Fatal error: Don't know how to make target `all-local' Current working directory /home/phil/build/gtk+-2.0.3/docs/reference/gdk-pixbuf *** Error code 1 And finally, the killer, while trying to configure gimp 1.3.7: checking for GTK+ - version = 2.0.0... yes (version 2.0.3) checking for pangoft2 = 1.0.0... sh: gnome-config: not found sh: gnome-config: not found Package pangoft2 was not found in the pkg-config search path. Perhaps you should add the directory containing `pangoft2.pc' to the PKG_CONFIG_PATH environment variable No package 'pangoft2' found And before you say I should set my PKG_CONFIG_PATH... 'pangoft2' **was** **not** **installed** by pango1.0.2, even when I used gmake to compile and install, from scratch. $ find /usr/local -name 'pangoft*' -print returns nothing. ___ 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] dependancies (used to be xinput)
On Wed, Jun 05, 2002 at 04:05:18PM -0700, Philip Brown wrote: And finally, the killer, while trying to configure gimp 1.3.7: ... Package pangoft2 was not found in the pkg-config search path. ... $ find /usr/local -name 'pangoft*' -print returns nothing. BTW: I went back and did a configure ; gmake; gmake install for pango 1.0.0 that did not install pangoft2* anywhere either, although i certainly see pango-1.0.0/pango/pangoft2.h sitting in the source directories. same with pango-1.0.2/pango/pangoft2.h ___ 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
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
