Topic: VEDIT 6.21.1 release candidate (1 of 32), Read 81 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Thursday, July 14, 2011 09:11 PM

A VEDIT version 6.21 release candidate is available at:

    www..../download/beta/vpa-prod.exe

Here are the changes since 6.20.1:

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

07/14/11  6.21.1
        Much, much faster (30x) Scribe spelling checker
        {MISC, Box drawing mode} now works for all fonts (ANSI and OEM)
        Easier integration with Windows, Explorer and IE
        Improved {MISC, Save and run programs} with useful defaults
        New {HELP, Dashboard info} helps to debug install/config problems
        New {FILE, Projects, Quit project}
        New {FILE, Projects, Set project directory} sets CURRENT_PROJ_DIR
        New {MISC, Execute current buffer} helps with macro development
        Improved USB installation support, including saving Projects on USB
        Minor improvements to compiler support
        Minor improvements to flat-csv.vdm and csv-flat.vdm macros
        Minor improvements to many other supplied macros
        Minor - Rename {CONFIG, Associate file types} to "Windows integration"
        Syntax directory moved from HOME to USER_HOME
        Technical - New Buf_Switch(r,VALUE,size) option
        Technical - New Reg_Prep() command to optimize macros for speed
        Technical - New Is_Font_OEM internal value
        Technical - New Command_Check("command")
        Technical - New string value CURRENT_PROJ_DIR for project support
        Technical - New string values VEDIT_DRIVE, HOME_DRIVE, USER_DRIVE
        Fix - New vedit.ini to reduce chance of 1st time crash in Win7
        Fix - Scribe didn't work under Vista/Win7
        Fix - Runshell.vdm didn't work under Vista/Win7
        Fix - VEDIT PDF manuals had minor problem under Vista/Win7
        Fix - Startup.vdm had wrong default location for ustartup.vdm
        Fix - Uninstall would break out if vedit/old directory found
        Fix - USB installation didn't work on different drive letter
        Fix - {GOTO, Matching ()} could get confused or possibly hang

===========

While it doesn't address every recent (and not so recent) suggestion, I think it does cover most of the
issues that have recently been discussed on WebBoard. Hopefully it has all of latest versions of the
supplied macros.

Today I finished updating the runshell.vdm macro which implements the {MISC, Save and run programs} sub-menu.
First, I had to save the commands into (USER_CFG)\runshell.ini (instead of into the runshell.vdm macro).
I then also implemented a new "&&" option and pre-loaded slots 1- 3 with useful commands.
I thoroughly updated the help system for this.

I finally figured out why VEDIT was crashing on some Win7 installations. It appears that when the very first
file opened in a new installation of VEDIT is added to the "Recent files" list in the File Selector, it is
exposing a bug which crashes on some Win7 systems. Since it doesn't crash on any of our Win7 computers, and
retired programmer Tom Burt wrote this complex code, I am hard pressed to find/fix the bug. Therefore, the
installation now adds "whatsnew.txt" as the initial "Recent file" in vedit.ini so that this list is never
empty. Sure, it just a work-around and I do hope to find/fix the "empty" case bug soon.

Please let me know if there are any serious problems in this release candidate. If not, I plan to release it
early next week.

Thank you.

Ted.

 


Topic: VEDIT 6.21.1 release candidate (2 of 32), Read 49 times
Conf: VEDIT Beta Test
From: Pauli Lindgren
Date: Sunday, July 17, 2011 10:19 AM

On 7/14/2011 9:11:37 PM, Ted Green wrote:
>
> Today I finished updating the
> runshell.vdm macro which
> implements the {MISC, Save and
> run programs} sub-menu.
> First, I had to save the
> commands into
> (USER_CFG)\runshell.ini
> (instead of into the
> runshell.vdm macro).
> I then also implemented a new
> "&&" option and pre-loaded
> slots 1- 3 with useful
> commands.

The text in the dialog box says '&' instead of '&&'.

The default command in slot 2 is "dir > out"
I think it should be "dir > vout".

By the way, where is this file vout stored?

I rarely use this "Save and run programs" function.
It would be more useful if you could specify the menu text for each sub-menu item.
The dialog box could have another text field for entering the menu text.

BTW, I recall many years ago there were plans to make the whole Vedit menu system configurable.

--
Pauli

 


Topic: VEDIT 6.21.1 release candidate (3 of 32), Read 48 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Sunday, July 17, 2011 05:43 PM

At 10:19 AM 7/17/2011, you wrote:

> The text in the dialog box says '&' instead of '&&'.

> The default command in slot 2 is "dir > out"
> I think it should be "dir > vout".

Pauli:

I fixed that today; thanks for noticing and reporting it.

> By the way, where is this file vout stored?

Where ever the "current directory" is. I think VEDIT always shells out to the current directory.

> I rarely use this "Save and run programs" function.
> It would be more useful if you could specify the menu
> text for each sub-menu item.
> The dialog box could have another text field for entering > the menu text.

> BTW, I recall many years ago there were plans to make the > whole Vedit menu system configurable.

Those would be nice improvements, but not today. :)

Ted.

 


Topic: VEDIT 6.21.1 release candidate (4 of 32), Read 47 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Wednesday, July 20, 2011 06:11 PM

Thanks Ted,

I am really looking forward to using Vedit 6.21.1 !

I like very much the new directory structure. In particular I like the new USER_Home directory.

So, this year I am starting my New Year's Resolution in July. It says that my HOME directory should be untouched by human hands. Only the Official Vedit installation program can touch it. At the same time, I plan to do quite a bit of editing USER_HOME directory.


I also like to study the directory structure of any program and learn about the program from the directory structure. I have a hunch that Ian is less enthusiastic about the new directory structure. (I also have a hunch that Ian has no need to classify the Vedit files and macros, he already knows them.) But I am not a programmer.


