07-06-2012 06:14 AM
@Prabhakant Patil wrote:
Attached vi will give you more Idea to resolve your problem.
you can try this way also.
This is very similar to the vi posted by the O.P. He has to explain more then only we can approach in the right direction.
07-12-2012 12:42 AM
Hi Prabhakant Patil,
I am unable to open the VI, since I am using the older version compared to yours. Please can you save it in version 8.6 and upload again.
Regards,
Pramod M G
07-12-2012 12:58 AM
A good practice is to design your program such that your UI is separate from your processing. Using messgaing schemes such as queues, notifiers of user events to inform the UI to perform updates. Also, as suggested you can create subVIs and use the connector pane to pass data in and out of the subVI. You should really try to use subVIs within your program. If you don't you end up with the huge monolithic VIs that are difficult to understand, maintain or extend. Modular code is much easier to maintain and extend when you need to.
07-23-2012 04:28 AM
hi follow the step wat i did in this vi to use control as a indicator
07-24-2012 05:17 AM
The VIs below have the following attributes:
1. The control is outside the sub vi.
2. A reference of the control has been passed inside the subvi.
3. Property node has been used to access and write into the control, inside the sub vi.
Before you run the code, set the numeric control and then run the vi. The same control gets updated as a vi.
You could have also done this using local variables but there is a disadvantage:-
Each local variable is stored in a separate memory location, thus if the number of instances are large, a lot of memory will be wasted.