07-06-2015 01:14 PM
You are all certainly correct in that the code is not modularized enough, but I do enjoy programming in an object oriented fashion as well. The situation we deal with is in some instances we have had programmers make code that does not made use of clusters to the utmost, and then I have had to maintain or expand upon the code. I re-program everything while attempting to not make more work for myself in Veristand and other sub-VI's, and I think in some cases it's easier to just add another terminal and utilize clusters there-foreward. I consolidate existing terminals according what makes sense time-wise. At the end of the day, it just isn't a friendly sized tool to work with.
The other main issue that I am having which I haven't heard a solution for (perhaps I simply haven't understood) is in selecting whether a Terminal is required/optional. This is a two step operation. First click the small box and then select the variable associated with it. Next go back, find the small box again, hope that you right click in the correct box and define the Connection as Optional/Required... It does help to view the Context Help to make sure after performing those tasks to make sure you performed the operation on the correct terminal, but it may mean you have to repeat the operation again if it wasn't performed properly the first time. Is there a faster manner to perform this operation?
Thanks,
07-06-2015 01:31 PM
I don't think it is two steps, but it sure could be improved. For me I just right click the connector pane terminal and choose This Connection is >> Required. Why do you first have to select the control? Or are you saying you don't know which terminal you want? Having the context help open helps with this.
But you are right. I think a easier solution would be to right click the control on the front panel. And if that connector is connected to the connector pane, then a menu should open saying This Terminal is >> Required. If that isn't on the idea exchange yet I suggest you post it. A quick search didn't come up with this idea.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
07-06-2015 01:39 PM - edited 07-06-2015 01:39 PM
@Hooovahh wrote:
But you are right. I think a easier solution would be to right click the control on the front panel. And if that connector is connected to the connector pane, then a menu should open saying This Terminal is >> Required. If that isn't on the idea exchange yet I suggest you post it. A quick search didn't come up with this idea.
I think a quick shift-click or alt-click could be an easy solution for this. Each click could show a tip-strip saying the new configuration of the terminal. Easy Peasy.
Cheers
--------, Unofficial Forum Rules and Guidelines ,--------
'--- >The shortest distance between two nodes is a straight wire> ---'
07-06-2015 02:19 PM
James.Morris wrote:
I think a quick shift-click or alt-click could be an easy solution for this. Each click could show a tip-strip saying the new configuration of the terminal.
I think I like this idea better, I just know it would be easier for NI to make the change the way I described it, so much so that I bet I could make something that does this in the future.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
07-06-2015 11:58 PM
I know that NI is aware of this issue with LV and looking into solutions, but I guess it can be difficult with almost thirty years of code which could depend on it.
I agree with the others about trying to avoid the larger panes.
I pretty rarely change the terminal settings. There is an option in LV to set them to required by default and that applies to most of the inputs on my subVIs, so I don't need to touch them.
If you really want, you can change the subVI view by right clicking a subVI call and unchecking the icon view. This will make it easier to wire, but will cost you a lot of space on the BD. It also won't help with manipulating the CP itself.
If it does bother you a lot, you could write some tools to handle it. This could be for example showing a large connector pane (as you originally asked and which I have seen people do), doing something along these lines, writing a Quick Drop shortcut which will find the selected control on the CP and set its rule, going in the reverse direction (which probably won't help you), etc. These are just from a quick search, so there might be others which are more suited for you or you could modify them.
07-07-2015 12:03 PM - edited 07-07-2015 12:06 PM
Ah the magic words "Required Connection" and "VeriStand"
OK I feel your pain. I do know that there is visability with the VS tools development team to make the create VS model tool a bit more user friendly. but that does not help today
Tools>>Options>>Front panel.General
Hit that checkmark before wiring the connector pane. (or after wiring just the ones you want recommended) the option applies to any control you connect when you connect it. Convienient that its the first item in the options editor
Why that option is not setable on a vi by vi basis from VI Properties Editor options is something that I've felt is an overlooked + that could easilly be implemented.
07-07-2015 02:18 PM
@JÞB wrote:
Why that option is not setable on a vi by vi basis from VI Properties Editor options is something that I've felt is an overlooked + that could easilly be implemented.
What would be the point? Setting inputs on a single VI is a relatively short operation. Why would you want to configure a specific VI to default all inputs from this point forward to a specific setting? Why not just set up the inputs and then change the ones which need changing?
07-07-2015 02:34 PM
@tst wrote:
@JÞB wrote:
Why that option is not setable on a vi by vi basis from VI Properties Editor options is something that I've felt is an overlooked + that could easilly be implemented.
What would be the point? Setting inputs on a single VI is a relatively short operation. Why would you want to configure a specific VI to default all inputs from this point forward to a specific setting? Why not just set up the inputs and then change the ones which need changing?
If you are using a sane connector pane pattern it really is about even. for that full 28 terminal pattern ---setting a bunch just by wiring after quick Ctrl+I, check mark, enter can save some eye strain. of course a custom menu shortcut to the option dialog is just as handy.
07-07-2015 02:35 PM
Jeff: Thanks, setting all Panes to "Required" will be helpful when creating new VI's in the future.