link boolean buttons in different tab control

[J.DECHET]

In the same event, click on sign 'plus' on the top left of the window dedicated to edit event.

Then you can add an other value change detection on other button.

And don't forget to create associated local variable changes.

Perhaps, there is a good reason but it would be better to have only one set of buttons like said => outside of tabcontrol and position with arrows. (cf attached file)

In run mode, the effect produced by layers are not showed.

Message Edité par J.DECHET le 01-13-2010 02:41 PM

[EduU]

Well, I did it put all the 16 buttons only in two events, but now I have a problem

When I'm running the program, and I click in any button that I made that

the program stop responding... something happens that I can't do anything more in the program, I will attach the hole VI but I think you will not understand what is happening =x

Also I have to say, that this program wasn't made by me... I only did a couple of implements.

PS: This program is running at LV 7.1

Thanks

[J.DECHET]

You have to define a timeout for the event structure because by default it's '-1' that mean software is wait for an action before to continue. So dataflow blocks the rest of the while loop.

To be the simpliest with your framework, duplicate your case structure where you play with WaveformGraph properties and include it in the both event concerned by button changes.

Then applicate a Timeout to the event structure (the blue corner on the left top).

[EduU]

Well guys, after some tryes here

I make it putting the buttons out of the tab control and them moving it with the arrows...

it's a lot more easier!

With event works too, and was nice to learn it...

but I have some problems!

Thanks, and forget my last post!

Well, J.DECHET I think I understand what you are talking about, I have to change the place I play with the waveform graph, or the event structure? Could you attach a little image or a vi only to show me? It already work, but I want to learn doing with event structure too! Thanks

Message Edited by EduU on 01-13-2010 08:36 AM

[J.DECHET]

This is not really that I say in my previous post but, with event strcuture, you could write this:

Please, watch for timeout (here 100ms but to adapt with your needs) and watch for the constant 'Refresh' which drive the update of property or not. (That I wanted to say in the previous psot, was only to be the simpliest...).

But, I think you are winner to apply the method with only one set of button. 😉

[EduU]

Only one set of button, is the best for my application because makes the program running more fast!

But is nice to learn new stuffs! This can be usefull for me next time!

Now I understand what are you talking about!

Thanks for the help J.DECHET!