LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
falkpl

Optional "confirm" on icon editor cancel

Status: Declined

National Instruments will not be implementing this idea.

Maybe this is a personal problem but I do this all the time and It frustrates me every time.

Edit an icon go to hit OK a little too fast and catch the cancel by mistake, all my hard work GONE.  Yes this is only a loss of a few minutes but time is money.  Do this 1 out of 50 times I edit an icon, ant it happens a few times a week. 

 

Can we move the cancel button away from the OK or can we add an optional confirm on unsaved changes to the icon so I dont loose my work every time I make this mistake.

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
11 Comments
JackDunaway
Trusted Enthusiast
Alternatively, automatically accept the changes made! Just keep changes in the Undo buffer for the Icon Editor, in case you want to come back and change your mind. For some reason, I instinctively make my edits and head straight for the [x] in the title bar, assuming that it will ask me "Do you want to save your changes?", and I'll hit Spacebar and be done. I've thrown away about a dozen icon edits since LV2009.
JackDunaway
Trusted Enthusiast
And it's not just a personal problem if we are all doing it. There's something wrong and nonintuitive about the UI of the Icon Editor if we all instinctively, inadvertently try to nuke our hard work. (And if no one else is making these silly errors, I guess falkpl and I are just losing our minds).
PJM_Labview
Active Participant

I also think that there are un-intuitive things in the new IE, and this is why I made a customized version that reorganized the UI in a more intuitive way [at least I think so] (it is freely available to download if anybody is interested).

I don't quite understand how the use case (closing through the [x]) is different from the previous version. The previous Icon Editor did not ask you for confirmation if you do that, so the new Icon Editor is not any less intuitive in that regards.

Additionnaly, I don't think that an icon change was undoable in previous version either (although I had wish it could have been for a long time and I think that this is a great idea that deserve a separate entry).

 

In conclusion, I am not a proponent of adding a confirmation dialog (unless I have an option somewhere to never see it).



  


vipm.io | jki.net

ThSa
Active Participant

The funny part is, we had a confirmation dialog at some point in the new IE. The thoughts of some folks were, it is not a 'document', therefore a confirmation dialog is not appropriate.

It is the same with the event-structure or property dialogs in general -> no dialog asks u if you really want to quit and discard all changes.

 

Why should be the IE behavior different than the event-structure dialog?

falkpl
Trusted Enthusiast

Yes the confirm would have to be optional since it could become anoying, I prefer for the confirm only to show up if changea are made.  I also prefer the cancel to be moved away from the OK, the 1 mm tolerance is just not enough for me.  Eliminating the Cancle and moving it to the X on the title bay would also work for me.

Just tired of loosing work

 

 

Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
Neil.Pate
Active Participant

I would vote against a "Are you sure?" Dialog. 

 

Soon every single action will require confirmation dialogue and moving the mouse will pop up a "Are you sure?" dialogue. Please no...

 

To me a nice trade off would be to allow the cancel operation to be undone.

 

If the dialogue had an option where you could get it not to show, after a few popups you would be sick of it and hide it, and then when you really needed it it would not appear.

Lavezza
Active Participant
I think the problem is the [X] has different meanings in different contexts. In some places it means cancel and in other places it means 'close with warning'. I would prefer the [X] just went away in the IE. OK and Cancel buttons are unambiguous.
RavensFan
Knight of NI

Here is where I run into a problem with the current behavior.

 

I start clicking into a tool such as Add Text.  I start typing and change my mind about what I just typed.  My natural instinct is to hit the Escape Key to back out of that tool.

 

Well, the Escape key is inherently linked to the X button of the icon editor window.  Rather than just backing out of the tool, with one quick key press, I wind up completely backing out of the icon editor losing any other changes I just made.

 

I think I would be better off just having the icon editor X disabled and rely on the OK button to get out with Save or the Cancel button to get out without saving.

 

Actually in some VI's I write, I intentionally need to disable the X button so that a user doesn't accidentally close a VI, or else wire in confirmation dialogs to the Panel Close? event.

 

On another note, why does the File / Close Menu choice just close the Icon Editor without asking you to save it?  (I have never used the menu for that before, but I just tried it.)  A File / Close menu choice is a very common menu choice in any type of "document" program such as MS Word, Excel, AutoCAD, .....  Those programs always prompt you to save changes if you do a File / Close.  So saying the Icon Editor doesn't need a confirmation because it is a dialog and not a document type of program just doesn't hold water when the window contains a "File" menu.

Message Edited by Ravens Fan on 09-10-2009 02:26 PM
AristosQueue (NI)
NI Employee (retired)

There is an update for the LV 2009 icon editor (posted Sept 14, 2009) available here:

http://decibel.ni.com/content/docs/DOC-6301

 

This update incorporates many suggestions that we got right off the bat from users and fixes a number of reported bugs.

 

An entire discussion forum exists for discussions about improving/extending the Icon Editor. It can be found here:

http://decibel.ni.com/content/groups/enhanced-icon-editor-2009

jacemdom
Active Participant

thsa wrote:

 

The thoughts of some folks were, it is not a 'document', therefore a confirmation dialog is not appropriate.


I believe a more appropriate question should be "Is there going to be more than one minute of work lost?" If yes than ask for confirmation "IF" changes occured.