{"push_id":1064043377,"size":1,"distinct_size":1,"ref":"refs/heads/od6.0","head":"12a6822d812c3c84fc6e22d19651858bcc10cdbb","before":"45221df8c13e7d96c7f42da5357aa3ce6ff8fc9d","commits":[{"sha":"12a6822d812c3c84fc6e22d19651858bcc10cdbb","author":{"email":"78cee6616ca25e6c7f708c42d961b3a21d8d3575@dgbes.com","name":"Jaap Glas"},"message":"[od6.0] Adding, removing and adding again a stored random line in 3D scene\nprovided a weird line with duplicated nodes.\n\nSummary:\n(1) Adding, removing and adding again a stored random line in 3D scene provided\na weird line with duplicated nodes. Introduced in revision r43317/D9947 by\nJaap about random line synchronization issues. Changing the random line ID is\na special case in which synchronization between the random line in /Geometry\nand /visSurvey is gone and needs to be re-established. setNodePositions(.)\nhas been split in a public part, and a protected part without geometrical\nrestrictions. The latter got an \"internalonly\" option to solve the bug.\n(2) Also removed special code for random lines with more than 50 nodes.\nTesting did not show any difference with and without that code for such lines.\nIn case moving_.trigger() has been the problem in the past, this is solved\nby a temporary NotifyStopper.\n\nTest Plan:\n(1) Tested in F3_Demo. Adding, removing and adding again the stored random\nline through all wells in 3D scene works perfect again. Also the duplication\nof a random line still works fine. The same holds if the base map window\nis popped up as well.\n(2) Used \"Example random contour demo 1 -> MFS4\", which has many nodes, to\nconclude that is does not make a difference (anymore) if the special code\nfor 50+ nodes is removed.\n\nReviewers: nanne\n\nReviewed By: nanne\n\nDifferential Revision: https://phabricator.dgbes.com:8443/D10059","distinct":true,"url":"https://api.github.com/repos/OpendTect/OpendTect/commits/12a6822d812c3c84fc6e22d19651858bcc10cdbb"}]}