I am also looking forward in the next release to the announced additional Predefined String Values. In fact, I would like to suggest USER_MENU as a new Predefined String Value. That is to say, a sub directory of USER_MACRO. If this is not possible, then I would like Vedit to search the sub directories of USER_MACRO for .mnu files at startup.
(I take it is less work to search a sub directory than to search a new directory. But I do not know.

Thanks to everybody who made this possible,

-peter

 


Topic: VEDIT 6.21.1 release candidate (5 of 32), Read 59 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Wednesday, July 20, 2011 06:14 PM

I have placed a new 6.21.1 release candidate at:

www..../download/beta/vpa-prod.exe

It has several new features and one tiny bug fix.

Bug Fix
-------
* On some new Microsoft "high resolution" mice, the scroll wheel did not work.

New Features
------------
* I added string value PROJ_NAME as requested by Scott Lambert:

PROJ_NAME - Name of the current project, if any. It is similar to PROJ_CURRENT, but with the directory path and without the .prj extension.

* To make it easier to read/write/create .ini files for different macros, I implemented Read_Ini() and Write_Ini() commands:

Read_Ini(...) Read a value from a standard format .ini file consisting of
[Section] and Parameter=Value. If no filename is specified,
it read from the userini.ini file in the USER_CFG directory.

Write_Ini(...) Writes a value into a standard format .ini file consisting of
[Section] and Parameter=Value. If no filename is specified,
it writes to the userini.ini file in the USER_CFG directory.
If the specified file does not exist, it is created; if
necessary, the section and parameter are created.

(These commands are not yet in the help system.)


Details
-------

Read_Ini(r,"section","parameter","filename")

Reads from the file 'filename' which is assumed to be in the standard .ini file format. From [SECTION] 'section' it reads the 'parameter's value as a string and places it into text register 'r'.

For example, the command to read (and display) the "Initsize" parameter from the vedit.ini file is:

readini(10,"vedit","initsize","$(USERHOME)\vedit.ini") rt(10)

The command returns the number of characters read. Zero indicates that the file was not found, or that the [Section] or Parameter= were not found. (I might change this to return -1 if the file was not found.)

The 'filename' is optional, if none is specified it defaults to $(USER_CFG)\userini.ini

====> If you would like to suggest a different default filename, PLEASE DO.


Write_Ini(r,"section","parameter","filename")

Writes to the file 'filename' which is assumed to be in the standard .ini file format. Under [SECTION] 'section' it writes the 'parameter's value to the string in Text register 'r'. If needed, it creates the file, [Section] and Parameter=.

The command returns 1 if successful, 0 if failure.

The 'filename' is optional, if none is specified it defaults to $(USER_CFG)\userini.ini

For example, the command write a parameter to the new file mydoco.ini is:

rs(10,"Value1") writeini(10,"MySection","Parameter1","$(USERHOME)\mydoco.ini")

This creates:
[MySection]
Parameter1=Value1

AGAIN - If you would like to suggest a different default filename other than userini.ini, PLEASE DO.

--------

I will be on vacation from July 21 to July 26 with very limited Internet access. I will handle all feedback late next week.

Thank you!

Ted.

 


Topic: VEDIT 6.21.1 release candidate (6 of 32), Read 61 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, July 21, 2011 04:42 AM

On 7/20/2011 6:14:42 PM, Ted Green wrote:
>I have placed a new 6.21.1 release candidate at:
>
>www..../download/beta/vpa-prod.exe

I found a little problem in the 'compile' directory:

You recently updated C-INIT.VDM etc. to my current versions.

Somehow it happened that some corresponding changes in
compile.mnu and in java-sdk.mnu
didn't make it into the release.
(Perhaps I didn't told you about it? Don't remember.)

It's easy to fix:

In both files compile.mnu and java-sdk.mnu all appearences of "#124" need to be changed to "#55".

That change was done because register 124 interfered with some other macro(s).

Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (20 of 32), Read 22 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Tuesday, August 02, 2011 04:26 PM

On 02.08.2011 20:43 Ted Green wrote:
> At 04:42 AM 7/21/2011, you wrote:
>> From: "Christian Ziemski"
>> I found a little problem in the 'compile' directory:
>>
>> You recently updated C-INIT.VDM etc. to my current versions.
>>
>> Somehow it happened that some corresponding changes in
>> compile.mnu and in java-sdk.mnu
>> didn't make it into the release.
>> (Perhaps I didn't told you about it? Don't remember.)
>>
>> It's easy to fix:
>>
>> In both files compile.mnu and java-sdk.mnu all appearences
>> of "#124" need to be changed to "#55".
>>
>> That change was done because register 124 interfered
>> with some other macro(s).
>
> ???
> Sorry, but I don't understand nor think this is correct.
> Changing compile.mnu to use #55 will clobber any macro that is using #55
> when any item in the {TOOLS} menu is selected. #123 and #124 are reserved
> explicitly for the .mnu files.

Ted:

Now I found a hint why I did that change away from #124:

#124 is changed by Syntax_Load() and so the compile environment
sometimes had problems after changing the syntax highlighting.

If #124 is reserved for .mnu files, Syntax_Load() seems to have a bug...

I can't test it more this night. But tomorrow.

Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (22 of 32), Read 23 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Tuesday, August 02, 2011 07:21 PM

----- Original Message -----
> Now I found a hint why I did that change away from #124:
>
> #124 is changed by Syntax_Load() and so the compile environment
> sometimes had problems after changing the syntax highlighting.
>
> If #124 is reserved for .mnu files, Syntax_Load() seems to have a
> bug...
>
> I can't test it more this night. But tomorrow.

I'll check that Syntax_Load saves/restores #124 then.

Ted.

 


Topic: Re: VEDIT 6.21.1 release candidate (24 of 32), Read 20 times
Conf: VEDIT Beta Test
From: Pauli Lindgren
Date: Wednesday, August 03, 2011 10:55 AM

On 8/2/2011 7:21:19 PM, Ted Green wrote:
> ----- Original Message -----
>>
>> If #124 is reserved for .mnu files,
>> Syntax_Load() seems to have a bug...
>>
>> I can't test it more this night. But tomorrow.
>
> I'll check that Syntax_Load
> saves/restores #124 then.

It seems to me that you can not push-pop #124 in loadsyn.vdm.
Loadsyn.vdm saves some starting positions in registers #111...#124 and Vedit probably expects those values to be there when loadsyn.vdm exits.

BTW, I have seen long time ago that #124 may change when calling a macro from a menu, even if the macro itself does not change that register. (That is why I have changed my menus to not use #124 but instead use fixed T-Reg 100 for the macro.)
The reason could be that if the macro opens a file, then the automatic File-open Configuration would call loadsyn.vdm and thus destroy #124 contents.

--
Pauli

 


Topic: Re: VEDIT 6.21.1 release candidate (25 of 32), Read 14 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Wednesday, August 03, 2011 04:51 PM

At 10:55 AM 8/3/2011, you wrote:
>From: "Pauli Lindgren" (pauli0212@...)
>It seems to me that you can not push-pop #124 in loadsyn.vdm.
>Loadsyn.vdm saves some starting positions in registers #111...#124 and Vedit probably expects those values to be there when loadsyn.vdm exits.
>
>BTW, I have seen long time ago that #124 may change when calling a macro from a menu, even if the macro itself does not change that register. (That is why I have changed my menus to not use #124 but instead use fixed T-Reg 100 for the macro.)
>The reason could be that if the macro opens a file, then the automatic File-open Configuration would call loadsyn.vdm and thus destroy #124 contents.

Yes, you are correct. Loadsyn.vdm sets registers #111-#124 which are then used internally.
I need to either internally save/restore #111-#124 or find another solution.
Since Syntax_Load() clobbers #111-#124, this has caused some strange bugs in the past.
It will be fixed today.

Thanks.

Ted.


Ted.
-------------------------------------------------------------------------
Ted Green (support@...) Greenview Data, Inc.
Web: www.... 8178 Jackson Rd., Ann Arbor, MI
Tel: (734) 426-7500 Fax: 734-426-7510 VEDIT - Text/Data/Binary Editor
-------------------------------------------------------------------------

 


Topic: Re: VEDIT 6.21.1 release candidate (26 of 32), Read 13 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Wednesday, August 03, 2011 05:00 PM

A new "release candidate" dated 08/03/2011 was just placed at:

www..../download/beta/vpa-prod.exe

* It includes the new compdir.vdm, modified to save settings into macros.ini

* It fixes the problem with Synax_Load() clobbering #111 thru #124

-------
Concerning .ini files:

* I also changed compdir.vdm to use macros.ini instead of user_mac.ini.
* The default for Read_Ini() and Write_Ini() is now user-mac.ini

-----
Concerning fonts:

* The vedit.ini "Charset=" now supports all defined character sets (previously just ANSI and OEM).

-----

I probably have forgotten some other recent changes that were discussed here.

Unless there are significant problems with this, I plan to release it within a few days.
(I should update the help file to document the new Read_Ini() and Write_Ini() commands.)

Thanks again for all the feedback and macro improvements.

Ted.

 


Topic: Re: VEDIT 6.21.1 release candidate (28 of 32), Read 13 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, August 04, 2011 04:03 AM

Three issues for now, using yesterdays release candidate:

1.) There is an error in INSTALLW.VDM making it a bit difficult to read all of the four help pages during installation.

