Jump to content

spaceboy

Members
  • Posts

    10
  • Joined

  • Last visited

    Never

Posts posted by spaceboy

  1. QUOTE(dsaunders @ Aug 22 2007, 09:04 PM)

    Starting in 8, there are VI Server Methods to return the row (and column for tables, trees, and multicolumn listboxes) from a mouse coordinate. Just capture the Mouse Down event on your listbox, then feed the reference and mouse coordinates to the method "Point to Row".

    Perfect! Thanks. :thumbup:

  2. hi,

    I'd like to be able to tell which row from a listbox was selected. This VI will run on a touch screen so the usual solution of using the double click event is not a good option. Instead I'd like the VI to tell which row the user chose after one press only (possibly adding a button if this isn't possible). What I have so far is attached.

    thanks,

    Jon.

  3. hi,

    I have a VI which is, at the moment, only a GUI. After initialization all of it is controlled by a single event structure which responds to button pushes. I'd like to add an event which will correspond to data received from a USB modem. I assume this can be done by dynamically registering events, but I have no idea how to start. Any ideas? Maybe dynamically registering events is not even the way to go?

    thanks,

    Jon.

  4. hi,

    I have a list with the format: serial #, coordinate 1, coordinate 2, coordinate 3, coordinate 4 (each coordinate is a ten character string). I'd like to write a VI that enables the user to add an entry to the list and delete from it.

    I thought the best way to do it would be with a MultiColumn Listbox displaying the list, where the user would be able to double-click an entry to remove it. Unfortunately, I can't get the GetDoubleClickedRow invoke node to work as I think it should. If I could get it to report on the line that was double-clicked I could easily remove it. Right now the only thing it does is give me -2. The code I have right now is attached.

    Any ideas?

  5. QUOTE(yen @ Jul 23 2007, 11:31 PM)

    It seems to work fine in 7.1, even after playing with the size of the while loops.

    I would guess this was some sort of bug which was fixed. Do you happen to have 6.0.2 which should have some bug fixes?

    By the way, in general, there are several things I would change about how you do this.

    For example:

    • You can move the entire password part into a dialog subVI and use a boolean output for the status of the password. The rest of the code is in the True case of a case structure which only runs if the password status is T.
      Also, I don't think there is any need to inform the user that the password is correct since they will realize that when they see their program is running.
    • You don't have any wait primitives in your while loops. This is very important because if you don't use them, LV will use all the CPU. This might even be the cause of your problem.
    • Using the Stop primitive to stop the VI is bad. Instead, you should do what I mentioned before.

    • This is just a demo. The real version has a sub-VI that verifies the password. Also, no dialog for a correct password :)
    • I tried inserting wait periods into the while loops. Didn't help. I might have to (reluctantly) switch to LV8.0.
    • To stop the while loops I could always have a master button that stops any while loop, but that would require a lot of local variables. Why do you think that's better than using Stop?

  6. QUOTE(yen @ Jul 23 2007, 09:15 PM)

    Another option is that the tab control is disabled (right click>>Advanced>>Enabled State), but I would agree the indicator option seems more likely.

    It's neither. This is very odd. I went back to work with an older version. At first I was able to switch between the tab control pages with no problem but after a bit of resizing of while loops it stopped working! Strange. The code is attached.

  7. hi,

    I'm using LabVIEW v6.0. I have a VI with a tab control. The user must be able to switch between the pages during runtime. For some reason I'm unable to do this. I can only switch when the VI is not running. Is this built in or am I overlooking something? Is there a way to change this behavior?

    thanks,

    Jon.

×
×
  • Create New...

Important Information

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