[Gimp-developer] GIMP 2.7 (git) crashes with Gtk error
system: openSUSE 11.2 / KDE 4.4 (KDE factory repos) i've recently started using GIMP 2.7 from git repositories and am experiencing reproducable crashes when recomposing images after splitting them into LAB channels first, then recomposing after applying selective unsharp mask on the luminescence channel. i have a separate install of GIMP 2.6.8, which does not crash during the same procedure. GIMP 2.7 crashes both in single window and 'normal' mode. the error message i receive on the command line is this: - Gtk:ERROR:gtkrbtree.c:1098:_gtk_rbtree_find_offset: assertion failed: (tree) .gimp/bin/gimp-2.7: terminated: Aborted (script-fu:15893): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error - i don't seem to find any similar bug reports and am wondering if i should file a bug, and if, against Script-Fu or libgimp? -- phani. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] PhotoBook Designer Plugin
Hi, I am pretty new to GIMP. Just want to know how big a task is it to develop a photobook designer extension. -- Vissu +919740083224 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] PF_FILE of the register function in python plugins with 'new file' support
Hi Imagine a python-fu plug-in with a GUI that is initialized through the register function. One of the elements is of the PF_FILE type to select a file. Unfortunately, the dialogue that pops up when entering a file only allows the selection of an existing file. But I want to select a new file. So there should be a text box either in the file dialogue or in the plug-in GUI that allows to enter any file name. The only workaround in the moment is a PF_STRING element. But this is really inconvenient because the whole path has to be entered. A graphical selection is much easier. Thanks in advance! Mathias My way around this was to use a PF_DIRNAME immediately above the PF_STRING and combining them for the total path. -- Scott (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] A big thank you
Yes I can, I would love it, any suggestion? You may have well some suggestions As example just explore the download section(s). Instead then a page with a ordered and clear list of options available for the different OS,each with the related link more a link for the source, you will find a quite confusing situation, on one hand a Downlaod for Windows thingy, that go on by redirecting from page to page,as in a race trough a labyrinth ...and with no apparent link back in case you chose for error the wrong OS On the other hand other generic Download pages where any indication of the existence of something as a Windows OS is missed..but are missed also also the most basic tips for Linux users as were get a build for your distro ( i know answer is simple, directly in your distro repository ..but since other sw do offer directly binary for the main distro , also different answers may well be expected ...) This is what a not expert as me may spot at the very contact with the side ( spot is here a euphemism most of the casual visitors just smash there...and then they give up and download gimp from some other side as www.download com,Majorgeeks,Filehippo and similar.. or revert to ask advices to their distro forums ) But since is your field you should be able to notice more area that may need improvements -- photocomix (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.8 schedule
Alexia Death wrote: In general, its wonderful. A few notes tho. The format. It does not really facilitate discussion and is a bit inconvenient to follow. Perhaps a wiki format, tho I assume calc was selected because of the eta math? Versioning is a good idea regardless. Next, It currently assumes there is only one person at work. Wouldn't it make more sense to track estimated time of completion as provided by people working on a feature, or yes, a time estimate for no caretaker or hard to assess items? If something has no caretaker an no estimate of completion its likely to be left out. Lastly, items on this list could use some numbered markings so one could add a comment with a reference, say this depends on item X, cant be started before its done etc. Hi Kaja, Yes, I used OO.org Calc because there are calculations that needs to be made. It would be nice to have it more accessible but I think we can live with it when I've added it to ./devel-docs. The scheme does not assume there is only one person at work, the current factor 3 days worked per week is what I estimate that the GIMP community currently produces together. And IMHO, adding numbers to allow references and dependencies would create more complexity than we currently need. / Martin ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] A big thank you
Yes I can, I would love it, any suggestion? I would like a user driven gimp.org. With our current static web page only the ones with commit access can improve the web page. With more wiki-like site we could have a website that is alive. There are of course benefits of having a static site such as less load on the web server, but from what I understand we have the money to maintain a website that has the potential to become popular in the Web 2.0 sense. / Martin -- My GIMP Blog: http://www.chromecode.com/ Best way to keep up with GIMP from git ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.7 (git) crashes with Gtk error
phanisvara das wrote: - Gtk:ERROR:gtkrbtree.c:1098:_gtk_rbtree_find_offset: assertion failed: (tree) .gimp/bin/gimp-2.7: terminated: Aborted (script-fu:15893): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error - i don't seem to find any similar bug reports and am wondering if i should file a bug, and if, against Script-Fu or libgimp? It's neither Script-Fu nor libgimp. I suggest you file a bug report on GTK+ and attach a stack trace. / Martin -- My GIMP Blog: http://www.chromecode.com/ Best way to keep up with GIMP from git ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.8 schedule
Liam R E Quin wrote: clean up on-text editing, is there a better description? Not yet, but everyone is free to look into exactly what we need to do and come up with more detailed tasks. On-canvas text editing simply needs to work a bit better than it currently does. Just by using it it's possible to find things that could work better. / Martin -- My GIMP Blog: http://www.chromecode.com/ Best way to keep up with GIMP from git ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] A big thank you
On Tue, 2010-01-12 at 19:55 +0100, Martin Nordholts wrote: Yes I can, I would love it, any suggestion? I would like a user driven gimp.org. With our current static web page only the ones with commit access can improve the web page. With more wiki-like site we could have a website that is alive. We definitely want to limit who can change the web-site, right? We have a wiki already, there is really no need for the main web-site to be editable by the public. The current Wiki already suffers from the problem that it needs a lot of maintainance and we have not enough people willing to spend this time. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.8 schedule
On 1/11/10, Martin Nordholts wrote: Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more reasonable. And still somewhat scary :) The plan however does not seem to mention Python scripting improvements branch. (which will make estimations only scarier :)) Alexandre ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.8 schedule
On Wed, Jan 13, 2010 at 8:57 AM, Alexandre Prokoudine alexandre.prokoud...@gmail.com wrote: On 1/11/10, Martin Nordholts wrote: Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more reasonable. And still somewhat scary :) The plan however does not seem to mention Python scripting improvements branch. (which will make estimations only scarier :)) I thought that had already been merged. Was it only a partial merge? ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.7 (git) crashes with Gtk error
On Wednesday 13 January 2010 12:27:20 am Martin Nordholts wrote: Gtk:ERROR:gtkrbtree.c:1098:_gtk_rbtree_find_offset: assertion failed: (tree) .gimp/bin/gimp-2.7: terminated: Aborted (script-fu:15893): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error - i don't seem to find any similar bug reports and am wondering if i should file a bug, and if, against Script-Fu or libgimp? It's neither Script-Fu nor libgimp. I suggest you file a bug report on GTK+ and attach a stack trace. excuse me if i'm dense, but how comes this error occurs when using GIMP 2.7, but not with 2.6.8 on the same machine? it's the same plugins at work, and the same version of GTK+. -- phani. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.7 (git) crashes with Gtk error
phanisvara das wrote: On Wednesday 13 January 2010 12:27:20 am Martin Nordholts wrote: Gtk:ERROR:gtkrbtree.c:1098:_gtk_rbtree_find_offset: assertion failed: (tree) .gimp/bin/gimp-2.7: terminated: Aborted (script-fu:15893): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error - i don't seem to find any similar bug reports and am wondering if i should file a bug, and if, against Script-Fu or libgimp? It's neither Script-Fu nor libgimp. I suggest you file a bug report on GTK+ and attach a stack trace. excuse me if i'm dense, but how comes this error occurs when using GIMP 2.7, but not with 2.6.8 on the same machine? it's the same plugins at work, and the same version of GTK+. It's ok. What version of GTK+ is this? One reason you get it in 2.7 but not 2.6.8 is that 2.7 uses the GTK+ API in a way that triggers the bug, while 2.6.8 does not. / Martin -- My GIMP Blog: http://www.chromecode.com/ Best way to keep up with GIMP from git ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP 2.8 schedule
Alexandre Prokoudine wrote: On 1/11/10, Martin Nordholts wrote: Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more reasonable. And still somewhat scary :) The plan however does not seem to mention Python scripting improvements branch. (which will make estimations only scarier :)) Yes, if I recall correctly, Lars said there was still work left to do which he would not have time to fix for 2.8. I might be wrong though. / Martin -- My GIMP Blog: http://www.chromecode.com/ Best way to keep up with GIMP from git ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] PF_FILE of the register functi on in python plugins with 'new file' support (Sco tt)
My way around this was to use a PF_DIRNAME immediately above the PF_STRING and combining them for the total path. Ah, thank you very much. I wasn't aware of PF_DIRNAME. It's missing in the GIMP Python docs. This way I have a nice workaround which totally fits my needs. What else PF_ data types are missing in the docs? Or the other way around: Where can I read about all currently existing types? Kostenlos tippen, täglich 1 Million gewinnen: zum WEB.DE MillionenKlick! http://produkte.web.de/go/08/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] PF_FILE of the register function in python plugins with 'new file' support (Scott)
On Wed, Jan 13, 2010 at 5:52 PM, Mathias Lindner mathias.lind...@web.de wrote: My way around this was to use a PF_DIRNAME immediately above the PF_STRING and combining them for the total path. Ah, thank you very much. I wasn't aware of PF_DIRNAME. It's missing in the GIMP Python docs. This way I have a nice workaround which totally fits my needs. What else PF_ data types are missing in the docs? Or the other way around: Where can I read about all currently existing types? /usr/lib/gimp/2.0/python/gimpfu.py defines the types on a standard Linux install of GIMP. I think all except PF_DIRNAME are documented, though. (there's no steady maintainer for PyGimp or its documentation, so making sure it's up to date is currently somewhat a matter of luck) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