It's only a missing backquote and comma in line 2937, breaking the buttons:

own prefences and without needed write access to the Home directory.`,



2.) One thing I don't understand during installation:

(I'm on old XP just now, perhaps that's the reason...)

Either if I freshly install Vedit or update it (Type: Single or Multiple), in C:\Vedit the following directories get created and filled:

- config
- file-cfg
- projects
- syntax
- user-mac

in parallel to %APPDATA/VEDIT.

Are those double directories intended?

I at first thought of them as a fallback when %APPDATA%/Vedit isn't existing somehow, for example when a new Windows user gets created after Vedit installation.

But that didn't work. Vedit complains about missing user directory in an endless(?) loop then and has to be killed.

How is that new user problem supposed to be handled?

The macros in C:\Vedit\user-mac are correctly (IMHO) ignored when running Vedit.




3.) Not an issue, but cleaning up in C-INIT.VDM

Since #55 isn't used any more as my workaround for the #124 problem the following lines may be deleted/changed to 56 again:

// #55 Unused
Num_Push(55,99) //Save numeric regs
Num_Pop(55,99) //Restore numeric regs



Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (29 of 32), Read 13 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, August 04, 2011 04:51 AM


Another one:

Probably due to the recent internal font handling changes it could happen that Vedit doesn't display any text window.

It seems to be there but invisible (only the gray background is shown).

That was caused by the following entry in my vedit.ini:

[STATUSLINE]
Typeface=VEDIT Ansi

Deleting the Typeface entry (by using another editor than Vedit) cured the problem and after that it's changed to:

Typeface=Fixedsys

which seems to be fine.


Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (31 of 32), Read 18 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Thursday, August 04, 2011 12:07 PM

At 04:51 AM 8/4/2011, you wrote:
>From: "Christian Ziemski" (ch.ziemski@...)
>Another one:
>
>Probably due to the recent internal font handling changes it could happen that Vedit doesn't display any text window.
>
>It seems to be there but invisible (only the gray background is shown).
>
>That was caused by the following entry in my vedit.ini:
>
>[STATUSLINE]
>Typeface=VEDIT Ansi
>
>Deleting the Typeface entry (by using another editor than Vedit) cured the problem and after that it's changed to:
>
>Typeface=Fixedsys
>
>which seems to be fine.

Another good catch!
I have had this reported, but was not able to replicate it.
Previous versions of VEDIT might crash if there was a problem loading a font. I noticed the bug when working on fonts recently. This explained strange crashes that were occasionally reported and could be "fixed" by deleting the vedit.ini file. I guess I need to load a default font if the selected font doesn't load properly.

Right now I don't plan to fix this in 6.21.1. (I need something to work on next week. )

Ted.

 


Topic: Re: VEDIT 6.21.1 release candidate (32 of 32), Read 19 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Friday, August 05, 2011 01:55 PM

VEDIT version 6.21.1 dated 08/05/2011 is now released and on the website.
Here are the veditlog.txt entries for this version:

VEDIT LOG (veditlog.txt)
---------
08/05/11 6.21.1
Much, much faster (30x) Scribe spelling checker
{MISC, Box drawing mode} now works for all fonts (ANSI and OEM)
Easier integration with Windows, Explorer and IE
Improved {MISC, Save and run programs} with useful defaults
New {HELP, Dashboard info} helps to debug install/config problems
New {FILE, Projects, Quit project}
New {FILE, Projects, Set project directory} sets CURRENT_PROJ_DIR
New {MISC, Execute current buffer} helps with macro development
Improved USB installation support, including saving Projects on USB
Minor improvements to compiler support
Minor improvements to flat-csv.vdm and csv-flat.vdm macros
Minor improvements to many other supplied macros
Minor - Rename {CONFIG, Associate file types} to "Windows integration"
Minor - Syntax directory moved from HOME to USER_HOME
Minor - VEDIT Manual .pdf file moved to Help subdirectory
Technical - New ReadIni() and WriteIni() commands for .ini files
Technical - New Buf_Switch(r,VALUE,size) option
Technical - New Reg_Prep() command to optimize macros for speed
Technical - New Is_Font_OEM internal value
Technical - New Command_Check("command") tests if command recognized
Technical - New string value CURRENT_PROJ_DIR for project support
Technical - New string values VEDIT_DRIVE, HOME_DRIVE, USER_DRIVE
Fix - New vedit.ini to reduce chance of 1st time crash in Win7
Fix - Scribe didn't work under Vista/Win7
Fix - Runshell.vdm didn't work under Vista/Win7
Fix - VEDIT PDF manuals had minor problem under Vista/Win7
Fix - Compdir macro didn't work under Vista/Win7
Fix - Startup.vdm had wrong default location for ustartup.vdm
Fix - Syntax highlighting interfered with macros loading files
Fix - Uninstall would break out if vedit/old directory found
Fix - USB installation didn't work on different drive letter
Fix - Scrollwheel didn't work on some new high-res mice
Fix - {GOTO, Matching ()} could get confused or possibly hang

-------------

Thank you for everyone's help with this version.

Ted Green.

 


Topic: Re: VEDIT 6.21.1 release candidate (30 of 32), Read 11 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Thursday, August 04, 2011 12:00 PM

At 04:03 AM 8/4/2011, you wrote:
>From: "Christian Ziemski" (ch.ziemski@...) Three issues for now, using yesterdays release candidate:
>
>1.) There is an error in INSTALLW.VDM making it a bit difficult to read all of the four help pages during installation.
>It's only a missing backquote and comma in line 2937, breaking the buttons:
>own prefences and without needed write access to the Home directory.`,

