On 30 Mar 2014, at 18:26, Lakshman <[email protected]> wrote:
> The attached patch tries to resolve the looping issue with the
> "entered" branch of yours. I am assuming that you were referring to
> this in irc today morning, I was sleeping then and missed it.
Lakshman,
I think your patch does with the new state variable emitPointEdit that prevents
the recursive calling is not a solution because it creates a race condition:
Imagine in drawProfile it is set to false and then via the UI the user creates
a new point by double clicking.
I have no better solution myself but I would think we have to better handle the
dataChanged signal/slot (basically not call plan when the data change is due to
added calculated deco stops). But I am not sure how to do that.
Best
Robert
--
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oO
Robert C. Helling Elite Master Course Theoretical and Mathematical Physics
Scientific Coordinator
Ludwig Maximilians Universitaet Muenchen, Dept. Physik
print "Just another Phone: +49 89 2180-4523 Theresienstr. 39, rm. B339
stupid .sig\n"; http://www.atdotde.de
_______________________________________________
subsurface mailing list
[email protected]
http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
