LV7.1 - Property node inside a loop - bug or feature?

[SynergyMike]

Using LV7.1, I tried to create a property node for a front panel control that was located within a loop on the block diagram. The resulting node had a shadow outline and I couldn't move it at all.  However, when I moved the control outside the loop and created the node there, I could move both back inside the loop without any problems.  I duplicated this behavior with several different (simple) test programs, so it wasn't particular to my VI.  Is this a case of LV trying to "tell me something", or was this a known issue within 7.1?

Thanks.

Michael Tracy

Synergy Microwave

[Norbert_B]

Michael,

does this behaviour occur in new VIs as well or is it connected to an existing project?

Norbert 

[pincpanter]

I'm currently using 7.1 (not promoted to 7.1.1, though). When I try reproducing your problem, the property node does have a shadow outline, but it can be dragged to any position.

For anyone wondering, the shadow means that the node is not currently assigned to any region of the block diagram (neither to the loop inside nor to the outside) and must be dragged to the desired area.

[chrisger]

I can confirm pincpanter on LV 7.1.1. Both control and node can be dragged.

[SynergyMike]

Ok - I should have done more testing before I posted.  I had a flat sequence structure inside an event inside a loop, and assumed it didn't matter what the indicator was inside of.  I started over by cutting down the application until the problem was duplicated on a minimum block diagram:

I have a String indicator, and it has a separate reference (required because the string is "built" in an iterive process) that is inside a frame of a flat sequence structure (also happens within a stacked sequence).  If I right click on the indicator and select Create - Property Node, I wind up with a detached object that can't be moved.  This doesn't happen if the indicator lacks the reference, and it doesn't happen other than inside a sequence structure.  Maybe what I have here is simply a case of "Doctor, it hurts when I do this...", but I was just curious if the behavior was on purpose somehow - at this point, I think it is probably a real bug, but a _very_ minor one.

Regards,

Michael

[F._Schubert]

It couldn't reproduce the behaviour in 7.1. Perhaps you can post some code instead of the picture.

Felix

[SynergyMike]

VI attached.  I don't know if it makes any difference or not, but I'm running this under Windows XP.

Regards,

Michael

[Ipshita_C]

Hi Michael,

Running Windows XP is definitely not a reason as I followed your steps with Windows XP and LabVIEW 7.1 and could not reproduce the behavior. I would suggest checking if all the control and indicator kinds show the same problem, in that case it might be an installation issue.

Ipshita C.

[SynergyMike · Accepted solution]

After more fiddling with this, I finally discovered that it was a simple user (e.g., nut-behind-the-wheel) error.  I kept trying to select the floating node using the outline select feature and that wouldn't work, but when I carefully placed the mouse on top of it, I managed the click-and-drag move, no problem.  Oh well, live and learn!

Michael