Christian:

Good catch.

>2.) One thing I don't understand during installation:
>
>(I'm on old XP just now, perhaps that's the reason...)
>
>Either if I freshly install Vedit or update it (Type: Single or Multiple), in C:\Vedit the following directories get created and filled:...
>...
Are those double directories intended?

Yes, I want to keep a copy of all files in the VEDIT Home directory. Some commonly modified files I keep the original copy in the .\originals subdirectory.

>I at first thought of them as a fallback when %APPDATA%/Vedit isn't existing somehow, for example when a new Windows user gets created after Vedit installation.

Yes, that is my reason; I just haven't implemented running a new user yet. Soon.

>3.) Not an issue, but cleaning up in C-INIT.VDM
>
>Since #55 isn't used any more as my workaround for the #124 problem the following lines may be deleted/changed to 56 again:
>
>//#55Unused
>Num_Push(55,99)//Save numeric regs
>Num_Pop(55,99)//Restore numeric regs

I will leave #55 as Unused. This makes it easier to add a feature to the macro in the future.

Thank you as always.

BTW - So far, I will date-stamp the modified installw.vdm and veditpw.chm as 08/03/2011 even though I modified them today. (Else I have to re-compile vpw.exe and vpw64.exe, fix the internal checksum, etc....)

Ted.

 


Topic: Re: VEDIT 6.21.1 release candidate (27 of 32), Read 13 times
Conf: VEDIT Beta Test
From: Ted Green
Date: Wednesday, August 03, 2011 05:15 PM

At 10:55 AM 8/3/2011, vedit-betatest Listmanager wrote:

>It seems to me that you can not push-pop #124 in loadsyn.vdm.
>Loadsyn.vdm saves some starting positions in registers #111...#124 and Vedit probably expects those values to be there when loadsyn.vdm exits.

(BTW - Webboard is having problems, and this tread appears to be completely broken.)


I fixed this today by internally saving/restoring #111 thru #124.

Hopefully there will be no other conflicts with Syntax_Load.

-----
Concerning .ini files:

* I also changed compdir.vdm to use macros.ini instead of user_mac.ini.
* The default is now user-mac.ini

