Pot "verify" messes up data entry-Bug?- Others seen this?

[flexman]

Have others used "verify" element on a "pot" numeric entry?
I thought it would be a good user interface addition, so I made a "connection" with text element to the "verify" attribute of a Pot.
I was shocked to see that when "no" is selected from the verify message- the next object click on the panel will download whatever numeric value that last entered (on other fields) to the pot.

lookout 4.5.1 on Windows 98- must use numeric format to generate effect.

In more detail in case others want to try and duplicate:
Make two pots (Pot1, Pot2), put on a test panel
Display "digital entry" format (not slider or knob)
Edit connection Pot2: verify="warning"

Panel to run mode:
enter a recognizable value in Pot 1 (e.g. "13")
click on pot 2, at "warning" message, select "no".
click on Pot 1 again- POT 2 assumes value 13!

[A.S.]

Hi,
Thanks for contacting National Instruments. I was able to replicate this behavior here on the latest version of Lookout (version 6.0). This is most definitely an unexpected behavior. At this point, I have documented this in a step-by-step corrective action request to R&D. I will post a response as soon as I hear something from them. In the meantime, I'd suggest using sliders or pots instead of digital display for the pot display. I realize that this may not be the exact workaround you wanted, but until I hear back from R&D, this is the best thing to try.

Please let me know if we can help in any other way. Thank you for your patience.

A Saha
Applications Engineer
National Instruments

[hdp]

Additionally:

This effect will be seen with multiple pots. Create three pots and give them verify messages. Modify POT2, click on POT3 and select 'no', click again on POT3 and it assumes the value of POT2. Modify the value of POT1, click on POT3 and select 'no', click POT3 again and it assumes the value of POT1.

[flexman]

I simplified my example somewhat for posting, but all pots are affected. Also can select "no" multiple times and mis-enter on those multiple pots in a series.
The click doesn't have to be on any dynamic object, seems like next mouse click will do it.
The issue is related to the popup verify window. A connection of verify=if(danger=true,"Danger!","") will not bring up the dialog box if danger=false. No issue in this case. The problem isn't the connection to verify- it is the popup.
I suspect that there might be something related to the reset/resetvalue parameters, but they are write only so I cannot observe what is happening with them.
I have not been able to come up with a workaround.

[hdp]

And furthermore:

Add a slider for POT3.

Set POT3=10, POT2=20, POT1=40. Do this in the order shown.

Click on the digital display for POT3 and select 'no'. Now, drag the POT3 slider - POT3 again assumes the POT1 (last altered) value.

I can't say what it means, I'm just posting my observations.

[A.S.]

Thank you all for this additional information. I will edit the correction request document to include these observations. I will post something here as soon as I hear something from R&D on this issue.

Thanks!

[A.S.]

Hi,
R&D has researched this issue with the pot object. They have edited the pot object to try to fix this problem. So I will post the fixed pot CBX file on our FTP site. We would like it if you could please test this with your applications and ensure that it works okay. If it does work, then we will integrate this new pot CBX in our next fix.
So its absolutely imperative that we get feedback from you on this fix and whether it works well.

To get this fix, go to:
ftp://ftp.ni.com/outgoing and download the file called pot.cbx. Then copy this file to "C:\Program Files\National Instruments\Lookout 6.0". The last part may be different based on your version of Lookout. NOTE: Backup the existing pot.cbx file to another folder in case you need to revert back. This fix has been created for the latest Lookout version (v6.0), but I have tested it successfully in v5.1 and v6.0. We always implement fixes on the latest version of our software, but I think it should work with your version too.

Once this new pot.cbx has been verified by you, we will implement it in our fix. I would recommend re-downloading the fix when it releases. This is why I'm placing the pot.cbx file in the FTP site as a temporary download location.

Thank you for all your help!

[flexman]

This does NOT load with 4.51 lookout as purchased through Automation Direct. "error object class not loaded". Pot is then unavailable in object builder.

[A.S.]

Hi,
As I had mentioned before, we can only do development on the most current version of a software. However, I have told our R&D engineers about this fix not working in Lookout 4.5.1. As soon as I hear something back from them, I will post a response here.

Thanks for you patience!

[A.S.]

Hi,
The R&D engineer working on this issue was able to locate and modify the pot.cbx file for Lookout 4.5.1. I have uploaded it to our FTP site at ftp://ftp-stage.ni.com/outgoing/ . The name of the file is pot451.cbx. Move the existing pot.cbx to another folder and place this file in the Lookout folder where the original pot.cbx was located.

As I mentioned before, please test these and let us know how it works. I was able to get it working fine with Lookout 4.5.1, so I don't think you should have any trouble either.

Thanks!