Written by ScottG489 the 14 Feb 09 at 04:45.

A perfect example of this is an image file. Images are usually both edited and viewed about the same amount. So, for example, if you double click on the file to open it, it could normally open to be viewed in a program of your choice, but if you held shift (or some other modifier key) it would open with the editor of your choice.

A good reason for this is because most of the time programs used to edit files take a long time to open. Of course you can always just right click and choose a program to open the file with. However, an implementation to designate the two most common ways to open files (viewing and editing) would be very helpful.

A perfect example of this is an image file. Images are usually both edited and viewed about the same amount. So, for example, if you double click on the file to open it, it could normally open to be viewed in a program of your choice, but if you held shift (or some other modifier key) it would open with the editor of your choice. A good reason for this is because most of the time programs used to edit files take a long time to open. Of course you can always just right click and choose a program to open the file with. However, an implementation to designate the two most common ways to open files (viewing and editing) would be very helpful.

Written by sparky11 the 18 Feb 09 at 04:11.

Perhaps you should add an icon to the cursor when hovering and holding shift with a pencil, showing that clicking it would open the editor. Also, you could have a notification in the status bar informing the user of this feature. After all, a feature is useless if no one can use it, correct?

Perhaps you should add an icon to the cursor when hovering and holding shift with a pencil, showing that clicking it would open the editor. Also, you could have a notification in the status bar informing the user of this feature. After all, a feature is useless if no one can use it, correct?