-----
Concerning fonts:

* The vedit.ini "Charset=" now supports all defined character sets (previously just ANSI and OEM).

The code is:

//
// Define the keys and strings for Window's character sets.
//
#define NUM_CHARSETS 20

struct charsets {
int key;
char name[16];
};

struct charsets Font_Charsets[NUM_CHARSETS] = {
ANSI_CHARSET, "ANSI",
BALTIC_CHARSET, "BALTIC",
CHINESEBIG5_CHARSET, "CHINESEBIG5",
DEFAULT_CHARSET, "DEFAULT",
EASTEUROPE_CHARSET, "EASTEUROPE",
GB2312_CHARSET, "GB2312",
GREEK_CHARSET, "GREEK",
HANGUL_CHARSET, "HANGUL",
MAC_CHARSET, "MAC",
OEM_CHARSET, "OEM",
RUSSIAN_CHARSET, "RUSSIAN",
SHIFTJIS_CHARSET, "SHIFTJIS",
SYMBOL_CHARSET, "SYMBOL",
TURKISH_CHARSET, "TURKISH",
VIETNAMESE_CHARSET, "VIETNAMESE",
JOHAB_CHARSET, "JOHAB",
ARABIC_CHARSET, "ARABIC",
HEBREW_CHARSET, "HEBREW",
THAI_CHARSET, "THAI",
0, "UNKNOWN"
};

When reading the vedit.ini file:

//
// Decode the Charset from a string into Window's key value.
//
GetPrivateProfileString( pszSection, "Charset", "ANSI", sz, 16, lpVEDITINI );
key = ANSI_CHARSET;
for (i = 0; i< NUM_CHARSETS; i++) {
if (lstrcmpi( sz, Font_Charsets[i].name) == 0 ) {
key = Font_Charsets[i].key;
break;
}
}
plogfont->lfCharSet = key;


When writing the vedit.ini file:

//
// Convert the Charset from the Window's key value into a friendly string
//
lstrcpy( szProfile, "UNKNOWN" ); //Just in case
for (i = 0; i< NUM_CHARSETS; i++) {
if (plogfont->lfCharSet == Font_Charsets[i].key) {
lstrcpy( szProfile, Font_Charsets[i].name );
break;
}
}
WritePrivateProfileString( pszSection, "Charset", szProfile, lpVEDITINI );

------

Thanks again for all the feedback and macro improvements.

Ted.


Ted.
-------------------------------------------------------------------------
Ted Green (support@...) Greenview Data, Inc.
Web: www.... 8178 Jackson Rd., Ann Arbor, MI
Tel: (734) 426-7500 Fax: 734-426-7510 VEDIT - Text/Data/Binary Editor
-------------------------------------------------------------------------

 


Topic: VEDIT 6.21.1 release candidate (7 of 32), Read 42 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, July 21, 2011 08:48 AM

There are two typos in SORTMERGE.VDM:

line 350:
[Get keyfields] sets keyfields from delimites in the current line.

==> delimiters


line 421:
`Delete the the current line?`,

==> doubled "the"



Christian

 


Topic: VEDIT 6.21.1 release candidate (8 of 32), Read 40 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, July 21, 2011 08:53 AM

COMPDIR.VDM may have problems due to the fact that it saves the used directories in the macro itself (sort of "self-modifying").
We should try to find a better solution.

Any suggestions?


And COMPDIR.VDM seems to fail when it finds "filename.ext" in one and something like "filename.ext.bak" in the other directory.

Since I own a brand new Windows 7 box since Tuesday I'll have a look at COMPDIR.VDM soon.

Christian

 


Topic: VEDIT 6.21.1 release candidate (9 of 32), Read 52 times, 1 File Attachment
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Friday, July 22, 2011 09:51 AM

On 7/21/2011 8:53:45 AM, I wrote:
>COMPDIR.VDM may have problems due to the fact that it saves
>the used directories in the macro itself (sort of "self-modifying").

That is changed now in the attached version of COMPDIR.VDM.

It uses an .ini file now: "$(USER_CFG)\user_mac.ini"
by writing/reading this section:

[COMPDIR]
dir1=c:\vedit\macros
dir2=c:\vedit\user-mac
subdirs=no

with the new Write_Ini()/Read_Ini() commands.


I think this user_mac.ini could/should be used by other user supplied macros as well.

On the other side it may be better to have different .ini files for different macros...

Fortunately there's more than one way to go.


>And COMPDIR.VDM seems to fail when it finds "filename.ext"
>in one and something like "filename.ext.bak" in the
>other directory.

That should be fixed too.


It would be nice if somebody else could test this new version as well.


Christian

 
COMPDIR(1).VDM (31KB)

 


Topic: VEDIT 6.21.1 release candidate (10 of 32), Read 52 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Friday, July 22, 2011 11:58 AM

On 7/22/2011 9:51:20 AM, Christian Ziemski wrote:
>On 7/21/2011 8:53:45 AM, I wrote:
>>COMPDIR.VDM may have problems due to the fact that it saves
>>the used directories in the macro itself (sort of "self-modifying").
>
>That is changed now in the attached
>version of COMPDIR.VDM.
>
>It uses an .ini file now:
>"$(USER_CFG)\user_mac.ini"
>by writing/reading this section:
>
>[COMPDIR]
>dir1=c:\vedit\macros
>dir2=c:\vedit\user-mac
>subdirs=no
>
>with the new Write_Ini()/Read_Ini()
>commands.
>
>
>I think this user_mac.ini could/should
>be used by other user supplied macros as
>well.
>
>On the other side it may be better to
>have different .ini files for different
>macros...
>
>Fortunately there's more than one way to
>go.
>
>
>>And COMPDIR.VDM seems to fail when it finds "filename.ext"
>>in one and something like "filename.ext.bak" in the
>>other directory.
>
>That should be fixed too.
>
>
>It would be nice if somebody else could
>test this new version as well.
>
>
>Christian

