11-13-2013 07:22 PM - edited 11-13-2013 07:23 PM
While the Connector Pane Pattern is available in the ConPane properties, there doesn't seem to be an equivalent property to show the orientation/rotation. The only reference I can find on ni.com is a 10-year-old post which states that "we aim to include it in the next upgrade of LabVIEW". Am I just not able to find it?
11-13-2013 10:03 PM
I also don't see it.
11-14-2013 01:07 AM
I don't think I ever rotated or flipped a CP, so I can't say I miss this, but there seems to be a roundabout way of doing this - use the Terminal Bounds[] property to recognize the change. You can either write logic which will identify it from the data or you can use the methods to go through all the flipping and rotation permutations for each pattern to generate a lookup table of the possible states, then use that to look up your current state.
11-14-2013 09:30 AM
@tst wrote:
I don't think I ever rotated or flipped a CP, so I can't say I miss this,
Not only have I never used this, I didn't know it existed and it has been in a right click menu I probably use daily.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
11-14-2013 10:02 AM
I second Hooovahh. I could potentially see it being useful, however, when I make smaller icons and the connector pane I need is resulting in seeing the wire in the whitespace around the icon. A rotation could help me get the connectors I need in the right place. That said, this would probably be less than 1% of the VIs I make, as I generally try to stick with a standard, square icon.
To the OP, I'm curious what you need to determine the rotation for?
11-14-2013 11:35 AM
Do not rotate your ConPanes. Do not flip your ConPanes.
I have a lot of scripting code which I refuse to release publically because the logic I can use knowing that the conpane is standard (ie. error out is in terminal 0) is often quite simple. Adding the possibility for flipped ConPanes increases the code complexity significantly.
If you are stuck doing this, I do it this way which is much simpler than what tst was suggesting. That is to say simpler once you know what you are looking for....
11-14-2013 11:45 AM
@Darin.K wrote:
Do not rotate your ConPanes. Do not flip your ConPanes.
I have a lot of scripting code which I refuse to release publically because the logic I can use knowing that the conpane is standard (ie. error out is in terminal 0) is often quite simple. Adding the possibility for flipped ConPanes increases the code complexity significantly.
If you are stuck doing this, I do it this way which is much simpler than what tst was suggesting. That is to say simpler once you know what you are looking for....
how the ef do you figure this stuff out?
11-14-2013 12:07 PM
@for(imstuck) wrote:
how the ef do you figure this stuff out?
I enter the mindset of a LV developer and ask myself where would I put this information. Then I have to quickly leave that mindset, otherwise I wind up writing huge VIs with so many interdependencies I can no longer debug things and small changes in one area lead to changes all over the place...
11-14-2013 12:10 PM
@Darin.K wrote:
I enter the mindset of a LV developer and ask myself where would I put this information. Then I have to quickly leave that mindset, otherwise I wind up writing huge VIs with so many interdependencies I can no longer debug things and small changes in one area lead to changes all over the place...
Ohhh.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
11-14-2013 01:12 PM
Actually, you do neet to use tst's solution, since you can rotate and flip a connector pane multiple times. I would determine the connector pane pattern, pick two opposite terminals, find their actual positions, compare to known patterns, then use that to determine whether or not the pane has been rotated and/or flipped and where it went. All of this is irrelevant if you just don't do it (I don't).