LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

Provide General Control Over Events Generated

Provide general on/off control of event types, such as mouse-over, so they can be disabled.  It is often very difficult to debug a callback by setting a break-point, then attempting to generate EVENT_COMMIT, EVENT_LEFT_CLICK or EVENT_RIGHT_CLICK.  The mouse over event is generated first, of course.

1 Comment

Typically, breakpoints are set in the callback under a case statement in a switch (or if statement) for a particular event that you're interested in debugging.


Another way to do it is by setting a condition on the breakpoint. From the edit breakpoint dialog, you can enter "event == EVENT_LEFT_CLICK_UP" in the Condition control.