Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am Mittwoch, 21. Juni 2017, 09:33:13 CEST schrieb Robert William Hutton: > On 21/06/17 04:47, Germano Massullo wrote: > > It would be also interesting to know if there will be changes in > > darktable dependencies, so that package maintainers can early start > > working on them > > I'll do some

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

On Wed, Jun 21, 2017 at 12:17 PM, Tobias Ellinghaus wrote: > Am Mittwoch, 21. Juni 2017, 09:33:13 CEST schrieb Robert William Hutton: >> On 21/06/17 04:47, Germano Massullo wrote: >> > It would be also interesting to know if there will be changes in >> > darktable dependencies, so

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

I am running gtk3 3.20.10-5.3.1 ... but there are a number of 'secondary' packages that are carrying entirely different version numbers. PackageKit-gtk3-module 1.1.3-3.2 gtk3-branding-openSUSE 42.1-3.1 . (I am running openSUSE 42.2) No modules show any available updates. Is there any

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto >> I've also been working on Wayland support >> (https://redmine.darktable.org/issues/11535). This is mostly done, but >> isn't worth enabling until GTK+ >= 3.22.16 makes its way into >> distributions. Wayland support doesn't seem to me to be

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am Mittwoch, 21. Juni 2017, 19:01:10 CEST schrieb David Vincent-Jones: > The image import problem still exists on my system requiring this > strange work-around (multiple tabbing and then a Ctrl a). This is a > nuisance apart from anything else. Is there any light at the end of this > tunnel and a

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am Mittwoch, 21. Juni 2017, 13:06:48 CEST schrieb David Vincent-Jones: > I am running gtk3 3.20.10-5.3.1 ... but there are a number of That's the broken version. It seems a recent 3.22 is only in Tumbleweed. I am sorry but there is nothing we can do, besides encouraging to upgrade or to look

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am Mittwoch, 21. Juni 2017, 21:44:30 CEST schrieb Germano Massullo: > Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto > > >> I've also been working on Wayland support > >> (https://redmine.darktable.org/issues/11535). This is mostly done, but > >> isn't worth enabling until GTK+ >= 3.22.16

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

heya, On Thu, Jun 22, 2017 at 4:35 AM, Moritz Mœller (The Ritz) wrote: > On June 20, 2017 18:34:27 Roman Lebedev wrote: >> >> On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller >> wrote: >>> >>> On 20.6.17 11:43 , Tobias

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Germano Massullo writes: > Il 21/06/2017 17:43, Tobias Ellinghaus ha scritto >>> I've also been working on Wayland support >>> (https://redmine.darktable.org/issues/11535). This is mostly done, but >>> isn't worth enabling until GTK+ >= 3.22.16 makes its way into >>>

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am 21.06.2017 um 18:03 schrieb Dan Torop: I'd say that is well withing the time frame – provided it's not too invasive. That is great. Should be a tweak to the Bayer downscale code (making start/endpoints of sample right), bringing that work to X-Trans, and then SSE variants. Please

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: > Hi Tobias, > > I've been working on downscaling mosaiced images without (or with fewer) > artifacts (https://redmine.darktable.org/issues/11167). Right now there's > workable code for Bayer and X-Trans in git master. The main flaw is

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

Tobias Ellinghaus writes: > Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: [...] >> I will be able to get to this again in early July. Is that soon enough to >> make its way into 2.4.0? Additional improvement would be slightly better >> quality zoomed-in rendering

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

I don't use Wayland for that very reason. On Wed, 21 Jun 2017 at 17:04 Dan Torop wrote: > > Tobias Ellinghaus writes: > > > Am Mittwoch, 21. Juni 2017, 11:39:30 CEST schrieb Dan Torop: > > [...] > > >> I will be able to get to this again in early July. Is that

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

On Wed, Jun 21, 2017 at 7:35 PM, Moritz Mœller (The Ritz) wrote: > On June 20, 2017 18:34:27 Roman Lebedev wrote: >> >> On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller >> wrote: >>> >>> On 20.6.17 11:43 , Tobias Ellinghaus

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

On June 20, 2017 18:34:27 Roman Lebedev wrote: On Tue, Jun 20, 2017 at 5:55 PM, Moritz Moeller wrote: On 20.6.17 11:43 , Tobias Ellinghaus wrote: I'm using a local build with [...] Wolfgang Mader's modern monochrome modules since about 4 months and

[darktable-dev] Flash data in "image information" panel?

Hi, Is there a reason (beyond UI space) that flash information is not displayed? Or is it somewhere else that I'm missing? Either way, it would be rather nice if flash data was included in the image information panel. Thanks.

Re: [darktable-dev] Planning of the upcoming 2.4.0 release

The image import problem still exists on my system requiring this strange work-around (multiple tabbing and then a Ctrl a). This is a nuisance apart from anything else. Is there any light at the end of this tunnel and a fix in sight? I am running the latest git on OpenSUSE with XFCE desktop.