I don't know if this is relevant to your case, or to darktable 2.x.x/gtk3 at all, but in the 1.x/gtk2 versions, I had weird things happening to that patch as a result of custom gtk2 theme settings... turns out it was actually a button widget, and was subject to shading, etc applied to that class... just a thought.
-- jys On Sun, Jan 28, 2018, at 00:02, David Vincent-Jones wrote: > Roman, .... after more thought, not totally convinced by your response. > If my patch covered a larger portion of the sky I should have been able > to get 3 clearly different results from max/min/mean. This shows > correctly in the saved information where the colors and data are > correctly represented. At no time does 'green' become part of the result. > > David > > > On 01/26/2018 09:25 PM, Roman Lebedev wrote: > > On Fri, Jan 26, 2018 at 11:21 PM, David Vincent-Jones > > <david...@gmail.com> wrote: > >> Picking an area color from the blue sky and displaying it in the > >> color-picker. > > You did note that you set it to "min", not "mean"? > > > >> The main patch shows an incorrect color (green not blue) but the > >> secondary saved patches are shown correctly and the rgb values are > >> correct; spot colors are OK. > >> > >> A small screen clip is attached. > >> > >> ver. 2.4.0 > >> > >> David > >> > >> > >> ____________________________________________________________________________ > >> darktable user mailing list to unsubscribe send a mail to > >> darktable-user+unsubscr...@lists.darktable.org > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
