El 18/07/13 00:27, Jason Simanek escribió:
Hi,
Is there any way to set default JPG/PNG/whatever export settings? I am
manipulating a lot of images right now and every JPG export involves
changing the Quality, the Smoothing and the DCT method. Over and over
and over. This happens with Export as
Hey all,
it seems I am the culprit for this bug. I don't have this crash on Linux though.
It looks like the implementation of setenv/getenv is different on OSX.
According to glib doc, the problem may be that on some
implementations, successive calls may use the same buffer. I guess
that's the
Hi,
On 07/18/2013 01:05 AM, Guillermo Espertino (Gez) wrote: Just save a
new default with the settings you want and it will be used
next time you export.
Well, now I feel dumb. Thanks Gez!
This certainly fulfills my need, but I find it odd that the only way to
alter that setting is from
Hi Carlos,
nice to read your update! I'd like to see updates here on the mailing
list from other GSoC students too.
Regards
Tobias
2013/7/14 Carlos Zubieta czubieta@gmail.com:
Hi everyone,
This is a report of my gsoc work's status until now.
-Already ported
Color-to-alpha
El 18/07/13 10:28, Jason Simanek escribió:
Hi,
On 07/18/2013 01:05 AM, Guillermo Espertino (Gez) wrote: Just save a
new default with the settings you want and it will be used
next time you export.
Well, now I feel dumb. Thanks Gez!
This certainly fulfills my need, but I find it odd that the
Hi again,
I have some working code in my working branch now where I applied the
concepts I wrote about (basically initializing the language store only
once and at the very start of the program, before any threading would
occur hopefully).
Don't know if that will be the finale code, but should be
Sounds good. I will file a bug.
Thanks,
Partha
On Thu, Jul 18, 2013 at 8:40 AM, Michael Natterer mi...@gimp.org wrote:
On Wed, 2013-07-17 at 17:31 -0400, Partha Bagchi wrote:
Hey V,
Thanks for checking on this. I am glad (in a way) that my system is not
the
only one having this
Jehan,
I will test it tomorrow. I will get back to you with the results.
Thanks for your prompt response!
Partha
On Thu, Jul 18, 2013 at 11:42 AM, Jehan Pagès jehan.marmott...@gmail.comwrote:
Hi again,
I have some working code in my working branch now where I applied the
concepts I
Hi,
I searched a little more though, and it seems on BSDs, hence on OSX,
indeed setenv with a NULL value could crash the program. The setenv in
GNU libc on the other hand perfectly handles the case explicitly.
So obviously when I see this kind of code (note I am not 100% sure
this is the code for
Jehan,
Do you want me to go ahead test the current code or wait for you to add
additional logic?
Thanks!
Partha
On Thu, Jul 18, 2013 at 10:04 PM, Jehan Pagès jehan.marmott...@gmail.comwrote:
Hi,
I searched a little more though, and it seems on BSDs, hence on OSX,
indeed setenv with a
Partha,
nothing pushed yet. I'll do this and send a message. :-)
Jehan
On Fri, Jul 19, 2013 at 11:21 AM, Partha Bagchi parth...@gmail.com wrote:
Jehan,
Do you want me to go ahead test the current code or wait for you to add
additional logic?
Thanks!
Partha
On Thu, Jul 18, 2013 at
Hey Partha,
you can pull and test now. I made a simple commit where I only take
care of the unset env variable issue. Hopefully this will fix the OSX
crash. I'll handle the other issue I discovered about not being
thread-safe later.
Tell me how it goes. :-)
Jehan
On Fri, Jul 19, 2013 at 11:26
12 matches
Mail list logo