Hi,

I have downloaded it to my MACRO directory. Then I renamed my old one to COMDIR_2004.VDM and your macro to COMPDIR.VDM.

I had no problem launching it from the Vedit {Misc, More macros} menu. In fact, it worked like a charm !

This time I also noticed a blue "button". For comparing two files that are different. I clicked on it and sure enough the cursor ended up on one of my typos.


Apropos typos. I have a hunch that this macro discriminates against people, like myself, who make many typos.

Question: Would it be possible to integrate COMPDIR.VDM with the Vedit File Selector. In other words, would it be possible to copy and paste directories from the Vedit File Selector into COMPDIR.VDM I have a hunch that copying from different programs, like .chm files, is always a delicate question. I just thought, it is no harm to ask.

It just occurred to me. In the good old days of DOS Directory Compare was one of my favorite programs. This was a poor man's XTREE or something like that, I have forgotten.
I also remember that you did succeed in importing some of the XTREE feaures into Vedit. So, possibly, probably, your XTREE macro already has built in navigation. May be one could take it from there.


Thanks as always.

-peter

 


Topic: VEDIT 6.21.1 release candidate (11 of 32), Read 41 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Friday, July 22, 2011 08:10 PM

On 7/22/2011 11:58:27 AM, peter rejto wrote:
>On 7/22/2011 9:51:20 AM, Christian
>Ziemski wrote:
>>On 7/21/2011 8:53:45 AM, I wrote:
>>>COMPDIR.VDM may have problems due to the fact that it saves
>>>the used directories in the macro itself (sort of "self-modifying").
>>
>>That is changed now in the attached
>>version of COMPDIR.VDM.
>>
>>It uses an .ini file now:
>>"$(USER_CFG)\user_mac.ini"
>>by writing/reading this section:
>>
>>[COMPDIR]
>>dir1=c:\vedit\macros
>>dir2=c:\vedit\user-mac
>>subdirs=no
>>
>>with the new Write_Ini()/Read_Ini()
>>commands.
>>
>>
>>I think this user_mac.ini could/should
>>be used by other user supplied macros as
>>well.
>>
>>On the other side it may be better to
>>have different .ini files for different
>>macros...
>>
>>Fortunately there's more than one way to
>>go.
>>
>>
>>>And COMPDIR.VDM seems to fail when it finds "filename.ext"
>>>in one and something like "filename.ext.bak" in the
>>>other directory.
>>
>>That should be fixed too.
>>
>>
>>It would be nice if somebody else could
>>test this new version as well.
>>
>>
>>Christian
>
>Hi,
>
>I have downloaded it to my MACRO
>directory. Then I renamed my old one to
>COMDIR_2004.VDM and your macro to
>COMPDIR.VDM.
>
>I had no problem launching it from the
>Vedit {Misc, More macros} menu. In fact,
>it worked like a charm !
>
>This time I also noticed a blue
>"button". For comparing two files that
>are different. I clicked on it and sure
>enough the cursor ended up on one of my
>typos.
>
>
>Apropos typos. I have a hunch that this
>macro discriminates against people, like
>myself, who make many typos.
>
>Question: Would it be possible to
>integrate COMPDIR.VDM with the Vedit
>File Selector. In other words, would it
>be possible to copy and paste
>directories from the Vedit File Selector
>into COMPDIR.VDM I have a hunch that
>copying from different programs, like
>.chm files, is always a delicate
>question. I just thought, it is no harm
>to ask.
>

Hi,

I would like to come back to the question of automating or partially automating the entering of the names of the two directories that I wish to compare.

My first preference is via the Vedit File Selector Utility,
as per my previous email.


My second preference is via the [RECENT FILES] section of the Vedit.ini file. In other words, in addition to the option of typing in the names of the directories I would like to have the option of highlighting the name of the directory in this section of the Vedit.ini file.
(Then, the rest would be the usual Register_Copy_Block() routine ?)

In fact, we have a new command to edit any section of the Vedit.ini file. So, it would be easy to access the [RECENT FILES] section.

These are just two personal preferences. I also went back to the Xtree, Dir_Date() discussion. I learned that everybody is very enthusiastic about Ztree. However, at present I can barely keep up with the new developments in Vedit and so, I am not ready to learn a new software.


Thanks as always.

-peter

 


Topic: VEDIT 6.21.1 release candidate (13 of 32), Read 34 times
Conf: VEDIT Beta Test
From: Pauli Lindgren
Date: Saturday, July 23, 2011 09:52 AM

On 7/22/2011 8:10:45 PM, peter rejto wrote:
>
>I would like to come back to the
>question of automating or partially
>automating the entering of the names of
>the two directories that I wish to
>compare.
>
>My first preference is via the Vedit
>File Selector Utility,
>as per my previous email.
>
>
>My second preference is via the [RECENT
>FILES] section of the Vedit.ini file. In
>other words, in addition to the option
>of typing in the names of the
>directories I would like to have the
>option of highlighting the name of the
>directory in this section of the
>Vedit.ini file.
>(Then, the rest would be the usual
>Register_Copy_Block() routine ?)
>
>In fact, we have a new command to edit
>any section of the Vedit.ini file. So,
>it would be easy to access the [RECENT
>FILES] section.

The problem is that the Dialog_Input_1() command in Vedit macro language does not have any method to display a list.
There is no text_area, listbox or combobox available.

Combobox is one of the enhancements to DI1 that I have hoped for a long time.
Combo box is used for example in File Open dialog box. There you can either type in the File name or click on the triangle button to open a list of previously used filenames.
Similarly, in Search dialog, you can either type in the search string or click on the triangle button to open list of previously used search strings.

