Event Structure Edit Window

I am using LabVIEW 2013. When I place an event structure on the BD and right clikc and 'Add Event Case' or 'Edit Events Handled by This Case' the Edit Events window does not pop up. An animation happens like it has opened up but the window is no where to be seen. If I try to click anywhere else in labview my computer just beeps at me like the window is open and I'm clicking outside of it. If I press Esc I can get back to my BD and continue as normal. Unfortunately I can't edit my events. Any ideas? Is there some option I may have changed that is making this happen?
Thank you for any help
Jesse Zamora
P.S. This is happening in a VI I started this morning and it also happens in a new VI.
Solved!
Go to Solution.

Close LabVIEW
Look in LabVIEW.ini for "EditEventsDlgSize="
delete the line.
you should have much joy. (this appears to be a known issue)
Jeff

Similar Messages

Can event structure detect window minimized

Can the (LV 8.5.1) event structure detect when a window is being minimized?
Solved!
Go to Solution.

Yes, you can!
The event 'Panel Resize' is the triggered event:
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

How do I access indicators in other windows of an event structure?

Let's say I have an indicator in 'case 1' called ON/OFF. How do I get the status or value of ON/OFF if I'm in case 2?
or - if this seems like a ridiculous question, am I missing some sort of important concept about how event structures work?
thanks
-z

Local variables are certainly an option. Property nodes are another, but both of which are probably the least recommended around here.
You can use shift registers, but then you have to be careful about where you update your indicator. Unless you've got a ton of these that need updating, that's the way I'd go.
Place your indicators outside the event structure and then just make sure you wire everything through every case (otherwise you'll end up with the default value of your indicator's type). See the image... I think it's more clear than my words can be.
Message Edited by Will.D on 10-31-2006 04:16 PM
Attachments:
Update.jpg ‏18 KB

Handling windows messages within an event structure

Hello all.
I've got an event driven VI which makes use of an event structure. I'd like my VI to be able to respond to some custom windows messages (i.e. WM_USER) sent from a separate process that listens on a telemetry card (sends a message when it receives data).
I have tried modifying the Windows Messaging Queue VI example provided by NI so that the VI will process windows messages during the timeout event in the event structure but this doesn't seem to work.
Any suggestions?
If labview events and windows messages don't mix then I guess I could do away with the event structure and go entirely with windows messages. This could be done by defining some custom messages that replace the labview events (e.g., W
M_STOPBUTTON_PRESSED = stop button, value changed event) and have the VI post these messages using PostMessage from User32.DLL and then catch these messages in the same manner as the NI Windows Messaging Queue VI.
My preference is to make use of the event structure if I can because its more inline with the labview methodology.
This is really interprocess communication question so if there are other ways of achieving the same result (sockets, named pipes, shared memory?) I'm keen to listen.
cheers,
Novak.

These 'sockets' sound interesting. What exactly are they? Could you direct
me to an example?
Thanks
Denis
"VI Guy" wrote in message
news:[email protected]..
> LabVIEW Events and Windows messages don't mix. To implement as such,
> you would have to do as you describe.
>
> Using sockets as an inter process communication scheme works great.
> And on a single machine, they dont leave the computer (i.e. no round
> trip on the network). Also, its cross platform compatable, not to
> mention it adds the possibility of being able to seperate your
> processes across several machines. Add to this that sockets are as
> easy to code as serial communication (with the benefit of "sleeping"
> waits instead
of "serial polling") and you get a solution fits many
> applications and needs.
>
> Get the idea I am sold on sockets?
>
> Good luck.

Firing events from a Menu using Event Structure - all in the same Event Window?

I have an ap where I have three menus, and several selections from
those three menus. I'm trying to keep everything within the Event
Structure, but it seems that ALL of the events fired from the Menu must
be contained within one "frame" of the Event Structure, that being the
Menu Selection (user) Event. In other words, if I have 16 events that
can be fired from the menu, do I have to put them ALL in this one event
frame?
I can't seem to use a T/F indicator within the Menu Selection (user)
Event to access another Event. For example, within the Menu Selection
(user) Event, I placed a boolean named X and can turn it on with a menu
selection. Now, make a new Event Structure to look for X Value Change -
doesn't work.
Message Edited by Broken Arrow on 11-30-2005 10:24 AM
Richard

