Académique Documents
Professionnel Documents
Culture Documents
http://labviewartisan.blogspot.in/2009/10/progress-report-1-block-diagr...
6 comments:
Yair October 27, 2009 at 1:14 PM The diagram explosion and overly bent wires are definitely what I find to be the biggest pain points. What's particularly annoying about the wires is that there's no good reason for them to have multiple bends. If you invoke a manual cleanup on the wire, it usually comes out with
1 of 3
12-Dec-13 12:15 PM
http://labviewartisan.blogspot.in/2009/10/progress-report-1-block-diagr...
considerably fewer bends. It seems to me that if the algorithm called a cleanup on each wire after it finished cleaning, the result would be better (although this might hurt performance). Reply
TonPlomp October 29, 2009 at 1:55 PM Fun experiment: Create a control and indicator of matching type. Line these two up. Create an exesive bendy wire in between. Only select the wire with triple-click. Select auto-cleanup. In LabVIEW 2009, this action is a no-op. Ton Reply
That's expected behavior to me, since Diagram Cleanup is focused on node placement, and not wire placement. If you take any arbitrary diagram and multi-select an arbitrary number of wires, I'm pretty sure you'll see a no-op there as well. Reply
Steve Bird October 30, 2009 at 8:06 AM I haven't moved my client to LV2009 yet, so I haven't used the Code Cleanup 2009 myself. But if expands the diagrams, bends the wires and moves the labels where IT wants to, then I still have to go along behind it and clean things up to fit my own standards. If that's the case, I don't see how I could get to the "twice as fast" point, as you have. What does it actually do FOR you, that saves you that much time? Reply
Darren Nattinger
I'm not going back to clean up after it. I'm basically declaring its results "clean enough". That's how I'm twice as fast now. And I'm sending feedback to the diagram cleanup team on things I would like to see it do better (like all the stuff in this blog post). Reply
Anonymous January 15, 2010 at 12:02 PM I have found that if you select a case structure and clean it up by itself, the case is small. Then if you right-click on it and disable cleanup on that case structure, then cleanup the next outer loop, the inner one stays tight. Then you can progressivly cleanup your code without so much sprawl. Reply
2 of 3
12-Dec-13 12:15 PM
http://labviewartisan.blogspot.in/2009/10/progress-report-1-block-diagr...
3 of 3
12-Dec-13 12:15 PM