asuwish4

OK, This is crazy. I'm using 8.2: I created a sub-VI that is essentially a dialog box. it is a string display with OK and CANCEL buttons beneath it. There is a string control that is used to feed the string indicator from a calling VI. After one of the dialog buttons is pressed, I feed an empty string to a property node of the string indicator before closing the sub-vi. I am using it in a VI that feeds a string constant into this dialog VI. While testing it I found that after the dialog closes, my string constant, that was feeding it, goes blank.... bearing in mind that the string constant is not even in the dialog sub-vi, but in the calling VI. However, if I replace the property node with a local variable, it works fine. ??? Chuck

I use a single, 20" Silicon Graphics CRT (Trinitron) monitor set at 1280x1024. I try to maintain those limits but you know.... I guess my true goal is to get a boxlight projector, hook it up to my laptop, and find an old closed drive-in movie theater and use that for my screen... Chuck

It would be REALLY helpful if, within the list of every instance of a particular variable, it would tell you if each instance is a read or a write. After refactoring so much code, I'm convinced that this would save oodles of time. btw "oodles" is an industry term. Thanks, Charlie

We all (should) know that saving your vi, zeroes your undos for that vi. However, it turns out that merely getting to the SAVE or SAVE AS dialog box zeroes it as well. Accidently clicking on SAVE (when working on a previously unsaved vi) or SAVE AS (while working on any vi) and then pressing CANCEL, will zero your undos as well. I discovered it in 6.1 and it still does it in 7.0. I do not have 7.1 but I believe someone had mentioned the bug is still extant in 7.1 as well. Steps for reproducing the bug: 1. open a blank vi 2. drop a few controls or indicators on the front panel 3. click FILE->SAVE or Cntrl-S 4. When the dialog box opens, click CANCEL 5. press Cntrl-Z Nothing happens. go to EDIT->UNDO and it is greyed-out. This also happens will an existing saved vi that you make chages to and then try to SAVE AS. It seems any time the file dialog box is displayed for saving, the undos are reset - whether you actually save it or not. Chuck Spitaleri

We all (should) know that saving your vi, zeroes your undos for that vi. However, it turns out that merely getting to the SAVE or SAVE AS dialog box zeroes it as well. Accidently clicking on SAVE (when working on a previously unsaved vi) or SAVE AS (while working on any vi) and then pressing CANCEL, will zero your undos as well. I discovered it in 6.1 and it still does it in 7.0. I do not have 7.1 but I believe someone had mentioned the bug is still extant in 7.1 as well. Steps for reproducing the bug: 1. open a blank vi 2. drop a few controls or indicators on the front panel 3. click FILE->SAVE or Cntrl-S 4. When the dialog box opens, click CANCEL 5. press Cntrl-Z Nothing happens. go to EDIT->UNDO and it is greyed-out. This also happens will an existing saved vi that you make chages to and then try to SAVE AS. It seems any time the file dialog box is displayed for saving, the undos are reset - whether you actually save it or not. Chuck Spitaleri