[darktable-devel] updating git tags

2012-12-10 Thread Togan Muftuoglu
Hi, Looks like the git needs touch of a loving master as when I issue git describe --tags HEAD here is what I get release-1.1-110-gd8dbc97 Shouldn't it be release-1.1.1-whateversha1 number Togan -- LogMeIn Rescue: Anyw

Re: [darktable-devel] darktable and OpenCL

2012-12-10 Thread Ulrich Pegelow
Am 10.12.2012 21:16, schrieb Sebastian Wagner: > Hi Ulrich, > > I'm chiming in here in with my question. > I want to ask if there's something else that influences dt's decision on > accepting a GPU's OpenCL capacities. I have a GPU with only 255MB, and > yes I know it's very low, I've set opencl_m

Re: [darktable-devel] Bug with GTK+ theme

2012-12-10 Thread Pascal de Bruijn
On Mon, Dec 10, 2012 at 9:48 PM, François-Xavier wrote: > Excellent, that fixed the problem right away. > Maybe this gtk2-engines should be set as a dependency for dt ? Well gtk2-engines isn't a build dependancy because it's not required for building Darktable. Most packages do have gtk2-engines

Re: [darktable-devel] Bug with GTK+ theme

2012-12-10 Thread François-Xavier
Excellent, that fixed the problem right away. Maybe this gtk2-engines should be set as a dependency for dt ? Anyways tks a lot -- François-Xavier GSELL On Mon, Dec 10, 2012 at 8:25 PM, Pascal de Bruijn wrote: > On Mon, Dec 10, 2012 at 9:18 PM, François-Xavier > wrote: > > Hello, > > > > Fir

Re: [darktable-devel] Bug with GTK+ theme

2012-12-10 Thread Pascal de Bruijn
On Mon, Dec 10, 2012 at 9:18 PM, François-Xavier wrote: > Hello, > > First thanks for the great work, every new release of darktable is > delightful. > > Since I migrated to fedora 18, I have troubles with the GTK+ theme. It makes > draktable unusable with fedora/gnome 3.6 default theme. A screens

[darktable-devel] Bug with GTK+ theme

2012-12-10 Thread François-Xavier
Hello, First thanks for the great work, every new release of darktable is delightful. Since I migrated to fedora 18, I have troubles with the GTK+ theme. It makes draktable unusable with fedora/gnome 3.6 default theme. A screenshot will explain it. (And sorry about the SSL Warning) https://owncl

Re: [darktable-devel] darktable and OpenCL

2012-12-10 Thread Sebastian Wagner
Hi Ulrich, I'm chiming in here in with my question. I want to ask if there's something else that influences dt's decision on accepting a GPU's OpenCL capacities. I have a GPU with only 255MB, and yes I know it's very low, I've set opencl_memory_requirement to 255 (same with 254), but dt still deac

Re: [darktable-devel] over/under exposure warning

2012-12-10 Thread Martin (Lists)
Am 10.12.2012 19:37, schrieb Pascal de Bruijn: > On Mon, Dec 10, 2012 at 6:27 PM, Martin (Lists) wrote: >> Hallo >> >> I recently had to do some testing with my display profile and I found an >> unexpected (at least for me) effect: under/over exposure warning changes >> with the display profile. I

Re: [darktable-devel] over/under exposure warning

2012-12-10 Thread Pascal de Bruijn
On Mon, Dec 10, 2012 at 6:27 PM, Martin (Lists) wrote: > Hallo > > I recently had to do some testing with my display profile and I found an > unexpected (at least for me) effect: under/over exposure warning changes > with the display profile. If I use my display profile I got a little > more over/

[darktable-devel] over/under exposure warning

2012-12-10 Thread Martin (Lists)
Hallo I recently had to do some testing with my display profile and I found an unexpected (at least for me) effect: under/over exposure warning changes with the display profile. If I use my display profile I got a little more over/under exposure warning than with no display profile or sRGB. I did

Re: [darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread Moritz Moeller
On 10/12/12 10:37 PM, parafin wrote: > There aren't any libstdc++ in DMG and no binary in there links to any > libstdc++ other than /usr/lib/libstdc++.dylib. Then something that DT links against (possibly/likely statically) was linked against a different libstdc++. I can see the app itself is li

Re: [darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread parafin
By bugzilla I of course mean our redmine bug tracker. On Mon, 10 Dec 2012 18:37:42 +0400 parafin wrote: > There aren't any libstdc++ in DMG and no binary in there links to any > libstdc++ other than /usr/lib/libstdc++.dylib. > Please supply full crash report, and better do it via bugzilla - I'm

Re: [darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread parafin
There aren't any libstdc++ in DMG and no binary in there links to any libstdc++ other than /usr/lib/libstdc++.dylib. Please supply full crash report, and better do it via bugzilla - I'm not generally reply to mailing list messages. On Mon, 10 Dec 2012 22:21:56 +0800 Moritz Moeller wrote: > On 10

Re: [darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread Moritz Moeller
On 10/12/12 10:05 PM, parafin wrote: > DT has been usable on OS X for a long time, No it hasn't. I am reporting this issue for the 3rd time now. I can not use DT on my retina macbook running OS X 10.7.5 with all latest patches ever. If you import some images and edit it works beautifully. If you

Re: [darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread parafin
DT has been usable on OS X for a long time, and with 1.1.1 release the last annoying bug has been fixed (crash when adjusting curves). Try DMG image and you will see. More to the point - you're using non-system C++ compiler, that's why darktable is linked for you to macports libstdc++. Don't do it!

[darktable-devel] DT OS X is still crashing when reading XMPs

2012-12-10 Thread Moritz Moeller
The std::string crash is still making DT more or less unusuable on OS X. Thread 4 Crashed: 0 libstdc++.6.dylib 0x7fff8e028220 std::string::_Rep::_M_grab(std::allocator const&, std::allocator const&) + 4 1 libstdc++.6.dylib 0x7fff8e02834d std::basi

Re: [darktable-devel] iop and distortions

2012-12-10 Thread alic VB
2012/12/9 johannes hanika > On Mon, Dec 10, 2012 at 10:48 AM, AlicVB wrote: > > Hi all, > > > > Just a thought : I think module should expose function if they do image > > distortion. Now we have just the spot iop which suffer of problem, but > > the mask tool will have this problem too : > > ex