image display reference control still not working

[Vladimir_Drzik]

Is this issue planned to be resolved? The current version is LV2009 and the issue still persists.

[rpursley8]

It seemed to work for me.  Can you post the example you tried?

[Vladimir_Drzik]

I didn't check the workaround, because it was said that it can't be used in built application. Which makes it unusable for me. Anyway, I tried opening your attached example and my LV froze badly after running it. I'd rather like to see this issue resolved, not just worked around.

[rpursley8]

I didn't use the work around.  I dragged a image display reference from the block diagram of the main vi to the front panel of the sub vi.  I was able to hook it up and control the zoom of the image display from the sub vi.

j

[Vladimir_Drzik]

Well, thanks for the example, but... I actually think this is a hack NI wouldn't really want us to use.

I've got a couple of reasons:

• When I first did what you suggested, it really worked. However, on second run LV froze and popped up an internal error on restart. 
• When I took the example you attached, it did not work at all. The control reference in the subVI was somehow broken and after I somehow managed to make it runnable, LV froze immediately after running it.
• I took the version which worked for the first time and built it into an executable. That one crashed immediately after running.

To sum up, I think there's a good reason why LV doesn't allow you to create an image control reference control or indicator. Something inside just doesn't function the way it should.

Could anyone from NI give us the status of CAR# 3R1F8KRJ?

[esmaham]

Hi Lanmat ,

I will search the CAR database and check for any updates. Thanks and have a great day.

Esmail Hamdan | Applications Engineering | National Instruments  

[esmaham]

Hi Lanmat,

I have looked into the "CAR 3R1F8KRJ" and found out that it's still open and have been addressed for potential fix in the upcoming versions. We also have tried both of the workaround for this issue, and both worked for us. Since there is a viable workaround, this is not currently considered an urgent issue. If you still have issues with it, I highly suggest that you contact us so we can help you figure it out.

Thanks and have a great day.

Esmail Hamdan | Applications Engineering | National Instruments   

[Vladimir_Drzik]

Did the workaround work in a built executable?

[DirkLV]

You could create a dynamic event in the subVI, transfer it's reference to the main VI in a kind of "init" call of the subVI, and register it in the main VI as a dynamic event. Then, everytime you change a control value in the subVI, fire the event. In the main VI, the event is recognized and the method "image refresh" is executed for the image display.

That should work for built apps.

D.

[Vladimir_Drzik]

Dirk,

Yes you're right. But that's exactly what I don't  want to do in the case I'm trying to pass an image control reference to a subVI. In this case, I'm usually planning to do multiple different operations with the image control in the subVI. Moreover, there are usually more such subVIs for one parent VI. If I'd have to create a complicated user event structure in order to use the subVIs, I'd rather do all the image control manipulation inside the parent VI. Dirty but much easier.