great fix. only that it doesn't work :(
as LebedevRI pointed out, my elegant patch would also trigger redraw
whenever someone drops a read lock.. this is essentially an infinite loop
again. rewriting it to only send the signal on write (
https://github.com/darktable-org/darktable/pull/819) doesn't refresh
lighttable any more at all when it should. so i'm reverting to the stupid
timeout solution i had before.. let me know if anyone comes up with
something more elegant.
-jo
On Wed, Jan 7, 2015 at 2:48 AM, Pascal Obry <pas...@obry.net> wrote:
> > there is also something in master. does it still happen for you?
>
> No, fixed too. Our fixes were quite similar, I have close my pull-request.
>
> Thanks for fixing that!
>
> --
> Pascal Obry / Magny Les Hameaux (78)
>
> The best way to travel is by means of imagination
>
> http://v2p.fr.eu.org
> http://www.obry.net
>
> gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
