Jump to content


  • Posts

  • Joined

  • Last visited

Guenther's Achievements


Newbie (1/14)



  1. QUOTE (mesmith @ Nov 29 2008, 06:19 PM) Yes, this works indeed. I disabled "Show Front Panel when Called" in the sub-VI and called the FP.Open property for the sub-VI during initialization of the main VI. As expected, the window of the sub-VI pops open immediately, but the sub-VI does not grab focus anymore when called. Thanks for the solution! Cheers, Guenther
  2. Hi guys, I'm working on an application where the main VI repeatatly (every few sec) calls a sub-VI, which is visible in order to display some information. This call is made in the consumer loop of a state machine. On the other hand, the user should be able to edit the content of a control (numeric within an array within a cluster) in the main VI. However, each time the sub-VI gets called, the control in the main VI immediately looses key focus, which makes it very cumbersome to edit its contents.. Of course you can prevent the loss of key focus by making the main VI modal, but that also prevents any user interaction with any sub-VI, so I'd like to avoid this. In this thread Yair showed a way how to keep the key focus on a control using the "FocusObj" property, which is available in some key-related events. I haven't found this property outside these events. So, is the any way to prevent the loss of key focus without making the main VI modal? Thanks a lot, Guenther
  3. QUOTE (vugie @ Sep 2 2008, 12:42 PM) It is not probe related, the output array shows the same errors, even if I output a 3D array. That was the original design, when I first noticed this issue. Interesting that it works fine with LV8.2. Cheers, Guenther
  4. QUOTE (Ton @ Sep 2 2008, 11:17 AM) Hi Ton thanks for reproducing this bug. I was starting to worry about my copy of LV. The names don't make the difference. If I feed an unnamed cluster constant into the cluster input, the VI works. But that is just the reason for using this simple bundle function, that you don't have to use a cluster template. Looks more like a cluster initialization issue. Cheers, Guenther
  5. Hi guys, I just discovered a serious bug in the bundle function in LV 8.5.1. Looks like the output cluster doesn't match the input values. The VI should generate dummy data for testing the queued state machine in the main program. When the QSM started to act funny, I found that the generated data are wrong There are 3 nested loops, the output should contain a state for the QSM and the indices of the loops in a variant. The first 6 iterations of the inner loop are ok, but after that the value of the middle index is wrong in almost every other iteration. The boolean is just there to prevent constant folding, so I could actually watch what is going on in the loops. See the screenshot, where the bundle inputs are "1 1 0" while the cluster output reads "1 0 0". This is the first step that is wrong. After that, plenty more. Funny thing, if I wire the output cluster to the case structure or the loop frame, everthing works fine. Could someone try to reproduce this behavior to make sure it is not my copy of LV? In LV 8.6. I could not reproduce this bug, everything works as it should. Good reason to switch to LV 8.6. Cheers, Guenther Download File:post-3733-1220344764.vi[
  6. QUOTE (Tops @ Aug 7 2008, 02:14 PM) Yes, but only if you use the radio buttons from the "classic controls". Then you can make it transparent. Have fun, Guenther
  7. Hi Tops, you can disable individual radio buttons. On the front panel select the radio button, right mouse click -> create property node -> disable. This property node works on this selected radio button only. Of course you'll need to have separate property nodes for each radio button. Have fun, Guenther
  8. QUOTE (Ton @ Jul 17 2008, 08:21 PM) Yep, that was it. I wanted to prevent the cursor to be in the indicator field. Enabling the string indicator again makes the menu work. I do have a "mouse down" event that I use to select one of the items. To prevent the cursor from showing in the indicator I now redirected the key focus to a dummy control in this event. Is this the way to go or is there something more elegant? Thanks a lot! :worship: Cheers, Guenther
  9. Hi, I've got an array of clusters for which I configured a run time menu. Problem is, during program execution the run time menu is only shown if the right mouse click is done on the frame of the array or exactly between the elements, not if the mouse hovers over the array elements. I tried to configure a run-time menu for the array element or an element of the cluster but LV doesn't offer this option. How can I get the menu to appear regardless where on the array area the mouse click is done? Thanks in advance, Guenther EDIT: forgot to mention, this is LV 8.5.1
  10. Hi Osiris, for another project I coded a sub-VI that will give you the nearest data point for a given coordinate. So you make a mouseclick on the graph, close to the plot you're interested in, and the sub VI will give you X and Y value of the nearest data point plus the numer of the plot with this data point. This way you should be able to identify the strange graph. Sample is attached. Have fun, Guenther Download File:post-3733-1208445785.vi Download File:post-3733-1208445797.vi
  11. QUOTE(JFM @ Apr 11 2007, 03:46 PM) Yes, you're right. Backspace, delete, cursor movement etc. would have to be handled in different cases. The Scancode parameter gives you all necessary information to do that. But it's a bit more work. Did it once before I discovered the "Update while typing" property on a string control. I attach the program (LV8.20), one thing I didn't implement is when the user highlights some characters with the mouse and deletes them. But that could be added. Guenther http://forums.lavag.org/index.php?act=attach&type=post&id=5467''>http://forums.lavag.org/index.php?act=attach&type=post&id=5467'>http://forums.lavag.org/index.php?act=attach&type=post&id=5467
  12. The key down event is the correct one, but instead of reading the table value you should capture the key itself and add up the consecutive keystrokes in a string indicator. In this string indicator you'll always have the current value of the table cell. To reset the value you can use the "value change" event, this means the user hit enter or clicked into another cell. I only have LV8.20, so a screenshot will have to do. Good luck Guenther http://forums.lavag.org/index.php?act=attach&type=post&id=5466
  13. QUOTE(REM1 @ Apr 10 2007, 06:16 PM) Thanks, REM1 that's the answer I was hoping for Guenther
  14. Hu guys, is the run time engine of LV 8.2.1 different from the one if LV 8.20 or will programs compiled with LV 8.2.1 also run with the 8.20 RT engine? We have the LV8.20 RT engine already installed on quite a number of measurement PCs. Thanks, Guenther
  15. Hmm, your VI does pass a non-zero refnum, but also no effect on the position of the file dialog window. I'm attaching my VI, replacing the App.ParWinforDlgs property node with Mikkel's VI doesn't change anything. Maybe the mistake is at some other place? Thanks Guenther Download File:post-3733-1170936325.vi
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.