Combo box would be useful for example in Wildfilew.vdm.
I would like to use it in all text input fields (search, replace, filename, directory etc.) to allow using previously used entries.

--
Pauli

 


Topic: VEDIT 6.21.1 release candidate (15 of 32), Read 36 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Saturday, July 23, 2011 01:35 PM

On 7/23/2011 9:52:40 AM, Pauli Lindgren wrote:
>On 7/22/2011 8:10:45 PM, peter rejto
>wrote:

>>My second preference is via the [RECENT
>>FILES] section of the Vedit.ini file. In
>>other words, in addition to the option
>>of typing in the names of the
>>directories I would like to have the
>>option of highlighting the name of the
>>directory in this section of the
>>Vedit.ini file.
>>(Then, the rest would be the usual
>>Register_Copy_Block() routine ?)
>>
>
>The problem is that the Dialog_Input_1()
>command in Vedit macro language does not
>have any method to display a list.
>There is no text_area, listbox or
>combobox available.
>
>Combobox is one of the enhancements to
>DI1 that I have hoped for a long time.
>Combo box is used for example in File
>Open dialog box. There you can either
>type in the File name or click on the
>triangle button to open a list of
>previously used filenames.
>Similarly, in Search dialog, you can
>either type in the search string or
>click on the triangle button to open
>list of previously used search strings.
>
>Combo box would be useful for example in
>Wildfilew.vdm.
>I would like to use it in all text input
>fields (search, replace, filename,
>directory etc.) to allow using
>previously used entries.
>
>--
>Pauli

Hi,

I was glad to learn that I have asked a relevant question.
(The rest should be easy ?)

Now let me give you a progress report:

When COMPDIR.VDM prompted me for a directory name, I have opened up my Vedit.ini file and highlighted a pathname in that file. Then I used the Ctrl-C and Ctrl-V routine to enter it into the dialog box. It seemed to work.

I have not tried to automate this procedure via a macro.

May be, to be on the safe side, I should invoke a new copy of Vedit, do the copying to the Windows clipboard in the new invocation, close it and go back to the original invocation. Then use Ctrl-V in the original invocation to copy the pathname from the Windows clipboard into the COMPDIR dialog box.

This way I would not do any potential harm to my original invocation of Vedit, where I opened COMPDIR.VDM.

Actually, I would love to do it this way as a tutorial for my "inverse search" in my Miktex previewer Yap.exe.
I do this via my LATEX.VCS written by Christian and Yap.vdm written by Fritz. They work together like black magic and I would like to have a simpler model that I can understand.

Thanks as always,

-peter

 


Topic: VEDIT 6.21.1 release candidate (12 of 32), Read 37 times
Conf: VEDIT Beta Test
From: Pauli Lindgren
Date: Saturday, July 23, 2011 09:04 AM

On 7/22/2011 9:51:20 AM, Christian Ziemski wrote:
>
>I think this user_mac.ini could/should
>be used by other user supplied macros as
>well.

Yes, user_mac.ini would be a good choice for user supplied macros.
However, if these changes are included with Vedit distribution, then it is not a user supplied macro.
For supplied macros, I think a good name would be macros.ini. This way, the name of .ini file reflects the name of the macro directory.

If the name of .ini file is left out, the question is, should the default filename be user_mac.ini or macros.ini?
For a user creating new macros, it might be better that it was user_mac.ini.

>
>On the other side it may be better to
>have different .ini files for different
>macros...

I think that if the macro only stores a few values, it could use the common .ini file. If there are many values, then it may be better to use a dedicated file.

One problem with using the read_ini command is that for each individual read, it opens the file, reads the value and closes the file. When reading multiple values, it is more efficient to open the file, read all the values and then close the file, as it is done in wildfilew.vdm etc. In some cases, it may be necessary to keep the .ini file open during the whole macro execution.

>
>>And COMPDIR.VDM seems to fail when it finds "filename.ext"
>>in one and something like "filename.ext.bak" in the
>>other directory.
>
>That should be fixed too.

I was not going to talk about this yet.
But I think you should not spend too much time improving compdir.vdm.
I have made a much improved version of the macro, with better user interface and many new features. And most importantly, it calls my own cmp_1_2.vdm macro instead of compare.vdm. I have used this for a couple of years myself, but there are still many things that need to improve. And I have only started to write the help file.

--
Pauli

 


Topic: Re: VEDIT 6.21.1 release candidate (16 of 32), Read 35 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Monday, July 25, 2011 02:10 PM

On 23.07.2011 15:04 in vedit-betatest Pauli Lindgren wrote:
>
> But I think you should not spend too much time
> improving compdir.vdm.
> I have made a much improved version of the macro,
> with better user interface and many new features.
> And most importantly, it calls my own
> cmp_1_2.vdm macro instead of compare.vdm.
> I have used this for a couple of years myself,
> but there are still many things that need to improve.
> And I have only started to write the help file.

Pauli:

O.k. So I won't think about enhancements for compdir any more.
I'll only fix bugs - if time and enthusiasm allow.

Usually I'm using kdiff3 for such compares now (on Linux and Windows).

But I'm interested to see (and test ;-) your new compdir.vdm!

Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (21 of 32), Read 20 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Tuesday, August 02, 2011 04:31 PM

On 02.08.2011 21:55 Ted Green wrote:
>
> I changed the default filename to be user_mac.ini.

"user-mac.ini" then, isn't it?

> I am inclined to agree with Pauli that there should
> be two .ini files, I would prefer macros.ini and user-mac.ini
> (with a dash, not an underscore).

Agreed.

Christian

 


Topic: VEDIT 6.21.1 release candidate (17 of 32), Read 32 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Thursday, July 28, 2011 10:51 AM

