Topic: BAD PARAMETER: Column_End(65535) (1 of 3), Read 9 times
Conf: Error messages, Crashes
From: Pauli Lindgren
Date: Thursday, June 25, 2009 05:08 AM

When attempting to open a project, I got an error message
BAD PARAMETER: Column_End(65535)

I examined the .prj file, and indeed it contained a command
Column_End(65535)

The help does not say what is the largest allowed column value. I tested it and it seems that any value smaller than that, e.g. Column_End(65534), is accepted.

I wonder why 65535 is not accepted?

And I wonder why projsav.vdm had written such value in the .prj file? The file in question did not have a block defined. The other settings for that file were:

Block_Begin(-1)
Block_End(-1)
Column_Begin(1)
Column_End(65535)
Block_Mode(0)
Goto_Pos(0)

It has happened a few times that attempting to open a project causes an error, but the cause is not always the same.

--
Pauli

 

Topic: Re: BAD PARAMETER: Column_End(65535) (2 of 3), Read 9 times
Conf: Error messages, Crashes
From: Ted Green
Date: Monday, June 29, 2009 05:49 PM

At 05:08 AM 6/25/2009, you wrote:
>From: "Pauli Lindgren"
>
>When attempting to open a project, I got an error message
>BAD PARAMETER: Column_End(65535)
>
>I examined the .prj file, and indeed it contained a command
>Column_End(65535)
>
>The help does not say what is the largest allowed column value. I tested it and it seems that any value smaller than that, e.g. Column_End(65534), is accepted.
>
>I wonder why 65535 is not accepted?

The code was written to test for a value > 65535 and give an error; somehow there is an error in this code and it also errors on 65535. This is probably a vestige from much older versions that did not support greater column numbers. I probably can/should set a larger max, perhaps 100,000 or even 1,000,000.

>And I wonder why projsav.vdm had written such value in the .prj file? The file in question did not have a block defined. The other settings for that file were:

That is the more interesting question. I suspect that whatever value I set as the max value, that the new max value will show up in the .prg file.

>Block_Begin(-1)
>Block_End(-1)
>Column_Begin(1)
>Column_End(65535)
>Block_Mode(0)
>Goto_Pos(0)

The easiest fix would be to modify projsave.vdm to clear Column_Begin and Column_End when the markers are not set. I will also try to fix this in the code.

Ted.

 

Topic: Re: BAD PARAMETER: Column_End(65535) (3 of 3), Read 10 times
Conf: Error messages, Crashes
From: Ted Green
Date: Tuesday, June 30, 2009 05:50 PM

At 05:08 AM 6/25/2009, you wrote:
>From: "Pauli Lindgren"
>
>When attempting to open a project, I got an error message
>BAD PARAMETER: Column_End(65535)
>
>I examined the .prj file, and indeed it contained a command
>Column_End(65535)

OK, this is fixed, Column_End(65535) is now the max value as documented.
(I am not eager to increase the max value at this time.)

>And I wonder why projsav.vdm had written such value in the .prj file? The file in question did not have a block defined.

This could happen if you:
1. Pressed in Visual mode to highlight the entire file.
2. Performed Block_Begin(-1) in a macro to clear the block markers.

I "fixed" it so that Block_Begin(-1), which is the same as Block_Begin(CLEAR), now also clears Column_Begin and Column_End. However, as before, Block_Mode is not changed.

The fixed version is available again at:

http://www.vedit.com/download/vpw.exe

However, this time it is the VEDIT 6.15.3 release code updated to 6.15.4 with only these changes and the fix for Visual Studio.

VEDIT LOG (veditlog.txt)
---------

06/30/09 6.15.4
Minor - Starting line number can be e.g.: file.txt -l "123"
Technical Fix - Column_End(65535) gave error
Technical Fix - Block_Begin(CLEAR) now clears Column_Begin/End

-----

Next, I will work on the Date() command and ensure that all the supplied macros using Date() work correctly. Then I would like to release a new version which has all of the new macros, including Pauli's new Wildfile.

Ted.