Re: [darktable-devel] gui_synch madness

2012-11-04 Thread Ulrich Pegelow
Another simple fix would be to change line 125 in darkroom.c:expose() to if(dev->gui_synch && !dev->image_loading) That way dt_iop_gui_update() is only executed after image is completely loaded, which implies that all parameters are available and blend gui is set correctly. Ulrich Am 04.11.20

Re: [darktable-devel] gui_synch madness

2012-11-04 Thread johannes hanika
aha. i guess that line should rather go into dt_dev_reload_image (around 334 same file). maybe that's the reason for the issues houz had the other day, with gui_update() being called and sometimes not.. depending on moon phase. gui_synch is a flag that tells the gui thread later on to call gui_upda

Re: [darktable-devel] gui_synch madness

2012-11-03 Thread Ulrich Pegelow
Short addition: all problems seem to be gone if dev->gui_synch is not set in line 264 of develop.c Ulrich Am 03.11.2012 23:18, schrieb Ulrich Pegelow: > Hi, > > maybe someone can help me here. It's a complicated thing about ui updates. > > There is an issue with expansion of blend controls when

[darktable-devel] gui_synch madness

2012-11-03 Thread Ulrich Pegelow
Hi, maybe someone can help me here. It's a complicated thing about ui updates. There is an issue with expansion of blend controls when you open an image in darkroom mode. Let's say you have an image with module highpass activated, with blend mode "overlay" and with conditional blending set to ac