Leaderboard

Hi Sjukheter The Event Structure has an Event Data Node on the left hand side which outputs data for a configured event (when that event occurs) and is very similar to the Unbundle By Name node. As the data returned is specific to an event it will change from event to event however, there are some standard or common data that is returned each time i.e. what you can see with an 'empty event structure' - to answer part of your question: Source - U32 value of the source of the event (LabVIEW UI, User Event etc...) Type - Enum of the type of event (Key Up, Key Down etc...) Time - U32 timestamp of when event occurred For Filter events you will also see a Filter Node on the right hand side and this is similar to a Bundle By Name Node. These can be more complicated especially if you have multiple events structures configured for the same Filter event. Put simply, you can override data just by wiring it into the node, or you can leave it and no change to the data will occur. You can even ignore the event so no notification occurs. I recommend you check out the LabVIEW help to find out more or do a quick search, here are a few links to get you started: Event Structure Components Notify and Filter Events Using Events in LabVIEW Also just by playing around with them and trying different stuff, you will pick up on it quick. Cheers -JG

I thought this: http://screencast.com/t/Th1N0wVFm0G ... I need less caffeine, I think. Joe Z.

This was precisely the reason I brought up this point yesterday - people are not aware of this issue and it's very easy to get bitten. The problem is that this declaration is done by name. There are legitimate reasons for wanting to change a class name without wanting to lose the history, so it would have been nicer if this was some sort of GUID and we would get the option to reset this GUID when renaming the class. Here are some examples for legitimate reasons: Code distribution (Daklu's case). Spelling mistakes (Oh, I forgot to type the F in "shift"?). Changes in the class subject (I first encountered this issue when The Device was nearing the end of the development and marketing gave it its final production name. "OK, I'll just rename the class", thought I). I would really like to avoid this. The class name is supposed to be descriptive and having different names will just create confusion (see case 3 above). For further reading, you may wish to have a look at the preserving class data document: http://zone.ni.com/devzone/cda/tut/p/id/6316