Topic: Strange behavior when opening new file (1 of 8), Read 25 times
Conf: Startup, File Open, Exit
From: Larry Kirkpatrick
Date: Wednesday, February 23, 2005 11:17 AM

First of all, thank you for such a wonderful program. It just keeps getting better with each new release.

I frequently launch vpw from the command prompt. I have it setup to use the same instance when doing so. Here's my scenario: Open 2 or more existing files in vpw. Open a new file (one that doesn't already exist) in vpw from the command line. The newfile "tab" displays whatever was in the previous "tab" being shown before opening the new file. Changing to any other tab displays the same file info. As soon as you hit a key the correct text is displayed and all tabs show the correct text. The first time or two this happened, it really threw me, as I thought I had corrupted my opened files! It usually happens to me when I go to add another file and type in the name wrong on the command line.

I am using version 6.13.1 of vpw and WinXP Pro, SP2. Thanks.
Larry

 


Topic: Re: Strange behavior when opening new file (2 of 8), Read 25 times
Conf: Startup, File Open, Exit
From: Christian Ziemski
Date: Wednesday, February 23, 2005 12:39 PM

Larry:

I don't have a solution but would like to add some infos.


On Wed, 23 Feb 2005 11:17:00 -0500, Larry Kirkpatrick wrote:

>I frequently launch vpw from the command prompt. I have it setup
>to use the same instance when doing so.

Instance control = 1

>Here's my scenario: Open 2 or more existing files in vpw.
>Open a new file (one that doesn't already exist) in vpw from the
>command line. The newfile "tab" displays whatever was in the previous
>"tab" being shown before opening the new file.

Confirmed.

>Changing to any other tab displays the same [wrong] file info.

When switching via mouse, confirmed.

>As soon as you hit a key the correct text is displayed and all
>tabs show the correct text.

It seems to be not only an "Missing Update()" bug.

For example: After having opened the new file and confirmed the
"New file" dialog box I have choosen {Search, Search} via mouse and
immediately canceled the search dialog via mouse.
Then VEDIT jumps into command mode.

Christian

 


Topic: Re: Strange behavior when opening new file (3 of 8), Read 22 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Friday, March 18, 2005 05:33 PM

At 12:40 PM 2/23/2005, you wrote:
>>Here's my scenario: Open 2 or more existing files in vpw.
>>Open a new file (one that doesn't already exist) in vpw from the
>>command line. The newfile "tab" displays whatever was in the previous
>>"tab" being shown before opening the new file.
>
>For example: After having opened the new file and confirmed the
>"New file" dialog box I have choosen {Search, Search} via mouse and
>immediately canceled the search dialog via mouse.
>Then VEDIT jumps into command mode.

I can replicate the problem.
Removing the "New file" dialog box seems to fix the problem. (Evidently, this dialog box somehow clears some "update-needed" flags.

Since the "New file" dialog box is a very old vestige, I see no reason
to keep it any way. The status line lists "New file", same as when you
open a non-existent file in VEDIT.

I was thinking of changing such status line messages to a red color.

If people agree to dump the "New file" dialog box, this is a simple fix. Otherwise Tom will need a few hours to figure this one out.

Ted.

 


Topic: Re: Strange behavior when opening new file (4 of 8), Read 25 times
Conf: Startup, File Open, Exit
From: Ian Binnie
Date: Friday, March 18, 2005 07:06 PM

On 3/18/2005 5:33:01 PM, Ted Green wrote:
>>If people agree to dump the
>"New file" dialog box, this is
>a simple fix. Otherwise Tom
>will need a few hours to
>figure this one out.
>
>Ted.

Since I never create new files from the command line I can see no problems. I had some difficulty actually trying this, as I normally start Vedit from ZTreeWin.

I create new files from within Vedit (or a macro).

The one thing I would REALLY like is a macro command to set the default directory the file is created in.

 


Topic: Re: Strange behavior when opening new file (5 of 8), Read 27 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Friday, March 18, 2005 07:10 PM

At 07:06 PM 3/18/2005, you wrote:
>The one thing I would REALLY like is a macro command to set the default directory the file is created in.

Might the Chdir() command do what you want?

Ted.

 


Topic: Re: Strange behavior when opening new file (6 of 8), Read 29 times
Conf: Startup, File Open, Exit
From: Ian Binnie
Date: Friday, March 18, 2005 11:47 PM

On 3/18/2005 7:10:50 PM, Ted Green wrote:
>At 07:06 PM 3/18/2005, you
>wrote:
>>The one thing I would REALLY like is a macro command to set the default directory the file is created in.
>
>Might the Chdir() command do
>what you want?

Thanks Ted.
One of the problems with Vedit is finding how to do things.
I now have Chdir("D:\progs\Vedit\text") etc in my Tools menu. This is more elegant than the way I used to do it.

This allows me to "Save" files to the new default directory.

"Save as" does not change directory. Is this intended?

 


Topic: Re: Strange behavior when opening new file (7 of 8), Read 31 times
Conf: Startup, File Open, Exit
From: Ted Green
Date: Saturday, March 19, 2005 12:06 AM

At 11:48 PM 3/18/2005, you wrote:
>"Save as" does not change directory. Is this intended?

Look at the file selection dialog boxes carefully; some have a checkbox:

[ ] Change directory

:-))

Ted.

 


Topic: Re: Strange behavior when opening new file (8 of 8), Read 35 times
Conf: Startup, File Open, Exit
From: Ian Binnie
Date: Saturday, March 19, 2005 03:40 AM

On 3/19/2005 12:06:23 AM, Ted Green wrote:
>At 11:48 PM 3/18/2005, you
>wrote:
>>"Save as" does not change directory. Is this intended?
>
>Look at the file selection
>dialog boxes carefully; some
>have a checkbox:
>
> [ ] Change directory
>
>:-))
>
>Ted.

I should have been more explicit.

Save uses the default directory as its starting point.
Save as does not.

This may make sense with an existing file, but not with a new file.