event structure on base development license

[SeanJ]

Hello,

I've developed a GUI that uses the event structure on a machine with a full development license in order to enter a serial number.

I now wish to use the code on a machine that has a base development license. 

When I run the gui on the machine with the base development license, it functions fine except the string value where the serial number is entered does not update.

I am going to revert to using a timed while loop, however I am interested to know if this is expected behaviour.  My understanding was that I could run code developed on the full development system on the base development system.  Is this correct?

Thanks,

Sean

[altenbach]

I never used lv base, but my understanding is that events should continue to work (?). Could you build it into an application instead? Can you show us some code? I don't undrstand why a manual entry field need to update at all.

[JÞB]

The event structure should run on the target machine since the RTE is responsible for execution.  HOWEVER, the base compiler may not know what to do about compiling the code related to the event structure so if the code opens needing a save you might lose some functionallity.

Of couse, I've been wrong before and your code may be at fault.  lets take a peek

[Rhys - AE]

Hey Guys,

You should indeed be able to work with event structures in LabVIEW base; you just can't find them on the functions pallet or manipulate/edit and of the event cases.

I tested this out for you guys by developing a wee VI in LabVIEW 2010 SP1 Full, and then relicinsing my LabVIEW 2010 SP1 to Base. I restarted my PC to make sure all the NI services had restarted, and then tested my VI out. Everything worked just as before.

I echo the other guys in asking; lets have a look at your code.

Thanks man.

[SeanJ]

Hi Guys,

Sorry about the delay, instead of using the event structure I reverted to a while loop with a delay.

I couldn't recreate the error, however I've atatched two vi's that I think resemble the issue.

In the good vi the indicator is updated, in the bad vi it is not. 

I think this may have been the issue although I recall testing on the development saving the vi on the network and then having the issue. 

Apologies for the confusion, it seems fine now.

Sean

[smercurio_fc · Accepted solution]

The reason why the "bad" doesn't work is because you are trapping the Boolean MouseDown event. That's the event that gets fired first. If you typed something in the serial number control and then went to click the button the MouseDown event gets fired. However, the serial number control has not been updated in terms of registering a new value. Hence, when the MouseDown event is handled, as far as the application knows, the control is still empty. If you type something into the string control, and then click somewhere else on the panel, then the control's value is updated. If you then click on the Boolean you will see that the "bad" works. In essence, trapping the MouseDown on the Boolean prevents LabVIEW from updating the control's value since the program immediately ends.