wim…Pascal came forth with the fix, so the bug was thus acknowledged as there was a solution. With so much on I am not aware of repeated calls to show it despite already feeling that it was acknowledged as a bug, some things get overlooked, especially when busy climbing over hurdle after hurdle including finding layers that have moved.
How does one show it happening, a video I suppose, but I struggle to find a way to make and upload, the fact that someone else has same issue I didnt dream it, happens to me a lot.
I will try to think of a way to show it happening, do a step by step screenie or something.
sat here in pyjamas as there is no time like the present, breakfast can wait !
attached a step by step in photoshop of what happens. print screen by printscreen, step 1 at base of layers palette, turn off all photoshop layers then turn them on 1 by 1 starting at bottom.
I have it do this whilst working, this time I decided to close and open layer palette as I do when working, that from memory does it, didnt on this occasion, closing and opening the file did it !
see long jpg attached, another 20 mins spent , hope this is visible.
start at top, the timeline is downwards.
3 weeks behind thanks to central heating debacle so need to catch up with work backlog, so I dont have time just now to try for a normal working time on a file and study it by the minute for when it happens, and also keep doing screen captures at every stage of the workflow, as not started my days work yet through other things going wrong here, to replicate if it happens with layer palette turned off and on, it did it as can be seen with closure of rhino. thats for sure.
V4 never did it, V5 does it. V4 and V5 on tower and laptop. tower win7, lappy xp.
Will do this test on lappy when get time.
I only bring objects or curves from one file to another using edit copy edit paste, most of the time I am working within a file,
taking final product out for clarity purposes, grab the final bits and leave behind the mess ! make into stl etc.