On 5/22/2007 5:55:52 PM, John H wrote:
>If instances is 0 (set via config menu)
>there is no delay whatsoever
>but to open multiple files in one
>instance I must apparently use the
>'Open with Vedit' right click option
>that is optionally added. While
>workable it's a chore compared to my
>normal approach which is to
>simply launch an edit session via my
>file manager using the
>keyboard or though command line.
>Setting the instances to 1 introduces
>the few second "Waiting for
>Disk" delay if opening a file to edit
>and running vedit at the same
>time. ie: vpe.exe something.txt
I can confirm that. I am using Windows XP Pro SP2. If Instance Control is set to 1, there is about 4 seconds delay whenever I open a file from Windows Explorer or from DOS prompt. If Instance Control is set to 0 or 2, there is no delay.
However, I can see very little reason to use instance control 1. In fact, 0 is more flexible. With setting 0, you can choose if you want to open the file in the same or different instance, e.g. by using drag and drop. In addition, drag and drop works with all files, not just with those that have been associated to Vedit.
If you drag a file into existing Vedit instance, the file is opened in that instance. If you drag the file into Vedit's desktop icon, a new instance is opened.
When using command line, you can control the instances with -s option.
The following test may reveal something about what is happening:
Set the instance control to 1.
While an instance of Vedit is open, drag a file onto Vedit desktop icon.
First, a new instance of Vedit is opened. Then there is few seconds delay with "Waiting for disk" message. Then the new instance is closed and the file is opened in the old instance.