11-26-2015 01:32 PM
@RavensFan wrote:
How does LV internally correlate how a wire connects with a tunnel?
I didn't check, but I'm guessing it doesn't. The wire has the Joints[] property, which I think includes the endpoints and I doubt that the tunnel cares which direction the wire comes from, as long as it's connected to the correct side. That would also explain why it doesn't fix it when the tunnel is moved to another wall.
11-30-2015 11:28 AM
Seems this is an actual topic.
So, it's time for a small summary ...
The answers to this thread are categorizable into two statements:
1) Yes, indeed it's a problen, even in LV2015.
Thus, I'll insert a post into the idea exchange.
2) This is just a proplem of missing skills of the programmer.
Here, some different strategies have been suggested, to avoid the situation, e.g. to clean up the wires immediately.
Are You never in a situation of a hurry, in that You simply forget about Your usual habits, just to get something done
quick and dirty?
In my opinion this shouldn't lead to code which seems to be "clean". A feature, that maintains the visibility of the wires,
while they are dragged, would help. The resulting code doesn't need to be pretty - it just shoud not hide important
details.
11-30-2015 11:31 AM
For "quick and dirty" I just wire everything up in a mess and run the diagram cleanup when I am done. It should make sure everything is visible.
11-30-2015 12:47 PM - edited 11-30-2015 12:49 PM
For "quick and dirty" I just wire everything up in a mess and run the diagram cleanup when I am done. It should make sure everything is visible.
I think you don't want to use "diagram cleanup" if you edited something in clean code. I will mess up the good parts too.
The situation of the initial post came up, because I deleyed the "cleanup by hand task" and later on, I didn't notice the hidden wire. So, the code seemed to be clean, but the hidden wire was still there and messed up the data in the array .
Edit: please kudo this idea: