LabVIEW Idea Exchange

In my experience using and developing software it is typical save behavior to simply exit the dialog when a user clicks Cancel to a save operation.  This is reasonable if, when the file selection dialog is open, the user does not click anything (i.e. there is nothing in the file name field) and just clicks Cancel.  However, when the user has selected an existing file from the directory or there is a default file name in the file name field, I like to warn the user that the file was not saved when Cancel was clicked.

When invoking the Export Image method, if Always Overwrite is False, it will prompt the user if they are about to overwrite a file with dialog box that has an Ok and Cancel button.  This is great however there is no way to capture what the user clicked.

It would seem like good form to have a Canceled or Ok output just as in File Dialog express VI. 

This idea is a general request for NI to improve accessibility features for physically disabled users.  The background for the request is in this post.  In general the problem stems from LV's overreliance on precision mouse control.  I don't want to focus on a specific feature as I think the best solution will be a combination of features, possibly including the following:

* Better support for hotkey customizations.

* Ability to select and manipulate FP and BD elements with the keyboard.

* Block diagram zoom so users can zoom in when they need to target a small element, like a terminal or loop resize handle, or zoom out to navigate a large block diagram.

Here's an example of how I envision these features might be used to wire two nodes together:

1. While the keyboard is in "selection mode" I use the arrow keys to change which node is selected.  (i.e. Has the marching ants.) 

2. When I get to a sub vi with a terminal that needs to be connected I hit 'w' to enter "wiring mode."  This allows me to use the arrow keys to select the specific terminal I'm going to connect.  When that terminal is highlighted, I hit the spacebar to tag that terminal and go to the next step.

3. Using the same process as step 1, I highlight the node with the terminal I want to connect to and hit the spacebar, activating the ability to select a terminal.

4. I select the terminal using the arrow keys and hit the spacebar, and LV inserts the wire connecting the two terminals.

Again, this idea isn't requesting those features specifically (though they are all features I'd like to see) or claiming the workflow I described is the best solution.  They are just examples of one way to help disabled users.  The important thing is having a solution that works.