On 7/22/2011 9:51:20 AM, Christian Ziemski wrote:
>On 7/21/2011 8:53:45 AM, I wrote:
>>COMPDIR.VDM may have problems due to the fact that it saves
>>the used directories in the macro itself (sort of "self-modifying").
>
>That is changed now in the attached
>version of COMPDIR.VDM.
>
>It uses an .ini file now:
>"$(USER_CFG)\user_mac.ini"
>by writing/reading this section:
>
>[COMPDIR]
>dir1=c:\vedit\macros
>dir2=c:\vedit\user-mac
>subdirs=no
>
>with the new Write_Ini()/Read_Ini()
>commands.
>
>
>I think this user_mac.ini could/should
>be used by other user supplied macros as
>well.
>
>On the other side it may be better to
>have different .ini files for different
>macros...
>
>Fortunately there's more than one way to
>go.
>
>
>>And COMPDIR.VDM seems to fail when it finds "filename.ext"
>>in one and something like "filename.ext.bak" in the
>>other directory.
>
>That should be fixed too.
>
>
>It would be nice if somebody else could
>test this new version as well.
>
>
>Christian

Hi,

I am studying the new COMPDIR.VDM for Vedit 6.21. Specifically, I am looking at the :DIALOG: subroutine, and subsection;

//-- // Get the default dir1 and dir2 prompts into Reg(10) and Reg(11).

Suppose that I have already copied and pasted them into T-Reg(10) and T-Reg(11).

Now I would like to have the option of calling COMPDIR.VDM

I have also tested this new version and it works like a charm.

Thanks as always,


-peter

 


Topic: Re: VEDIT 6.21.1 release candidate (18 of 32), Read 36 times
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Thursday, July 28, 2011 03:39 PM

On 28.07.2011 16:52 in vedit-betatest Peter Rejto wrote:
>
> I am studying the new COMPDIR.VDM for Vedit 6.21. Specifically,
> I am looking at the :DIALOG: subroutine, and subsection;
>
> //-- // Get the default dir1 and dir2 prompts into Reg(10) and Reg(11).
>
> Suppose that I have already copied and pasted them into T-Reg(10) and
> T-Reg(11).
>
> Now I would like to have the option of calling COMPDIR.VDM

My internal version already does have such an option.
I'm using this feature from the user menue with different "preloaded"
COMPDIR calls.

I'll try to merge that option into the published COMPDIR - As far as I
remember that are only a couple of lines of code.


Christian

 


Topic: Re: VEDIT 6.21.1 release candidate (19 of 32), Read 24 times, 1 File Attachment
Conf: VEDIT Beta Test
From: Christian Ziemski
Date: Monday, August 01, 2011 08:40 AM

On 7/28/2011 3:39:17 PM, I wrote:
>On 28.07.2011 16:52 in vedit-betatest Peter Rejto wrote:
>>
>> Suppose that I have already copied and pasted them into >> T-Reg(10) and T-Reg(11).
>>
>> Now I would like to have the option of calling COMPDIR.VDM
>
>My internal version already does have such an option.
>I'm using this feature from the user menue with different "preloaded" COMPDIR calls.
>
>I'll try to merge that option into the published COMPDIR -


And here it is (attached)...

I only merged that feature in (together with some small fixes). My (several years old) "internal" version does have some more features, but due to Pauli's comment I don't plan to work on it any more.


You can now call COMPDIR from within VEDIT:

N_Option(2) Reg_Set(103,*"dir1" "dir2"*) (CALL_File(100, "compdir.vdm")

Use N_Option(3) if sub-directories should be processed as well.

The double quotes surrounding the filenames are only necessary if the path or filenames contain spaces...


Calling the macro this way is useful for the {User} menu for example:

0
Compare VEDIT's Macro directories
N_Option(2) RS(103, '"') RS(103, MACRO, APPEND) RS(103, '" "', APPEND) RS(103, USER_MACRO, APPEND) RS(103, '"', APPEND) CALL_File(100, "compdir.vdm")


When there are no spaces in path or filename this easier call would be sufficient:

N_Option(2) Reg_Set(103,MACRO) Reg_Set(103, " ", APPEND) Reg_Set(103, USER_MACRO, APPEND) CALL_File(100, "compdir.vdm")

But it is safer to use the double quotes.

Christian

 
COMPDIR(2).VDM (34KB)

 


Topic: Re: VEDIT 6.21.1 release candidate (23 of 32), Read 25 times
Conf: VEDIT Beta Test
From: Peter Rejto
Date: Wednesday, August 03, 2011 01:32 AM

Thanks Christian. I really like your COMPDIR(2) very much!

-peter

 


Topic: Re: VEDIT 6.21.1 release candidate (14 of 32), Read 31 times
Conf: VEDIT Beta Test
From: Pauli Lindgren
Date: Saturday, July 23, 2011 10:15 AM

Ted Green wrote:
>
> I would suggest using an .ini file
and the new Read_Ini and Write_Ini commands:
>
> * Using a [COMPDIR] s
ection in a new userini.ini file. Or better name...
>
> Current I th
ink:
>
> * macroini.ini might be a better name than userini.ini for sup
plied macros.

> (Or even just macros.ini) I can easily change the
default when no name
> is provided.

> * Instead of using e.g. wi
ldfilew.ini and veditpdf.ini, just make sections
> in the macroini.in
i file for them.

I would not want to save wildfilew settings in a comm
on ini file.
Wildfile has lots of settings, and my new version has even m
ore (separate settings for each of the 5 searches).

In addition, I am
planning to add an option to save project specific settings.
When this op
tion is enabled, wildfilew.ini, as well as the search results and related .
syn files will be stored in CURRENT_PROJ_DIR.

--
Pauli