Re: [Gimp-developer] Two notes for UI (inconsistency and cleanup)
On Friday 19 October 2007 07:57:26 pm Nemes Ioan Sorin wrote: Vladimir, things are in change, nothing can be done over night. I'm aware of that. I didn't want to sound like pushing someone to do something. If I did, then sorry... (but I'm not even in position for doing things like that) I found a lot of ...let say ...here could be better in few areas - but I prepare my material and my studies for the guys which work right now for GIMP UI redesign. Oh, well... I can't find my proposal to be bug or/and feature request. So I didn't open ticket in tracker. It's not UI redesign neither. It's more like, as I've said, inconsistency... :) But that's more like subjective classification :) I threw it in on mailing list. If developers/users think I need to fill report, I'll gladly do that. Please consider following links: http://gimp-brainstorm.blogspot.com/ http://gui.gimp.org/index.php/GIMP_UI_Redesign See you there, As soon as I do some redesign proposition, I'll catch you there. Vlada Sorin Vladimir Savic wrote: As I can see, GIMP UI is undergoing some minor cleanups in svn version. Just two observations. Nothing major. :) I've noticed that only Smudge Tool doesn't have brush scaling, which is just inconsistent to to other tools. And second one is about Pressure sensitivity. Opening that tab could align it's sub-options vertically not just horizontally (if tool window width is too small, of course). As is right now, everything fits into window here, but hitting the expand arrow brings sliders which can easily destroy window's layout. Regards, Vlada ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Two notes for UI (inconsistency and cleanup)
As I can see, GIMP UI is undergoing some minor cleanups in svn version. Just two observations. Nothing major. :) I've noticed that only Smudge Tool doesn't have brush scaling, which is just inconsistent to to other tools. And second one is about Pressure sensitivity. Opening that tab could align it's sub-options vertically not just horizontally (if tool window width is too small, of course). As is right now, everything fits into window here, but hitting the expand arrow brings sliders which can easily destroy window's layout. Regards, Vlada ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Two notes for UI (inconsistency and cleanup)
Vladimir, things are in change, nothing can be done over night. I found a lot of ...let say ...here could be better in few areas - but I prepare my material and my studies for the guys which work right now for GIMP UI redesign. Please consider following links: http://gimp-brainstorm.blogspot.com/ http://gui.gimp.org/index.php/GIMP_UI_Redesign See you there, Sorin Vladimir Savic wrote: As I can see, GIMP UI is undergoing some minor cleanups in svn version. Just two observations. Nothing major. :) I've noticed that only Smudge Tool doesn't have brush scaling, which is just inconsistent to to other tools. And second one is about Pressure sensitivity. Opening that tab could align it's sub-options vertically not just horizontally (if tool window width is too small, of course). As is right now, everything fits into window here, but hitting the expand arrow brings sliders which can easily destroy window's layout. Regards, Vlada ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] calling a procedure in a plugin
Thanks to all... Now it's work... You are attempting to modify a color at some random memory location, that's never been allocated (you didn't initialize colore) and then you passed this dodgy pointer to gimp_by_color_select. In most parts of the GIMP, GimpRGB are statically allocated, and you see that they are used more like this: GimpRGB colore; GimpChannelOps parametri; gboolean success; gimp_rgb_set_uchar(colore, pixel[0], pixel[1], pixel[2]); parametri = GIMP_CHANNEL_OP_REPLACE; success = gimp_by_color_select(drawable-drawable_id, colore, termogramma.scarto, parametri, FALSE, FALSE, 0.0, FALSE); _ Conosci Doretta? Contattala, รจ ora su Messenger! http://www.doretta82.it/banner/index.html ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] calling a procedure in a plugin
I have modified the code as you suggested: GimpRGB *colore; GimpChannelOps parametri; gboolean success; gimp_rgb_set_uchar(colore, pixel[0], pixel[1], pixel[2]); parametri = GIMP_CHANNEL_OP_REPLACE; success = gimp_by_color_select(drawable-drawable_id, colore, termogramma.scarto, parametri, FALSE, FALSE, 0.0, FALSE); The compiler returns me no error but when I execute the gimp return a fatal error: segmentation fault. I think the problem is in one of this line but, with my few experience, I can't find it... Hi, I think I already pointed you to the API reference for GimpRGB and gimp_rgb_set_uchar() in particular. GimpChannelOps is an enum and the possible values are listed in the API reference. Just follow the link. You can also save yourself the hassle of working with pixel regions if all you want to do is to get the color of a single pixel. There's gimp_drawable_get_pixel() for that purpose. Sven _ Crea i tuoi biglietti da visita con Windows Live Messenger! http://www.messenger.it/biglietti_da_visita.html ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] calling a procedure in a plugin
On 10/19/07, Giuseppe Pasquino [EMAIL PROTECTED] wrote: I have modified the code as you suggested: GimpRGB *colore; GimpChannelOps parametri; gboolean success; gimp_rgb_set_uchar(colore, pixel[0], pixel[1], pixel[2]); parametri = GIMP_CHANNEL_OP_REPLACE; success = gimp_by_color_select(drawable-drawable_id, colore, termogramma.scarto, parametri, FALSE, FALSE, 0.0, FALSE); The compiler returns me no error but when I execute the gimp return a fatal error: segmentation fault. I think the problem is in one of this line but, with my few experience, I can't find it... You are attempting to modify a color at some random memory location, that's never been allocated (you didn't initialize colore) -- and then you passed this dodgy pointer to gimp_by_color_select. In most parts of the GIMP, GimpRGB are statically allocated, and you see that they are used more like this: GimpRGB colore; GimpChannelOps parametri; gboolean success; gimp_rgb_set_uchar(colore, pixel[0], pixel[1], pixel[2]); parametri = GIMP_CHANNEL_OP_REPLACE; success = gimp_by_color_select(drawable-drawable_id, colore, termogramma.scarto, parametri, FALSE, FALSE, 0.0, FALSE); ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