I use one event, Menu Selection (user). to trap all of my menu events. Use Item Path and / or Item Tag to figure out what menu item was selected then branch code based on selection. Wtih Booleans and menus you need to update the state of the boolean on the menu by setting it True or False. It doesn't automatically toggle like you would expect.
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
Attachments:
menuSelect.JPG ‏45 KB

Event Structure Freezes Vi After Capturing The First Event

My Event structure catches the first instance of my button press but then it freezes my Vi. The reason is because of the while loop but I need the while loop to constantly read from a serial port and send data to a serial port. The vi included is stripped down to be just a while loop that does nothing. I have also tryed putting the event structure in the while loop, but the same thing is happening.
Any ideas?
Thanks,
Cason Clagg
SwRI
LabView 7.1, Windows XP

Also, put the button inside the event structure where it is acted upon, from LV help (suggest you read the entire events section of help):
When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control.
Refer to the Handling a Latched Stop Boolean Control in an Event Structure caveat for information about how to handle a latched Boolean control.
When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control.
Refer to the Handling a Latched Stop Boolean Control in an Event Structure caveat for information about how to handle a latched Boolean control.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Change the condition in event structures

Hi all,
I am a student, currently doing a project. I'm very new to labview and I don't really know much of the function in labview. Anyway, I have this timer made using event structure if I'm not mistaken (I downloaded this timer from one of the post in this forum). This timer will start at 0s, count to 20s, then stop. So what can I do to change the end time of this timer?? Let's say stop at 50s??
Attached is the program. Kindly please explain to me or modify the program and attached back as a reply. I've been trying to figure it out from the help function, but still don't understand.
Thank you very much in advance!!!
Solved!
Go to Solution.
Attachments:
TIMER s.vi ‏13 KB

Hi,
Thanks for your inquiry. The VI attached uses a couple of programming structures: While loop, Event structure and Case structure. What you would have to change is actually the case structure. Before we go to that, let us go through the different structures. Open up the block diagram by going to the Menu bar of the front panel and navigate to Window->Open block diagram.
The While loop is like a Do Loop in text based programming. It will execute until a condition is met. From the attached VI, it stops running when you click the exit button.
The Event structure is a structure which consists of subdiagrams. The structure responds to interactions with front panel objects. For example, if you click the start or stop button in the front panel, the event structure will switch to a case which corresponds to this interation. In the attached VI, the case, which corresponds to intreaction with the start or stop button, is called "Start", "Stop": Value Change. Each case will contain an event-handling routine.
Case structures are like switch statements in text programming. Take a look at the "Start", "Stop": Value Change event. It contains a routine which consists of a case structure. The case structure responds to the input terminal called Start (which is actually the start button on the front panel). The case structure switches between cases according to this input. To view the different cases just cycle through the case structure by clicking the left and right buttons. There are only two cases: True or False as the input is a boolean.
Now lets take a look at the VI. Take a look at the "Timeout" case of the event structure. This is where the modification needs to be made. Modify the case structure by editing the cases. Change the numbers in case structures: ..20000 to ..50000 and 20001.. to 50001.. This should do the trick.
Regards,
Alan Bong

Event structure problem

HI!
I am a Labview Newbie and i have some problems with my event structure in the program "Biegelinie"! I get always failure from the event-structure in the failure-list!
Could somebody help me???
best regards,
Peter
Labview 7.1 on Windows 2000
Attachments:
program.zip ‏134 KB

For a less complicated system, you can achieve nearly the same
functionality without using an event structure. Simply poll the
state of the booleans you require and feed them into case
structures. By placing these case structures and the polling into
a loop with a "wait until ms multiple" set to around 50 or 100ms, the
responsiveness of the code should be high enough without bogging the
processor down with the polling.
If you want have a look at the example VI I've attached.
Hope this helps
Shane.
PS Are you sure the document linked below is relevant for you? It
states that the event handler isn't in the base 6.1 version of LabVIEW,
but your sig says you're using 7.1........
Message Edited by shoneill on 07-25-2005 11:30 AM
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
Attachments:
Polling boolean.vi ‏23 KB

Labview 2013 cannot use event structure

