Post by George on Nov 9, 2023 13:46:15 GMT -5
This thread will contain the latest Beta release following the V3.0.23313 production release.
I've created a unique Beta notice based on the Production version so that thread postings from a previous Beta version are not lost nor confused with comments on THIS release.
By Beta, I mean one that is, in my opinion, at least good enough to let other users try it out.
If you download and use one of these Betas, you should take precautions to be able to back off should it prove unstable.
I will try to provide, with every version, any information that may affect switching to the Beta release. When a new Beta completely replaces previous versions, the download link for the previous beta versions will be removed.
If you are running the latest production release, this Beta can simply be swapped in place of the production EXE.
Beta version: V3.0.24023 - This Beta should be the final one (barring any last minute problems reported)
CHANGES
* The number of UNDO levels option will be removed as a Profile Level item and will become an Options => General item. Automatic migration will be done and the setting will be made to the highest value currently used by any Profile.
* Correct several errors in handling UNDO/REDO commands. Errors were corrected in the commands CLIP, COPY, and in the main UNDO support itself.
* Correct an error in how internal data memory tables are expanded to prevent affecting special line storage (e.g. PROF lines).
* Correct MINLEN command. If the MINLEN value was increasing, it was failing to adjust the existing lines in the session.
* Correct PRESERVE handling when AUTOCAPS ON is also specified.
* Correct coding error in the DIFF support for removing comments from the data being compared.
* Correct error in parsing the -FILEOPEN file contents which could cause the contents to be ignored.
* Correct error in a FIND PREV type search. It was not finding strings which were ON the cursor line to the left of the cursor column.
* Add several enhanced Primitives to support TABS delimited column mode editing.
So, what is Column Mode Editing?
Well, it uses the TABS settings to organize the data into 'columns', and normal KB activity will honor column widths IF ASKED FOR. This means character typing in INS, OVR or DIN mode. The DEL, BS, DataDelete and DataBS will also adapt to the new mode.
How is it asked for? The new Primitive (TabBNDS). This will toggle this new mode. It will be displayed in the INS/OVR box of the Status Bar.
Other new associated Primitives are:
(TabShift) - Will take all data from the current cursor column and shift it right to the next 'column' boundary.
(TabRelease) - In INS mode, you may 'push' characters into the next column. When this would occur, the function will be stopped, with
an Audible/Visible Beep. (TabRelease) will temporarily stop column oriented activity for the current line.
Note: When typing in a column, if all further columns are blank, the check for overlowing a column will not be made, as no further data is impacted.
* Add several requested new MACRO functions:
Get_Arg_LRef_Count
Get_Arg_NumLit_Count
Get_Arg_Tag_Count
Get_Arg_TextLit_Count
Get_ANSI2SOURCE_Table$
Get_SOURCE2ANSI_Table$
For details of these functions, please see the Help Documentation
* Correct cursor positioning of 'N' inserted lines when there is actual data in the MASK line.
* Correct handling of the -F * operand in the INSTANCE command.
* Correct error in the SUBMIT handling of INCLUDED files.
* Correct error in the Line Command table which caused some line commands to reject / or \ modifiers.
* Update macro function Get_Profile$() to add the new MACLIB profile paramater.
* Correct parsing error when a Picture literal contains only a single *.
* Minor tweaks to INSTANCE support. If the -F filename has no path specified, the SPFLite HomeFolder will be added. An extra reset of the Most Recent Files list when the END operand was used, was removed. Some overlooked Doc. changes were completed.
* Small changes are:
(Backspace) bug was corrected
StatusBar display of the INS/OVR box improved
PROF display now formatted to match the COMMENTS command layout
In TabBNDS mode, the columns are marked with a dotted vertical line (like MARK)
If MARK is also active, TabBNDS mode will supercede it
* Added a new KB Primitive (Comments)
This will be of interest to source coders who place comments on the right side of the line.
Note: This will only function if you have HILITE AUTO ON and your Profile's AUTO file contains language comment definitions.
There is a new Profile Option and associated primary command - COMMENTS - with 4 operands.
e.g. COMMENTS 2 45 5 90
Which specifies:
1) The specific COMMENTx statement in the AUTO file describing the default comment format.
2) The desired starting column where comments are to begin.
3) An Increment to 2) when the code goes past 2) - The comment column is incremented by this amount till it is past the code
4) The desired column for closing comment identifier (e.g. the */ in a /* ... */ pair). This is only used when that style of comments is used.
So how does it work? Well, assign (Comments) to your desired key using KEYMAP.
When coding, if you press the key:
1) On a blank line: Your comment identifier will be entered at the comment column, and the cursor positioned after it. If a paired comment style, the closing comment identifier will also be inserted.
2) On a non-blank line with NO existing comments. Same as 1) but moved right if the code length requires it.
3) On a non-blank line WITH existing comments. The code and comments are separated and rejoined, placing the comments in your desired comment column. Again, comments are adjusted right if required by the code length. Note: Comments will also be 'dragged left' if they are beyong the desired comment column. For this case 3), the cursor is not moved. If a 'paired' comment ID, the closing comment will be retained in the specified column location whenever possible.
And as this adds new Profile variables, an updated CFGMaint is included. If you use CFGMaint, please download this as well.
Download:
For members SPFLite2.3.0.24023.exe (509 KB)
CFGMaint.exe (97.5 KB)
For non-members: SPFLite2.EXE
CFGMaint.EXE
For non-Members, comments should be emailed to : support@SPFLite.com
RE: Beta 3.0.23230 -- or whatever the version is --
Or better yet, become a member, as it says in the news, it costs nothing, you get to post on the forum, and you will not be bothered by any emails from us.
I've created a unique Beta notice based on the Production version so that thread postings from a previous Beta version are not lost nor confused with comments on THIS release.
By Beta, I mean one that is, in my opinion, at least good enough to let other users try it out.
If you download and use one of these Betas, you should take precautions to be able to back off should it prove unstable.
I will try to provide, with every version, any information that may affect switching to the Beta release. When a new Beta completely replaces previous versions, the download link for the previous beta versions will be removed.
If you are running the latest production release, this Beta can simply be swapped in place of the production EXE.
Beta version: V3.0.24023 - This Beta should be the final one (barring any last minute problems reported)
CHANGES
* The number of UNDO levels option will be removed as a Profile Level item and will become an Options => General item. Automatic migration will be done and the setting will be made to the highest value currently used by any Profile.
* Correct several errors in handling UNDO/REDO commands. Errors were corrected in the commands CLIP, COPY, and in the main UNDO support itself.
* Correct an error in how internal data memory tables are expanded to prevent affecting special line storage (e.g. PROF lines).
* Correct MINLEN command. If the MINLEN value was increasing, it was failing to adjust the existing lines in the session.
* Correct PRESERVE handling when AUTOCAPS ON is also specified.
* Correct coding error in the DIFF support for removing comments from the data being compared.
* Correct error in parsing the -FILEOPEN file contents which could cause the contents to be ignored.
* Correct error in a FIND PREV type search. It was not finding strings which were ON the cursor line to the left of the cursor column.
* Add several enhanced Primitives to support TABS delimited column mode editing.
So, what is Column Mode Editing?
Well, it uses the TABS settings to organize the data into 'columns', and normal KB activity will honor column widths IF ASKED FOR. This means character typing in INS, OVR or DIN mode. The DEL, BS, DataDelete and DataBS will also adapt to the new mode.
How is it asked for? The new Primitive (TabBNDS). This will toggle this new mode. It will be displayed in the INS/OVR box of the Status Bar.
Other new associated Primitives are:
(TabShift) - Will take all data from the current cursor column and shift it right to the next 'column' boundary.
(TabRelease) - In INS mode, you may 'push' characters into the next column. When this would occur, the function will be stopped, with
an Audible/Visible Beep. (TabRelease) will temporarily stop column oriented activity for the current line.
Note: When typing in a column, if all further columns are blank, the check for overlowing a column will not be made, as no further data is impacted.
* Add several requested new MACRO functions:
Get_Arg_LRef_Count
Get_Arg_NumLit_Count
Get_Arg_Tag_Count
Get_Arg_TextLit_Count
Get_ANSI2SOURCE_Table$
Get_SOURCE2ANSI_Table$
For details of these functions, please see the Help Documentation
* Correct cursor positioning of 'N' inserted lines when there is actual data in the MASK line.
* Correct handling of the -F * operand in the INSTANCE command.
* Correct error in the SUBMIT handling of INCLUDED files.
* Correct error in the Line Command table which caused some line commands to reject / or \ modifiers.
* Update macro function Get_Profile$() to add the new MACLIB profile paramater.
* Correct parsing error when a Picture literal contains only a single *.
* Minor tweaks to INSTANCE support. If the -F filename has no path specified, the SPFLite HomeFolder will be added. An extra reset of the Most Recent Files list when the END operand was used, was removed. Some overlooked Doc. changes were completed.
* Small changes are:
(Backspace) bug was corrected
StatusBar display of the INS/OVR box improved
PROF display now formatted to match the COMMENTS command layout
In TabBNDS mode, the columns are marked with a dotted vertical line (like MARK)
If MARK is also active, TabBNDS mode will supercede it
* Added a new KB Primitive (Comments)
This will be of interest to source coders who place comments on the right side of the line.
Note: This will only function if you have HILITE AUTO ON and your Profile's AUTO file contains language comment definitions.
There is a new Profile Option and associated primary command - COMMENTS - with 4 operands.
e.g. COMMENTS 2 45 5 90
Which specifies:
1) The specific COMMENTx statement in the AUTO file describing the default comment format.
2) The desired starting column where comments are to begin.
3) An Increment to 2) when the code goes past 2) - The comment column is incremented by this amount till it is past the code
4) The desired column for closing comment identifier (e.g. the */ in a /* ... */ pair). This is only used when that style of comments is used.
So how does it work? Well, assign (Comments) to your desired key using KEYMAP.
When coding, if you press the key:
1) On a blank line: Your comment identifier will be entered at the comment column, and the cursor positioned after it. If a paired comment style, the closing comment identifier will also be inserted.
2) On a non-blank line with NO existing comments. Same as 1) but moved right if the code length requires it.
3) On a non-blank line WITH existing comments. The code and comments are separated and rejoined, placing the comments in your desired comment column. Again, comments are adjusted right if required by the code length. Note: Comments will also be 'dragged left' if they are beyong the desired comment column. For this case 3), the cursor is not moved. If a 'paired' comment ID, the closing comment will be retained in the specified column location whenever possible.
And as this adds new Profile variables, an updated CFGMaint is included. If you use CFGMaint, please download this as well.
Download:
For members SPFLite2.3.0.24023.exe (509 KB)
CFGMaint.exe (97.5 KB)
For non-members: SPFLite2.EXE
CFGMaint.EXE
For non-Members, comments should be emailed to : support@SPFLite.com
RE: Beta 3.0.23230 -- or whatever the version is --
Or better yet, become a member, as it says in the news, it costs nothing, you get to post on the forum, and you will not be bothered by any emails from us.
