Set "Value Changed" as default event when defining new event cases

[BruceAmmons]

When I use an event structure, the case I use about 99% of the time is "Value Changed".  This is a bit of a pain since it is alphabetically at the bottom of the list, so I have to scroll down the list every time to select the event.

Since I suspect most people use this event the most, I would like it to be the default value when defining an event.  This way, I could just select the control and be on my way!

Bruce

[Henrik_Volkers]

My Kudos for you.

Additional  feature: Set the default case in the options or labview.ini

Henrik

[altenbach]

I agree, the scrolling to the end of the list is most tedious.

As an additional suggestion, I would prefer if the event configuration dialog would be resizeable (and it would remember it's size between runs!). At least that would help us avoid scrolling to get to the bottom of the event list. Monitors are getting bigger these days and there is no need to stick to tiny dialogs with fields the size of a postage stamp.

[Intaris]

In case Altenbach's idea of re-sizeable Event editor pane is appealing, please pop over HERE to drop some Kudos on a similar suggestion which was posted before I realised Altenbach had made this suggestion here.

Dealing with multiple suggestions on this otherwise great new forum is getting tedious already.....

Shane.

[jdunham]

I agree it would be a nice default, but you don't have to scroll.  Just tab into the event list and type "V" and it will be selected.

[Intaris]

@jdunham

Nice one.  Why have I never tried this?!

I think you just saved me a lot of work in future irrespective of whether NI changes anything about the Event editor...

Thanks

Shane

[SteveP]

Rolling the mouse wheel quickly gets you to the bottom of the event list, faster than having to grab the scrollbar with the mouse and dragging it.

[altenbach]

Steve, not everybody has a scroll wheel. For example my laptop where I do most of my programming doesn't.

Maybe the list should also have a divider line so things can remain sorted as before. above the divider line could be a few of the "most used" (adaptive!) or "recommended" (fixed!) events. (timeout, value change, ...).

For larger projects, I am also having problems finding the correct control in the list on the left. How about if a control terminal is inside an event case, we could just "right-click the erminal...add event" and have the event configuration window open with an new evet added and the control already selected.

How about if we could do "create value changed event for each control inside this event case" and then simply delete the ones we don't want?

[BruceAmmons]

Perhaps the option to create a "Value Change" event case for each unwired boolean control (or all unwired controls or all selected controls) with the control moved into the event case.  This would save me so much time when I create a bunch of new buttons, then have to create an event case for each button.  I would like to be able to copy an existing case that has items that I use in almost every case.

I like the idea of the most commonly used events at the top of the list.  I also look forward to trying the tab V route.

Bruce

[AristosQueue (NI)]

On Tuesday the next version of LabVIEW releases. LabVIEW 2009 includes... a refactored Edit Events dialog. Even though this idea exchange was not existant when LV 2009 started development, the importance of making "Value Changed" easily accessible was very important to everyone. Check out the new dialog and see if it resolves your concerns.