Event structure can be added into the back panel, however when i add event case or try to edit the default event case, the program is crask and cannot response to my mouse.
when i launch windows task manager, it present " running" properly.
However this program run properly at my another computer with sample Win7 OS.
Can anyone tell me what the problem is?

Aaron1978 wrote:
sir, this issue does not related to code, even i create new empty VI, the event structure cannot work properly, i cannot add new event or edit the default even!
However, i installed the same eval version into my another computer, this event structure can work properly, both computers use same Win 7 OS.
Okay in that case I would recommend a repair install of LabVIEW.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Stop execution of a loop in an event structure

I tried searching the forums to avoid posting a duplicate, but most I could not open most of the vi's as they were higher version.
I put in a dummy while loop in an event structire i intend to use. Once I start executing the while loop, I am not able to stop it using a control for some reason from the fornt panel control.
I am not able to change the vale of the Stop control at all. I tried creating a seperate event for STOP, and I still could not stop the program when the While loop was executing.
I imagine I am missing something really small. I would appreciate your feedback on this.
Thanks,
Nevil
Solved!
Go to Solution.
Attachments:
FrontPanel.vi ‏34 KB

Right click on the event structure and choose "Edit Events" for the case that is giving you trouble.
Be sure the checkbox to lock the front panel is unchecked.
I suspect yours is checked, so your front panel is locked out until the event completes, thus you can never stop your loop.

How to use an Event Structure responding to an image control that belongs to a parent VI.

Hi
I am loading a subpanel vi by pressing a button located in the user interface of the main vi which also contains an image display. Subpanel vi opens up on the side and doesn't hide the image display of the main vi. Subpanel vi contains an event structure that needs to respond to user clicking on the image display of main vi.
Since the bug that occured while creating an image reference control isn't fixed, I am passing the main vi pane reference onto the subpanel vi. From that point I've tried to edit event structure and have it respond to the image control/pane that belongs to main vi but I don't know how.
Any help would be appreciated.
Thanks

Post a screenshot of your subVI code where you register the events.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Using Event Structures with Array of Clusters

Using LabVIEW 8.5
Hi all,
I'm trying to convert an existing application to one that can be used
through a touch screen. I updated the UI and added an event structure
to listen for mouse ups on controls that require a HMI keyboard or
numpad to show up. Although I've been programming for a while, I'm new
to LabVIEW and am struggling with a problem:
Is there any way to have an event case listen to an event within
arrays? I've seen a few examples on the forums, but they all start with
breaking up the arrays into individual variables. Using the variables,
they build arrays. This seems pretty tedious, and I'm pretty sure I
can't apply it to one of my arrays. Essentially, I just want to know
which cluster in which array the user has clicked on, so I can open the
HMI keyboard or numpad and send the text to that cluster. In my watered down app (Array of Clusters.vi), I've put 3 arrays of clusters and a few stand-alone controls to give you guys an idea of what I'm taking about.
BTW, I'm using the HMI Keyboard and Numpad built by the Beta Community (http://decibel.ni.com/content/docs/DOC-1062) and modified it to add a "Clear" button to the keyboard and numpad. Please let me know if I implemented this in the best way.
Thanks for the help,
Kunal
Message Edited by bhatiak on 08-04-2008 03:55 PM
Attachments:
Array of Clusters4.llb ‏274 KB

My old tic tac toe example shows how to determine which square of a 2D array has been clicked.
http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=247044#M247044
You probably can adapt some of it for the arrays on the right. If the array can be scrolled, you also need to account for the "indexvals" offset.
The Layers controls is easiest, because you only show one element. Just read the "index vals" property to get the array element and parse the coordinates to get the cluster element.
btw: the small while loop on the right serves no purpose at all and acts just as a CPU burner. You can delete it without any change in functionality. Is there anything else to it?
LabVIEW Champion . Do more with less code and in less time .

How to stop While Loop in Event Structure with same button?

Hello,
I have a problem. I want to use one control to activate an event in a event structure, and the same control to terminate a while loop in that event.
It is possible to use 2 controls to do this, but I need it to be only one.
Thank you
Message Edited by Heinen on 02-19-2009 06:16 AM
Message Edited by Heinen on 02-19-2009 06:20 AM
The Enrichment Center is required to remind you that you will be baked, and then there will be cake.
Solved!
Go to Solution.

