LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

code improvements


johnsold wrote:

Ravens fan,

 

Mostly the lack of tunnel alignment bothered me and at least part of that is due to the use of several different connector panes on the subVIs.  When I converted the stacked sequences to flat sequences on the way to eliminating them some extra bends appeared, but I guess I cannot blame that on the auto wiring.

 

Actually I meant auto wire routing.  I have autowiring turned on.  Although that seems to grab the wrong connector pane terminal more often than the right one when placing a node on an existing diagram.  The auto routing tool seems designed to create extra bends in wires.  It will not wire straight to a terminal if some other object is within some minimum pixel spacing of the wire route.  If I could set that minimum to one or maybe even zero, it might help.  Wiring past a multiply to an add for example.

 

Lynn 


Thanks for the response.  I didn't pay close attentions to the subVI's because they were all non-existent to me.

 

I now understand better what you are talking about for auto wire routing vs. autowiring.  I have both turned on my default and it is the autowiring that usually doesn't come into play for me because I don't try to place functions that close to each other.  I agree that in you screenshot, the lower straight wire is better than the upper bent one.  But the upper one doesn't bother me that much and I live with it.  When it happens, I usually just move the terminal or constant a bit so I have just a single bend.

 

I like the auto wire routing as it lets me place wires without having them accidentally appear behind other objects.  I try to space things out enough to prevent this from happening.  But if the auto wiring gives me a crazy route, I let it so the wire is not lost behind an object.  Then I go back and adjust the functions and wires to straighten things out again.  I find it best to neaten up wiring even if it takes a few seconds after placing every few functions, rather than spending a long time trying to clean up everything at once at the end.

Message Edited by Ravens Fan on 12-19-2008 05:36 PM
Message 11 of 15
(846 Views)

About the auto wire routing. In general I like it, but sometimes the wire takes strange paths. But there's a simple solution to that: just hit 'a' while in wiring mode and you're free to direct the wire yourself Smiley Happy

 

Daniel

 

Message 12 of 15
(835 Views)
This somewhat makes sense but I am not very familiar with action engines. I read some of bens post about them which is equivelant to a book, but it was a lot of info. Maybe I'm just being lazy but is there any way someone could put a .png of a brief example on here? If not I will just keep hacking away at it. Thanks for everyones help and im glad I inspired such a discussion haha.
0 Kudos
Message 13 of 15
(805 Views)

Hi,

 

An action engine is just a modified functional global variable. However, I do suggest looking at Ben's post to get a clear picture of action engines. The action engine essentially makes the operations in the running average program share the same block of memory while the functional globals read from or write to the data stored in the USR. 

 

Ipshita C. 

National Instruments
Applications Engineer
0 Kudos
Message 14 of 15
(771 Views)
I will be going back to work in a little over a week since my winter break will be over so I was taking a look at this again. Will the XY graph in my code still plot the "old" data points if I "throw away the oldest values" when the array reaches its maximum size? I need all the points to be in a plot on the front panel and if I toss away the old data points to make room for the new ones wont they be gone from the plot when the array is sent? I will do it because it is obvious that I don't want issues w/ memory in the shift registers but I wanted to check all of my options.
0 Kudos
Message 15 of 15
(710 Views)