Hello,
I have a bit different problem.
I have a tab control, with several buttons on different pages.
In the current situation, we can talk about two pages, where one page ("Settings") in the Image, has a START and EXIT button, while second page ("Wait") has an EXIT button.
In a while loop, I have event structure, which handles events of the START and EXIT buttons of the Settings page. This is fine. But I also want to control the Exit button of the Wait page.
The control works like this:
When I click on Start in the Settings page, the front panel shows Wait page and attempts to connect to a datasocket server on the remote computer. If the user wants to stop this process, he can click on Exit on Wait page too. But, this doesn't give any immediate effect. On the even of Start button, the front panel is not locked, so the user can actually click the Exit button on the next page when it's visible. But it's of no immediate effect. Means, what the LabVIEW does is, finishes the execution of event in Start button's click, and while this executes, it doesn't consider the Exit button's refreshed value (shown in Red circle in the block diagram).
Simple question: Is there any way to check the updated (latest/live) value of a control during some event's execution? Or if I write an Event "Value Changed" for the Exit button and pass it to some variable. Is it the only solution?
Thanks ahead.
Vaibhav
Attachments:
terminate event_diagram.jpg ‏200 KB
terminate event_front_1.jpg ‏63 KB
terminate event_front_2.jpg ‏63 KB

Need to revert to previous non-icloud ical -- new Delete button in Edit window is a problem.

Does anyone know how to revert to a previous version of iCal?
The new 5.0.3 iCal update is giving me huge problems.
When editing events, sometimes a delete button appears in the bottom right corner of the Edit window. Reflexivly, I click the small button, which I don't realize until it's too late, had changed to a 'delete' button. The new event is gone; there is no undo available.
I lost several appointments until I realized what was happening. I have lost new appointment with all the details I'd entered since.
Realize that this is just an opinion, but it is unfathomable why the UI change after all this time. There seems to be no good reason for having a delete button sometimes appear on the edit window.
Another change that is driving me crazy is that the Edit window open and close shortcuts were both command-E. Now, the commands have changed.
Please help! This is driving me crazy. I use iCal dozens of times a day. The new changes are not making me happy.
Thanks.

Hi flamechaser,
Welcome to the HP Forums.
I see that you are having some issue's when attempting to scan to the computer.
I do have a few suggestions we can try in the attempt to troubleshoot this issue.
First off, please make sure that you have the printer power cable connected directly to a wall outlet and not a power bar/strip. Here is a document that uses a LaserJet printer as an example but it is meant for HP products in general. Please click on the following link that explains the Issues when Connected to an Uninterruptible Power Supply/Power Strip/Surge Protector.
I have also located a document that deals with communication issues between the computer and printer. Please click on the following link for a Windows Error: 'No HP devices have been detected. HP Solution Center will now close.'
If the troubleshooting does not help resolve your issue, I would then suggest calling HP's Technical Support to see about further options for you. If you are calling within North America, the number is 1-800-474-6836 and for all other regions, click here: click here.
Thanks for your time.
Cheers,
Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
W a t e r b o y 71
I work on behalf of HP

Maximum size of an event structure

I have just a short question about the maximum size of a event structure, and did not found it yet in the forum.
I have an event case with 35 event cases. How many are allowed, what is recommended and is there a huge loss of performance by seizing it up?
Thx for answer

As far as run-time performance is concerned, the number of event cases in an event structure should have no noticeable effect. Worst-case scenario, when the event structure is woken up due to an event occuring in the system, it does a linear search through the list of event cases to figure out which event-handling diagram matches the event that it pulled off the queue. These tests are pretty quick (3-4 comparisons per event-handling diagram) so I can't imagine it really would have any effect on performance. However, this does tell you that if you want to squeeze every ounce of performance out of your event-handling code, make sure the most frequently run event-handling diagram is the first one in the list.
The only performance issue I could see arising is what Damien mentioned - at edit time, it may take longer to make edits to the event structure (eg adding new event cases, changing the events a given diagram is associated with). I don't know that I've seen any issues because of this (the largest application I've written has an event structure 40 different event-handling cases), but I think this is where any potential performance issues reside.
Hope this helps.
J
Jason King
LabVIEW R&D
National Instruments

Event Structure Edit Window

Similar Messages

Maybe you are looking for