Topic: New Wildfile for Windows (wildfilew.vdm) (1 of 44), Read 111 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Wednesday, September 20, 2006 01:41 PM

Hi,

I have made a new version of (or replacement for) Wildfile Wizard: WILDFILEW.VDM (Wildfile for Windows), attached with this message.

The user interface is totally new. It is not a wizard any more. Instead, all the input needed for multi file search can be entered on single dialog box. In addition, the macro remembers your previous settings, so normally you only need to enter the search string and then press Enter. Or, if you have highlighted a block, you only need to press Enter! If you select search with "List" or "Extract" option, even the end dialog is omitted, the search results are just displayed in a window.

One problem with old Wildfile Wizard was that you could not change the directory. On Wildfilew.vdm, the starting directory is given in a text box and you can edit it. Or you can click Browse button to change the directory visually. (Note: the Browse button is only used for changing directory, not for selecting files.)

If you want to perform Search & Replace operation instead, just click the Replace button. The dialog box will change slightly to present options needed for replace. Any input you have already entered in Search dialog (search string, file filters, options etc.) will remain in effect. (However, the "Display matched lines as" option is stored separately for each dialog box.)

If you want to perform any other operations, click the Menu button. This opens a menu dialog that contains buttons for selecting the operations: Search, Replace, Commands or Macro. In addition, there are two new buttons: View button displays the last search results. Options button allows you to configure how the macro operates.

If you perform a search with "List" option, wildfilew.vdm sets up double-click event macro (if one has not been set up earlier). This allows you to directly go to the file and location where the string was found, by double-clicking the corresponding line in the search.tmp window.

Note: the double click event macro calls an external macro search116.vdm (included in the zip package). Originally I was going to set up that macro directly as event macro, but then file type specific configuration did not work and syntax highlight etc. were not working on the file opened from the event macro.

There are some more enhancements in Wildfilew.vdm.

In Search and Search & Replace dialog boxes, you can see a new option, "Skip comments". If you tick this, any search strings found within comments are ignored. Currently only supports C and C++ comments. (It would be nice if you could read the comment delimiters from the color syntax definition and automatically support all file types.)

Read-only mode and NOEVENT options are used to speed up search, when search is performed with "List" or "Extract" option. In Commands and Macro functions, there is a tickbox in the dialog box for selecting the read-only mode.

If you perform Replace, any read-only files are skipped. (In Wildfile Wizard, break-out occurs if read-only file is encountered.) But maybe this should be user-selectable option, since otherwise the user may not notice that some files were not changed?

Syntax highlight now highlights replace string (in addition to search string), and recognizes Case Sensitive option. (New search.syn file included in the zip package.)


Bugs fixed from Wildfwiz.vdm:

- Wildfwiz.vdm tried to ensure T-Reg[#93] is adjacent to T-Reg[#94].
This didn't work, instead caused infinite loop. Now this works as expected.

- Wildfwiz.vdm tried to read config values for search options, but always got 0 for every option. Now the configure options are read correctly (if you have selected that option).

- If multiple replaces were done on single line, the Display option displayed the line after only the first change was made. Now the line is displayed after all changes have been made.

- 1st time in flag (#91) for "Macro" or "Command" option didn't work, since it was pushed/popped on stack before macro call.
Now #98 is used instead, and it is not pushed/popped.

- The screen blinking during search is fixed. Search result list is now displayed during the search.


Note: Wildfilew.vdm is quite a complex macro and I have not had time to test it extensively. Therefore, this should be considered as beta version. It is good idea to first test it with less important files!

There are a few things that may need adjustment in the user interface.
For example:
- Should there be options "Simple" and "Hex" for search mode?
- In Replace dialog, there is Back button for returning to Search dialog. But if you entered Replace dialog from Menu dialog, this is not very logical. Any suggestions?
- Currently, the Menu dialog displays text "Operations", as in Wildfwiz.vdm. Should it read "Menu" or "Main menu" or something?
- Any better name for the macro?
- etc.

I have tried to keep the register usage same as in Wildfwiz.vdm as much as possible. The registers that have been changed are marked with *, and new registers are marked with +.


--
Pauli

 
WILDFILEW.ZIP (15KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (2 of 44), Read 75 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Wednesday, September 20, 2006 02:17 PM

At 01:47 PM 9/20/2006, you wrote:

>I have made a new version of (or replacement for) Wildfile Wizard: WILDFILEW.VDM (Wildfile for Windows), attached with this message.

Wow and thank you. I will examine the macro carefully after my return from San Francisco next week (where I will be vacationing for a few days with Christian Ziemski.)

Ted.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (3 of 44), Read 77 times
Conf: Wildfile, Other macros
From: Ian Binnie
Date: Wednesday, September 20, 2006 11:00 PM

On 9/20/2006 1:41:32 PM, Pauli Lindgren wrote:
> I have made a new version of (or replacement for) Wildfile
> Wizard: WILDFILEW.VDM (Wildfile for Windows), attached with this
> message.

I tried the new macro and like it.

I had composed a reply, outlining shorcomings and suggesting
improvements, but then discovered that some of these were
addressed in the Options to configure how the macro operates.

I would suggest that the defaults be changed to:
Last dir used by Wildfilew
Last search/replace strings used by Wildfilew

It is easy to overwrite or delete these if needed (this is how most
Windows programs work), and many users may never discover the
Options button otherwise. Indeed it may be better to put this on
the opening dialog.

> One problem with old Wildfile Wizard was that you could not
> change the directory. On Wildfilew.vdm, the starting directory
> is given in a text box and you can edit it.

This is a fantastic improvement.

I rarely used the old wizard, because if you made a single
mistake, you had to go back and re-enter everything.
(I particularly HATE having to navigate through keyholes to get
to a directory.)


> There are a few things that may need adjustment in the user
> interface. For example: - Should there be options "Simple" and
> "Hex" for search mode?

I would like to see a "Simple", to make it easier to search for
pattern matching codes.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (4 of 44), Read 76 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Thursday, September 21, 2006 10:25 AM

At 11:00 PM 9/20/2006, you wrote:
>I tried the new macro and like it.
>This is a fantastic improvement.

Very likely we will integrate this macro (with a few changes) with
the normal Search/Replace dialog boxes.

Thank you again.

BTW - Please remember that both I and Christian are now "off-line" until Oct 1.

Ted.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (6 of 44), Read 75 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Thursday, October 05, 2006 05:12 AM

On 9/20/2006 11:00:20 PM, Ian Binnie wrote:

> would suggest that the defaults be changed to:
> Last dir used by Wildfilew
> Last search/replace strings used by Wildfilew

I think current file's dir is the best choice in most cases.

If you have more than one project you are working on, the "Last dir used by Wildfilew" is wrong most of the time. Even within the same project, I often need to search from different folder hierarchies (for example: source files, global header files, library sources and document files are all in different folder hierarchies).

With current file's dir option, it is easy to select correct directory by selecting one of the open files (or by opening a file from Proj tab).

But maybe the last dir option would be easier to understand for beginners.

For search/replace strings, I think the "empty" option is probably the least confusing for a beginner. In addition, with this option, you can easily see if you had a block highlighted or not.
By the way, if you leave the search box empty, the last search string is automatically used. (The disadvantage is that the searched word will not be highlighted in the search result listing.)

However, "Current search/replace strings" is quite useful, too. If you have performed a normal search, it is then easy to perform the same search/replace with Wildfilew. On the other hand, if your last search was done with Wildfilew, then the last Wildfilew search strings will be used, since Wildfilew stores search/replace strings into "current search/replace strings".

Additional advantage with "Current" option is that current search/replace strings are saved with Vedit projects.

After the "project home directory" setting becomes available in Vedit, I am planning to add an option to save wildfilew.ini file in project home directory.
This way, Wildfilew would remember directory, search strings etc. separately for each project.

Ted, a useful enhancement to Vedit macro language would be a Combo Box object. Then it would be possible to have list of previous search and replace strings (as in normal Search dialog), directories, and file filters.


> It is easy to overwrite or delete these if needed (this is how most
> Windows programs work), and many users may never discover the
> Options button otherwise. Indeed it may be better to put this on
> the opening dialog.

Do you mean the Search dialog? (Menu dialog can be configured to be the opening dialog, too.)

I am afraid there is no room for Options button in the search dialog. It would be nice to have the View button and Help button in Search dialog, too, but there is no room. That is why I created Menu dialog in the first place. (And options button is not needed often anyway.)

By the way, a Help button would be useful at least in the Menu dialog. I recall it could be possible to call Vedit Help from macro, or is it? Of course that would require Wildfilew.vdm help to be included in Vedit help file.


--
Pauli

 


Topic: New Wildfile for Windows (wildfilew.vdm) (7 of 44), Read 74 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Thursday, October 05, 2006 06:21 AM

On 10/5/2006 5:12:22 AM, Pauli Lindgren wrote:
>
>I am afraid there is no room for Options
>button in the search dialog. It would be
>nice to have the View button and Help
>button in Search dialog, too, but there
>is no room. That is why I created Menu
>dialog in the first place. (And options
>button is not needed often anyway.)

No room?
You don't want to use another row of buttons?
I see that the interface may be overloaded with too many options, but it IS a powerful macro...


>By the way, a Help button would be
>useful at least in the Menu dialog. I
>recall it could be possible to call
>Vedit Help from macro, or is it?

Yes it is. E.g. see here: http://www.ziemski.net/vedit/macros/cont-hlp.vdm

>Of course that would require Wildfilew.vdm
>help to be included in Vedit help file.


What about a macro specific help displayed with something like in this demo: http://www.ziemski.net/vedit/macros/di1-scroll2.vdm


Christian

 


Topic: New Wildfile for Windows (wildfilew.vdm) (8 of 44), Read 75 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Thursday, October 05, 2006 08:08 AM

On 10/5/2006 6:21:41 AM, Christian Ziemski wrote:

Here is a quick shot version of the macro to explain my last message.

It has additional buttons to replace the extra menu and it has a help dialog.


Christian

 
WILDFWIZ.VDM (56KB)

 


Topic: New Wildfile for Windows (wildfilew.vdm) (14 of 44), Read 73 times, 2 File Attachments
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, October 06, 2006 02:42 PM

On 10/5/2006 8:08:32 AM, Christian Ziemski wrote:
>
>Here is a quick shot version of the macro to explain my last message.
>
>It has additional buttons to replace the extra menu and it has a help dialog.

I made a couple of modified versions of your macro.
One has the additional buttons on the top of dialog, and the other one has them in the middle (as a separator between file selection and the variable operation part).

Maybe the top one is better, since the buttons in the middle make it more difficult to move between the text input boxes using Tab key.

This version might be good if it would be possible to display pushed-down buttons, or at least grayed buttons (to indicate the currently selected option).

--
Pauli

 
WILDFILEW_TOP.VDM (55KB)
 
WILDFILEW_MID.VDM (55KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (15 of 44), Read 75 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Friday, October 06, 2006 03:43 PM

On Fri, 06 Oct 2006 14:42:00 -0400, Pauli Lindgren wrote:

>On 10/5/2006 8:08:32 AM, Christian Ziemski wrote:
>>
>>It has additional buttons to replace the extra menu [...].
>
>I made a couple of modified versions of your macro.
>[...]
>Maybe the top one is better, since the buttons in the middle make
>it more difficult to move between the text input boxes using Tab key.

I prefer the top version too. It's more intuitive to first choose the
operation.

>This version might be good if it would be possible to display
>pushed-down buttons, or at least grayed buttons (to indicate the
>currently selected option).

The buttons doesn't seem to have different states.
So I coded a workaround (see attachment):
The text of the "pressed" button is modified on press.
I used different indicators for the 4 buttons for comparison.

Christian

 
WILDFILEW_TOP_2.VDM (56KB)

 


Topic: New Wildfile for Windows (wildfilew.vdm) (11 of 44), Read 76 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, October 06, 2006 11:35 AM

On 10/5/2006 6:21:41 AM, Christian Ziemski wrote:
>
>No room?
>You don't want to use another row of buttons?
>I see that the interface may be
>overloaded with too many options, but it
>IS a powerful macro...

The 2nd row of buttons does look quite messy.
Especially if there are 5 buttons on the 2nd row and only 4 buttons on the 1st row.

I was trying to make the Search dialog as simple as possible and put the other functions in other dialogs. After all, search is what people will use most of time. (I rarely even use Replace, since it feels too risky.)

Originally, I had [Advanced] button instead of [Menu].
That opened a dialog that contained both Command and Macro functions. But then I added View and Options operations, so I had to add the Menu dialog.

One possibility would be to have [More>>] button instead of the [Menu] button. Clicking it would add the 2nd row of buttons (and change [More>>] button into [Less<<] button).

Another problem with the 2nd row is that you do not have the description texts as in the Menu dialog. Tooltips would help, but Dialog_Input1 command does not support tooltips.

And what if more functions would be added to Wildfilew.vdm? Then you would need even more buttons. For example, I have been thinking of integrating the Proximity Search into Wildfilew.vdm.

>
>
>>By the way, a Help button would be
>>useful at least in the Menu dialog. I
>>recall it could be possible to call
>>Vedit Help from macro, or is it?
>
>Yes it is. E.g. see here:
>http://www.ziemski.net/vedit/macros/cont-hlp.vdm

Hmmm.. seems that this only supports macro command help. I thought there would be a general way to view any part of the help. Too bad.

>
>>Of course that would require Wildfilew.vdm
>>help to be included in Vedit help file.
>
>
>What about a macro specific help
>displayed with something like in this
>demo:
>http://www.ziemski.net/vedit/macros/di1-scroll2.vdm

Yes, that is better than nothing for user macros.
However, there is help for Wildfile Wizard in Vedit Help. It would be better that, when user clicks F1 in Wildfile, the real Wildfile help would be displayed instead of generic dialog box help, which is what happens now with Wildfile Wizard.

Even for user macros, it would be nice to be able to call real help file. But of course creating help files is not so easy and it requires Help Compiler, if I am not mistaken. (Or does the new Html Help on Windows XP require compiled help files?)

--
Pauli

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (12 of 44), Read 77 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Friday, October 06, 2006 12:48 PM

Pauli:

On Fri, 06 Oct 2006 11:35:00 -0400, you wrote:

>The 2nd row of buttons does look quite messy.
>Especially if there are 5 buttons on the 2nd row and only
>4 buttons on the 1st row.

Agreed. Not perfect.

>I was trying to make the Search dialog as simple as possible and put
>the other functions in other dialogs. After all, search is what
>people will use most of time.

Not all users are the same...

>One possibility would be to have [More>>] button instead of the
>[Menu] button.
>Clicking it would add the 2nd row of buttons (and change [More>>]
>button into [Less<<] button).

That seems to be a good compromise between "simple" and "full
featured".


>Another problem with the 2nd row is that you do not have the
>description texts as in the Menu dialog. Tooltips would help,
>but Dialog_Input1 command does not support tooltips.

Are those descriptions really necessary here?
Isn't it self explanatory? Users using macros like Wildfilew should
know what they are doing. At least after reading the help.


>And what if more functions would be added to Wildfilew.vdm?
>Then you would need even more buttons.

I'm afraid that DI_1() is not soooo flexible.
Or that macro would become *really* complex then.
But we can try to do it ;-)


>>[Help() command)]
>
>Hmmm.. seems that this only supports macro command help.
>I thought there would be a general way to view any part
>of the help. Too bad.

IMHO the Help() command supports most of the help topics.
Unfortunately it seems to be near to impossible to know the string to
call the wished topic directly.

Perhaps another reader knows more about help?


>However, there is help for Wildfile Wizard in Vedit Help.
>It would be better that, when user clicks F1 in Wildfile, the real
>Wildfile help would be displayed instead of generic dialog box help,
>which is what happens now with Wildfile Wizard.

Yes, indeed.
After Ted will have changed VEDIT for a F1-event-macro (or so) and we
figured out the help file index name of WILDFWIZ then that can be
implemented in the macro.


>Even for user macros, it would be nice to be able to call real
>help file.

You can. With the System("start xyz.hlp") command.
Unfortunately I don't know whether it's possible to call a topic this
way. Never used and never needed it.
(Microsoft's WINHLP32.EXE and/or HH.EXE seem to be the executables to
show the help files.)


BTW: But what sort of help file one should use?
I think the .hlp format, you correctly wrote about:
>But of course creating help files is not so easy and it
>requires Help Compiler, if I am not mistaken.
will not live forever. Much of the newer help seems to be .chm format.

And how many users ever created real help files, of any format?
So I'm using simple text format help in my macros.


Christian

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (16 of 44), Read 75 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Friday, October 06, 2006 03:47 PM

On Fri, 06 Oct 2006 00:48:00 -0400, I wrote:

>IMHO the Help() command supports most of the help topics.
>Unfortunately it seems to be near to impossible to know the string
>to call the wished topic directly.

I played a little bit with veditpw.hlp (including decompiling it)
trying to understand a few of its iternals, but gave up then.

That's a task for another fellow user. ;-)


Christian

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (18 of 44), Read 74 times
Conf: Wildfile, Other macros
From: Ian Binnie
Date: Saturday, October 07, 2006 04:35 AM

On 10/6/2006 12:48:25 PM, Christian Ziemski wrote:
>Pauli:
>
>On Fri, 06 Oct 2006 11:35:00 -0400, you
>wrote:
>
>>The 2nd row of buttons does look quite messy.
>>Especially if there are 5 buttons on the 2nd row and only
>>4 buttons on the 1st row.
>
>Agreed. Not perfect.

I tried Christian's version as well as the new version Pauli posted below.

I think Christian's version is much more intuitive.
I don't care is one row has 4 buttons and another 5, I don't have to click on a cryptic Menu button which creates another dialog which then hides the values entered.
>
>>I was trying to make the Search dialog as simple as possible and put
>>the other functions in other dialogs. After all, search is what
>>people will use most of time.
>
>Not all users are the same...

I rarely use Wildfile for searching unless I NEED pattern matching (I usually use ZTeeWin for viewing files, although the new option to jump to a line may encourage me to use Vedit more often).

I mainly use Wildfile for Replace & macro.
>>One possibility would be to have [More>>] button instead of the
>>[Menu] button.
>>Clicking it would add the 2nd row of buttons (and change [More>>]
>>button into [Less<<] button).
>
That would certainly be better than a pop up.

>IMHO the Help() command supports most of
>the help topics.
>Unfortunately it seems to be near to
>impossible to know the string to
>call the wished topic directly.

This is a problem with the Microsoft help format.

>>Even for user macros, it would be nice to be able to call real help file.

I would like to be able to call help files.
In particular I would like to write a macro to call MSDN help from Vedit rather than having to open Visual Studio.

I tried some time ago, but could not make it work.

>You can. With the System("start
>xyz.hlp") command.
>Unfortunately I don't know whether it's
>possible to call a topic this
>way.

I never figured a way to do this.

>
>BTW: But what sort of help file one
>should use?
>I think the .hlp format, you correctly
>wrote about:
>>But of course creating help files is not so easy and it
>>requires Help Compiler, if I am not mistaken.
>will not live forever. Much of the newer
>help seems to be .chm format.
>
>And how many users ever created real
>help files, of any format?

I have created .hlp files, but it is a pain, and I have used a tool to do so. Unfortunately this quite old.

I have looked at .chm, but never written one.
KeyTools lets you decompile these.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (9 of 44), Read 75 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Thursday, October 05, 2006 08:21 AM

On 10/5/2006 5:12:22 AM, Pauli Lindgren wrote:
>
>By the way, a Help button would be useful at least in the Menu dialog.

Another idea for this (not only in this macro).
It requires small changes in VEDIT itself, but anyway:


If a Dialog_Input_1() is shown, pressing "F1" shows a generic help about that.

What about a change for this function:

1) Having a text register called from here (if one is available) (like the double-click macro register). If that is empty, still call the old help.
The user can code some help function in that register.

or

2) If there is a label ":F1_HELP:" in the currently running macro, Call() that. Otherwise show old help.


What do you think?


Christian

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (10 of 44), Read 74 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Thursday, October 05, 2006 02:51 PM

At 08:22 AM 10/5/2006, you wrote:
>If a Dialog_Input_1() is shown, pressing "F1" shows a generic help about that.
>
>What about a change for this function:
>
>1) Having a text register called from here (if one is available) (like the double-click macro register). If that is empty, still call the old help.
>The user can code some help function in that register.
>
>or
>
>2) If there is a label ":F1_HELP:" in the currently running macro, Call() that. Otherwise show old help.

I will add that at the top of the suggestion list.
That should be easy to implement and seems very useful.

Ted.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (13 of 44), Read 75 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, October 06, 2006 06:42 PM

Hi,

Here is new version of Wildfilew.vdm.
It contains the following changes:

- Fixed handling "no files found" case. Could cause "Found..." text to be inserted in current file when Cancel was clicked.

- Now returns to correct dialog when "no files found" occurs in Command or Macro operation.

- Fixed "search subdirectories" option in Command and Macro operations. (Was always on, regardless of the tickbox.)

- Added search mode option "Simple".
I did not add Hex option, since I think it is only useful with hex editing and not relevant to multifile search.
Removed "extract" option from Replace dialog.

- Show end dialog after Command and Macro operations, too.

- If "files" field is empty, search in current file.

- Changed the handling of read-only files.
When doing Replace with Confirm option, and searched string is found in read-only file, a dialog box opens with the options to skip the file, skip all read-only files or cancel operation.
Selecting ALL in Confirm dialog sets skip-read-only mode, too.
When replacing with List option, read-only files are skipped as before.
I think it would be better to have the dialog box there, too, but it is not easy to do.
(It is not possible to check the cause of error afterwards, inside locked-in macro, is it?)

- When doing Replace, count number of replaces, not number of found strings.

- Expanded the function of the first time flag (#98).
As before, the flag is set to 0 in the beginning.
User macro can check if the flag is 0, do any initializations needed and set the flag to 1. On the next rounds, the flag is 1 and the user macro knows that no init is needed.

I expanded this so that, when user macro is called the last time (with the last file in list), the flag is set to 2.
User macro can then e.g. display the results with dialog box, or save results in a file.

In addition, the user macro can set #98 to 2 (or higher) at any point. This causes Wildfilew.vdm to exit main loop and not process any more files.
If user macro sets the flag to 3 or higher, the end dialog is not displayed.

The macro count2.vdm, included in the zip file, is an example of how to use the flag #98. The macro counts the occurrences of specified search string.

I have included the files search.syn and search116.vdm in the package, too. So those who have not yet downloaded the previous version will get all the files needed from this zip.


--
Pauli

P.S.
Sorry, that was old version.
Removed the attachment and post correct version in the next message.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (17 of 44), Read 72 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, October 06, 2006 06:45 PM

Oops.
It appears that the zip package I posted in previous message contained old version of wildfilew.vdm.

New try. Hopefully it is the correct version now.

--
Pauli

 
WILDFILEW1.2.ZIP (17KB)

 


Topic: New Wildfile for Windows (wildfilew.vdm) (5 of 44), Read 73 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Wednesday, October 04, 2006 05:36 AM

On 9/20/2006 1:41:32 PM, Pauli Lindgren wrote:
>
>I have made a new version of (or replacement for) Wildfile
>Wizard: WILDFILEW.VDM (Wildfile for Windows),

Pauli: That is a really great macro!

I had only some minutes to play with it for now, but in the next few days I'll have to do some work on many text files where I can use your new macro.

So probably I'll post again later ;-)


Christian

 


Topic: New Wildfile for Windows (wildfilew.vdm) (19 of 44), Read 74 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Sunday, October 22, 2006 10:27 AM

Hi,

Here is a new version (V1.3) of Wildfilew.vdm.

I replaced the Menu dialog with [More >>] and [Less <<] buttons that allow you to switch between simple and full dialog box.
The full dialog box contains another two rows of buttons:
2nd row contains buttons [View], [Options] and [Help], and
3rd row contains buttons for selecting the operation.

I positioned the dialog boxes so that the button row stays in place when you switch between the dialogs.
Maybe it would be better to have the buttons in top row so that the top part of the dialog would stay in place, but that could be confusing when you switch between Simple and Full dialogs.
And it is easier to interpret buttons this way.

The [Help] button calls Vedit help. However, I did not find a way to call directly the Wildfile help. Now it opens a dialog with two options to choose from. And of course it is not Wildfilew.vdm help yet.

Other changes:

- Open search.tmp at buffer 90 (or 89, 88...) so that it will be the last tab. This way it is easier to find the search results later.

- Options defaults for directory, search string and search options changed to "last used".

- When Replace operation done, display "Replaced..." instead of "Found..." in the results window.

- Some validity checking added when reading settings from .ini file.

- Added error checking in Macro operation. If no macro filename given or if file does not exist, display error message and return to dialog box.

- Fix: when "no files found", default path could change.

- Fix: "Pattern" option in Search Mode radio button was not restored from saved value.


Wildfile.vdm is attached. I do not post the other files this time. If you do not have them yet, you need to get them from my earlier post.


--
Pauli

 
v1.3

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (20 of 44), Read 67 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Wednesday, October 25, 2006 05:07 PM

At 10:29 AM 10/22/2006, you wrote:

>Here is a new version (V1.3) of Wildfilew.vdm.
>
>I replaced the Menu dialog with [More >>] and [Less <<] buttons that allow you to switch between simple and full dialog box.
>The full dialog box contains another two rows of buttons:
>2nd row contains buttons [View], [Options] and [Help], and
>3rd row contains buttons for selecting the operation.
>
>I positioned the dialog boxes so that the button row stays in place when you switch between the dialogs.

Wow. This is really impressive!!
The [More ..] and [Less ..] buttons are really cool.

This should clearly replace the current Wildfile wizard.

What should I call it?

"Wildfile GUI" ?

Ted.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (21 of 44), Read 64 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, October 27, 2006 08:30 AM

On 10/25/2006 5:07:21 PM, Ted Green wrote:
>
>What should I call it?
>
>"Wildfile GUI" ?

I have been calling it "Wildfile for Windows".
Of course that is quite a long name, and not very cool.

--
Pauli

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (22 of 44), Read 65 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Friday, October 27, 2006 11:29 AM

At 08:32 AM 10/27/2006, you wrote:
>>What should I call it?
>>
>>"Wildfile GUI" ?
>
>I have been calling it "Wildfile for Windows".
>Of course that is quite a long name, and not very cool.

Or I could call it simply "Wildfile" and change the command version in {MISC, More macros} to "Wildfile command".

Ted.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (23 of 44), Read 66 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, October 30, 2006 09:15 AM

On 10/27/2006 11:29:29 AM, Ted Green wrote:
>
>Or I could call it simply "Wildfile" and change the
>command version in {MISC, More macros} to "Wildfile command".

Why not. But then the filenames should be changed, too.
Now the command line version is wildfile.vdm.

--
Pauli

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (24 of 44), Read 72 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, December 11, 2006 12:01 PM

Hi,

Here is a new version (V1.4) of Wildfilew.vdm.
Perhaps this is the final version for now, unless some bugs are found.

Changes:

- Added search option "List filenames only".

- [View] button now toggles search.tmp display on/off.

- Search.tmp is now stored in the same dir as .ini file (default user-mac dir).
This is because in vedit_temp directory it was deleted on boot.
In addition, this allows multiple search results to be stored.

- You can now choose the .ini file.
Put the name of the file in text register 40 and then call label "set_ini".
Or call label "read_ini" if you want not to save the changes in .ini file.
(Note: normally the .ini file is always saved, so you will lose any comments you may have in the file)

Example:
RS(40,"mywf.ini") Call_File(100,"wildfilew.vdm","set_ini")

This is mainly intended for calling wildfilew.vdm from command line or .bat file, but you can for example put the commands in User menu so that you can have different settings for some special purpose.

- Wildfilew.vdm can now be called from command line or .bat file. So you do not need to use wildfile.vdm and input redirection to automate your editing tasks.
If you have setting opt_dialog=0 in the .ini file, the dialog boxes are not displayed and wildfilew.vdm is executed automatically using the settings from the .ini file.

Example of command line:
c:\vedit\vpw -q -c'RS(40,"mywf.ini") Call_File(100,"wildfilew.vdm","read_ini")'

There is, however, a problem with -q option (quiet). With -q option, the macro does not perform the operation ordered. I wonder what causes this.

- Wilfilew.vdm is now compatible with tutor macro.
I have included tutor file T-WILDF.VDM in the zip package, together with files wf_search.ini and wf_command.ini that it uses. Copy them to the tutor directory (perhaps after renaming the old file for backup).

To run the tutorial, select Help -> Tutorial -> Multi file processing.

This is just a quick example. Someone who is native English speaker should check the texts. And I have not changed the texts in the first and last dialog at all.

In addition, the zip package contains a new version of search116.vdm.
It now highlights the searched text in the target file when you double click a line in search.tmp. Further, I added some check for valid filename so that the macro doesn't try to load a file if you for example click on the top three lines.

New version of search.syn now highlights the search count values (on the 2nd row) with numeric color.

The example macro count2.vdm has some bugs fixed. End dialog was not displayed when called directly (instead of from wildfilew.vdm). Word and Case options did not work (it appears that SR_set() resets search options).


--
Pauli

 
WILDFILEW104.ZIP (22KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (25 of 44), Read 66 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, March 02, 2007 07:32 AM

Here is new version of wildfilew.vdm, v1.5.
Only some small changes have been made.

- Fixed a bug that was introduced in previous version when I added check for read-only attribute in the .ini file.
If .ini file did not exist, it was not created. Now the existence of .ini file is checked before checking attributes.

- When performing replace with confirm, and user selects ALL in the confirm prompt, the number of changed lines is not displayed in the end dialog since the value would be incorrect.

- Added some more hotkeys in dialog boxes.


I tried to fix the syntax highlight problem by adding EVENT option in Buf_Switch commands, but it didn't help, so I removed them again.
(The problem of losing the correct syntax highlight after running a macro has been in Vedit quite a while, but with wildfilew.vdm it has become more prominent since it happens almost every time.)

--
Pauli

 
WILDFILEW105.ZIP (16KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (26 of 44), Read 64 times
Conf: Wildfile, Other macros
From: Ian Binnie
Date: Friday, March 02, 2007 06:04 PM

On 3/2/2007 7:32:56 AM, Pauli Lindgren wrote:
>Here is new version of
>wildfilew.vdm, v1.5.
>Only some small changes have
>been made.
>
>I tried to fix the syntax
>highlight problem by adding
>EVENT option in Buf_Switch
>commands, but it didn't help,
>so I removed them again.
>(The problem of losing the
>correct syntax highlight after
>running a macro has been in
>Vedit quite a while, but with
>wildfilew.vdm it has become
>more prominent since it
>happens almost every time.)
>

Pauli,

Thanks, I have downloaded the new version.
I have been using your previous version as my standard, which has overcome my previous dislike of wizards.

I actually tried to steal your syntax highlighting for found strings, and graft it into srchshow, but found it did not always work.

Even for normal syntax highlighting, I have found problems, and it is necessary to force a screen refresh to get it to work.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (27 of 44), Read 66 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Friday, March 02, 2007 06:11 PM

At 07:34 AM 3/2/2007, you wrote:
>Here is new version of wildfilew.vdm, v1.5.
>Only some small changes have been made.

Thank you. I will make it the wildfwiz.vdm replacement and am running it now.

>I tried to fix the syntax highlight problem by adding EVENT option in Buf_Switch commands, but it didn't help, so I removed them again.
>(The problem of losing the correct syntax highlight after running a macro has been in Vedit quite a while, but with wildfilew.vdm it has become more prominent since it happens almost every time.)

Hmmm, I seem to have overlooked any previous bug reports of this.

Ted.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (28 of 44), Read 69 times
Conf: Wildfile, Other macros
From: Christian Ziemski
Date: Saturday, March 03, 2007 04:48 PM

On Fri, 02 Mar 2007 07:32:00 -0500, Pauli Lindgren wrote:

>Here is new version of wildfilew.vdm, v1.5.

Pauli:

In the replace dialog always the input box for the "replace string"
has the initial focus.

That is o.k. if there is a search string.
But if there is no search string yet the user usually(?) will type in
the search string first (at least I will do).

So please let me suggest the following:

To set the focus dependent on the existence of a search string
something like this can be done:


(Lines 552 ff.)

// Addition by CZ
// to let the Search string input box have the focus if there
// is no search string preset
Reg_Push(105,106)
if (Reg_Size(#93)) {
Reg_Empty(105)
Reg_Set(106, ".i")
} else {
Reg_Set(105, ".i")
Reg_Empty(106)
}
// (and added |@(10x) below at Search and Replace input box)
// End CZ

#75 = DI1(#91,^`Wildfile for Windows - Search & Replace`,
`Enter list of filenames to process, separated by commas.
The wildcards "?" and "*" may be used.`,
`??&Files: `,
`??&Directory:`,
`[]Search s&ubdirectories`,`.h.r[Browse]`,
`|@(105)??&Search: `,
`|@(106)??&Replace: `,
`[]&Case sensitive `,
`.h[]&Word `,
`.h[]S&kip comments`,
`Search mode: \t\t Display matched lines as:`,
`.l.g()S&imple`,
`()Pa&ttern`,
`()Regular &Expressions `,
`()Reg-Exp (M&ax)`,
`.g.h.l()Co&nfirm each replace`,
`()&List matched lines/filenames`,
|@(103)^,
APP+CENTER+TOP+SET,0,107)

Reg_Pop(105,106) // added by CZ
}


Christian

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (29 of 44), Read 63 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, April 23, 2007 11:21 AM

I recently needed o run my parenthesis checker macro on large number of .c and .h files (some 4400 files).
For that, I had to do some changes to Wildfilew.vdm. So, here is new version again, v1.6.
It contains the following changes:

- User macro can now use search.tmp to list it's output.
When "Macro" operation is selected, search.tmp is opened (in buffer pointed by #61).
If the user macro does not use search.tmp, it is silently closed and it's contents are not changed.
If the user macro needs to use the file, it has to empty it on the first call.
After all the files have been processed (#98==2), user macro should set bit 4 (mask 0x10) on register #98. Wildfilew will then save search.tmp but leave it open.

- User macro can now instruct Wildfilew to leave the processed file open, by setting bit 3 (mask 0x08) on #98.
This can be used for example when error checker macro has found an error in the file. Bit 1 (mask 0x02) should be also set, since currently Wildfilew can not correctly leave multiple files open.

Here is summary of the usage of numreg #98:

Wildfile sets:
0x00 = First call to user macro (Wildfile resets #98 at the beginning)
0x02 = Last file being processed

User macro sets:
0x01 = First call done (set by user macro if needed)
0x02 = Stop processing more files
0x04 = Do not show end dialog
0x08 = Do not close current file
0x10 = Search.tmp was used, do not close it.

Other changes:

- Christians changes on selecting input focus in Replace dialog.

- Fix: "Skip comments" option interpreted //* as block comment, and thus some occurrences were not found.

- Do not close search.tmp when Cancel button is clicked.

- Numreg #60 now contains number of files to process before starting the actual processing.
(My c_paren.vdm uses this to warn user if very large number of files was selected.)

--
Pauli

 
WILDFILEW106.ZIP (19KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (30 of 44), Read 68 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, April 23, 2007 11:37 AM

Forgot to mention.
The file wildfilew106.zip includes my parenthesis checker macro, c_paren.vdm, as an example of how to use the new features.

C_paren.vdm checks that parenthesis ()[]{}, block comments /*...*/ and #if's have matching pair in C language files.

You can call the macro directly, in which case it checks the current file starting from current cursor location.

If you call the macro from Wildfilew.vdm, it checks all the files from the beginning. Before checking the first file, it pops up dialog box where you can select if you want to list all the errors into search.tmp, or if you want to stop on first error (in which case the cursor points exactly the error location).

In addition, the .zip packet contains a new version of count2.vdm, since the usage of register #98 has changed a bit.

--
Pauli

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (31 of 44), Read 63 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, September 24, 2007 02:54 PM

Here is new version of Windfilew.vdm, v1.7.

The main change is that it uses HTML Help to display help info. The help file is wildfilew.chm.
This is not finished version of the help, I made it mainly to test HTML Help.

The help has some context sensitivity.
If you click Help at Search or Replace dialog, the main help page is displayed.
But if you click Help at Command, Macro or Options dialog, the help for that dialog is displayed.

On different help pages, somewhat different formatting has been used.
On some pages, I have used HTML form objects (buttons, checkboxes etc.) to display corresponding items in Wildfilew dialog.
On some pages, GIF's are used, and on some pages, just text representation of the controls.
I don't know which method is the best.


In addition to that, only some small changes have been made.

- I Expanded Christians initial idea of selecting which input field has focus.
If 'Files' field is empty, it will have the initial focus, otherwise 'Search' or 'Replace' field has focus as before.
Registers 104 to 106 are not pushed, since they are tmp regs anyway.

- Some fixes in the situation when user macro asks to keep the searched file open.


--
Pauli

 
V 1.7

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (32 of 44), Read 57 times, 2 File Attachments
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Thursday, December 06, 2007 05:31 PM

Here is the latest version of Wildfilew.vdm, V1.08.
I wasn't going to publish this yet, since there are not so many changes since v1.07, but if new version of Vedit is going to be released, I guess this could be included with it.

The main change is that "skip comments" option can now support other languages than just C.
You can specify the line comment and block comment delimiters by adding the following lines in wildfilw.ini:

linecmt=//
comment=|{/*,*/}

The above example is for C language which is the default.

Currently, the only way to change the comment delimiters is to edit wildfilw.ini.
You could, of course, have multiple .ini files for different languages.
If the project directory variable is implemented in Vedit, then you could have different settings for each project.
Maybe I will later try to implement automatic setting based on file name extension.


Another change is that search.syn now uses symbol color to highlight search string when it is not full word.

Some other minor changes have been done for the case when Wildfilew.vdm is called from another macro.

In addition, I have updated the help and added couple of new pages. The new wildfilew.chm is included in the .zip file.

The html sources for the help are in another zip package, wildfilew_help.zip.

--
Pauli

 
Help source files
  WILDFILEW108.ZIP (66KB)

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (33 of 44), Read 55 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Thursday, December 06, 2007 05:38 PM

At 05:33 PM 12/6/2007, you wrote:
>From: "Pauli Lindgren"
>
>Here is the latest version of Wildfilew.vdm, V1.08.
>I wasn't going to publish this yet, since there are not so many changes since v1.07, but if new version of Vedit is going to be released, I guess this could be included with it.

Great. That is an important macro I wanted to include in the new VEDIT.

Ted.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (34 of 44), Read 56 times
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Friday, December 07, 2007 10:32 AM

On 12/6/2007 5:38:26 PM, Ted Green wrote:
>
>Great. That is an important
>macro I wanted to include in
>the new VEDIT.

Wildfilew.vdm is now assumed to be in user-mac directory, and that is where the .ini and help files are loaded. Should these be moved to macro directory?

What about the name of the macro? Maybe the filename can be what it is, but should the Help (and the Wildfilew dialogs) just refer to "Wildfile" as the general function that has two implementations, Windows and DOS versions?

The menu-item mentioned in help is still Wildfile Wizard. Will that be changed (and perhaps moved to Search menu)? That needs then to be updated in help.

Don't forget to include the double-click macro search116.vdm, search.syn file and the example macros count2.vdm and c_paren.vdm (they are mentioned in help) in the distribution.

--
Pauli

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (35 of 44), Read 57 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Friday, December 07, 2007 10:42 AM

At 10:39 AM 12/7/2007, you wrote:
>Wildfilew.vdm is now assumed to be in user-mac directory, and that is where the .ini and help files are loaded. Should these be moved to macro directory?

Yes, I will distribute it in the /vedit/macros directory.

>What about the name of the macro? Maybe the filename can be what it is, but should the Help (and the Wildfilew dialogs) just refer to "Wildfile" as the general function that has two implementations, Windows and DOS versions?
>
>The menu-item mentioned in help is still Wildfile Wizard. Will that be changed (and perhaps moved to Search menu)? That needs then to be updated in help.

I may rename things a bit. Moving to the Search menu does sound like a good idea!

>Don't forget to include the double-click macro search116.vdm, search.syn file and the example macros count2.vdm and c_paren.vdm (they are mentioned in help) in the distribution.

OK thanks.

Ted.

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (36 of 44), Read 60 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Saturday, January 05, 2008 05:16 PM

At 05:33 PM 12/6/2007, you wrote:
>From: "Pauli Lindgren"
>
>Here is the latest version of Wildfilew.vdm, V1.08.
>I wasn't going to publish this yet, since there are not so many changes since v1.07, but if new version of Vedit is going to be released, I guess this could be included with it.

Pauli:

This is certainly a fantastic macro and great enhancement!

I do have a few thoughts on the buttons though. Primarily, I think that the [Help] button should always be visible. You KNOW how it works (!), but a new user will not, and hitting [More] to see get [Help] is not obvious. Your on-line help is so fantastic we should hide it!

Also, when showing all buttons, [Ok] and [SEARCH] do the same thing and [Replace...] and [Replace] do the same thing. Therefore, perhaps the initial buttons should be:

[OK] [Cancel] [Replace...] [Help] [More >>]

and all the buttons are:

[OK] [Cancel] [Replace...] [Help] [More >>]
[View] [Options] [Command] [Macro]

or if you like:

[OK] [Cancel] [Replace...] [Help] [Less <<]
[View] [Options]
Additional operations:
[Command] [Macro]

----

I was thinking of putting the new wildfilew.vdm into the /vedit/macros directory and help files into a new directory /vedit/macros/wildfile.

As I need to release a new VEDIT 6.15.2 in 2-3 days, I may need more time to include this macro.

Ted.





>The main change is that "skip comments" option can now support other languages than just C.
>You can specify the line comment and block comment delimiters by adding the following lines in wildfilw.ini:
>
>linecmt=//
>comment=|{/*,*/}
>
>The above example is for C language which is the default.
>
>Currently, the only way to change the comment delimiters is to edit wildfilw.ini.
>You could, of course, have multiple .ini files for different languages.
>If the project directory variable is implemented in Vedit, then you could have different settings for each project.
>Maybe I will later try to implement automatic setting based on file name extension.
>
>
>Another change is that search.syn now uses symbol color to highlight search string when it is not full word.
>
>Some other minor changes have been done for the case when Wildfilew.vdm is called from another macro.
>
>In addition, I have updated the help and added couple of new pages. The new wildfilew.chm is included in the .zip file.
>
>The html sources for the help are in another zip package, wildfilew_help.zip.
>
>--
>Pauli
>
>
>
>
>--
>Attachment:
>http://.../upload/wildfilew108.zip (66KB)
>
>
>http://.../upload/wildfilew%5Fhelp.zip (58KB)
>Help source files
>
>
>To reply: mailto:vtech-macros.39983@...
>To start a new topic: mailto:vtech-macros@...
>To login: http://...
>To (un)subscribe: mailto: vtech-macros.list-request@...

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (37 of 44), Read 72 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, January 07, 2008 10:53 AM

On 1/5/2008 5:16:20 PM, Ted Green wrote:
>
>I do have a few thoughts on
>the buttons though. Primarily,
>I think that the [Help] button
>should always be visible. You
>KNOW how it works (!), but a
>new user will not, and hitting
>[More] to see get [Help] is
>not obvious. Your on-line help
>is so fantastic we should hide
>it!

I have been thinking about this, too.
And the View button should be always visible, too, in order to be usable.

The easiest way would be to include the first two rows of buttons in simple dialog. But then the full dialog would only have one row of buttons more.


>
>Also, when showing all
>buttons, [Ok] and [SEARCH] do
>the same thing and
>[Replace...] and [Replace] do
>the same thing.

No. [OK] button starts the operation. [Search] button selects search dialog.

Having both [Search] and [Replace] buttons on bottom row is a little bit redundant, since you can use the [Search]/[Replace] toggle button after entering Search mode. But they can not both be removed, since then you would not have any means to go to search/replace dialog from Command or Macro dialog.

I have been thinking of Removing [Replace] button from bottom row and then add [File Find] as fourth operation button. (I have currently implemented File Find as a separate macro that calls Wildfilew.vdm, but calling Wildfilew from outside does have some problems. Or maybe best solution would be to create an independent macro for file find.)


> Therefore, perhaps the initial buttons
>should be:
>
>[OK] [Cancel] [Replace...] [Help] [More >>]
>
>and all the buttons are:
>
>[OK] [Cancel] [Replace...] [Help] [More >>]
>[View] [Options] [Command] [Macro]
>
>or if you like:
>
>[OK] [Cancel] [Replace...] [Help] [Less <<]
>[View] [Options]
>Additional operations:
>[Command] [Macro]

I don't like the idea of having 5 buttons on a row.
That makes the dialog much bigger, and the other rows would be half empty. In addition, it would be difficult to keep the dialog width unchanged when you switch from one operation to another.

The idea of the bottom row buttons is that they act like tabs (since DI1 does not support tab component). For smooth operation while clicking buttons, it is important that the buttons stay at same position instead of jumping around.

>----
>
>I was thinking of putting the new wildfilew.vdm into the
>/vedit/macros directory and
>help files into a new directory /vedit/macros/wildfile.

Or maybe there should be a help directory where all the help files would be located? I have already made help for ctags, and maybe some other macros will eventually have individual help files, too.

>
>As I need to release a new VEDIT 6.15.2 in 2-3 days, I
>may need more time to include this macro.

Wildfilew.vdm is quite a big change, so maybe it should be released with 6.2? But when is 6.2 going to be released? Are there still some problems with ftp?

Anyway, if the buttons are changed, the help file need to be updated, including all the pictures, so it is quite a work.

I made couple of test versions of wildfilew: one with 5 buttons on the first row, and another one where first 2 button rows are displayed in simple dialog. They can be found in the enclosed .zip file.


--
Pauli

 
Button test versions

 


Topic: Re: New Wildfile for Windows (wildfilew.vdm) (38 of 44), Read 83 times
Conf: Wildfile, Other macros
From: Ted Green
Date: Monday, January 07, 2008 04:13 PM

At 11:17 AM 1/7/2008, you wrote:
>From: "Pauli Lindgren"
.... (lots)
>Wildfilew.vdm is quite a big change, so maybe it should be released with 6.2? But when is 6.2 going to be released? Are there still some problems with ftp?

I am going to release a 6.15.2 this week.

I would like to release your new wildfile as ASAP, perhaps as 6.16 in two weeks. I will also put the "Wildfile" into the {SEARCH} directory as you suggested.

I like the idea of creating a /vedit/help directory as I would like to put fewer files into the /vedit directory.

I will check out your revised button layout tomorrow.

Ted.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (39 of 44), Read 42 times, 2 File Attachments
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Monday, June 23, 2008 02:23 PM

Here is new version of Wildfilew.vdm, V1.09.

In this version, the "simple" dialog contains the first two rows of buttons, i.e. buttons View, Options and Help are always displayed.

In the "full" dialog, a row of radio buttons has been added for selecting Search Number.
With these you can choose the output file for search results so that new search does not overwrite the previous results.

By default, search number 1 is selected. In this case, the results are stored in file search.tmp, as before. If you select 2, 3, etc., the results are stored in search2.tmp, search3.tmp, etc., respectively.

If one of the search results files is the current file when you start wildfilew.vdm, that search number is selected as default.

You can view the selected search results file by choosing a radio button and then clicking the View button.

Each search number has an associated syntax highlight file created in user-mac directory (search1.syn, search2.syn etc.). This allows the correct search string to be highlighted on each search results display. The file search.syn in Vedit home directory is used as template when creating the syntax files and it is not modified.

Note: There is a bug in Vedit in the radio buttons. Looks like Vedit splits radio buttons group after 10th button. This means that after search number 2, a new radio button group begins. If you select buttons 3 to 5, button 1 or 2 remains selected on the display. It is still possible to select any search number, but if you select any of the buttons 3 to 5, you can not select button 1 or 2 again.

Other changes:

- Number of files processed is displayed in search results.

- When running in batch mode and no files found, does not display a dialog but instead exits.

- Wildfilew.vdm returns number of files processed in Return_Value.

- If |{} pattern is used in search string, it is removed when creating syntax file to allow multiple words to be highlighted.

- Fix: registers #93,#94 were not popped in case no files found.


SEARCH116.VDM has been changed to accept any file "search*.tmp" as search results file.
In addition to using search1.tmp, search2.tmp created by wildfilew.vdm, you can manually save the search results file to other name that matches this pattern, perhaps to another directory, and you can still use double-click.

Another enhancement is that you can now select a C block (inside {}) by holding Ctrl+Shift keys while double-clicking inside the block.
To select the whole function, if-block, or loop, hold Alt+Shift keys while double-clicking anywhere before the '{' character. That highlights the block starting from beginning of the line and ending after the matching '}' character. (Note, however, that Alt-Shift key combination may have been configured to switch keyboard layout on Windows XP.)

The help file has been updated, too. In addition to the changes mentioned above, the help now has a new page about the .ini file. The compiled help file wildfilew.chm is included in the file wildfilew109.zip. The HTML source files are in the file wf_help109.zip.

--
Pauli

 
Help source files
  Wildfile v1.09

 


Topic: New Wildfile for Windows (wildfilew.vdm) (40 of 44), Read 42 times
Conf: Wildfile, Other macros
From: Paul Breen
Date: Sunday, July 06, 2008 01:19 PM

I have apparently done something wrong installing.
I get a message
"DIRECTORY NOT FOUND:Files\vedit\user-mac"
When I run wildfilew.vdm
I think the problem is the space in
"C:\program files\vedit\user-mac"
but I don't know how to fix this. The old wildfile ran
fine.
thanks,

 


Topic: New Wildfile for Windows (wildfilew.vdm) (41 of 44), Read 60 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Wednesday, July 09, 2008 11:35 AM

On 7/6/2008 1:19:17 PM, Paul Breen wrote:
> I get a message
> "DIRECTORY NOT FOUND:Files\vedit\user-mac"
> When I run wildfilew.vdm
> I think the problem is the space in
> "C:\program files\vedit\user-mac"
> but I don't know how to fix this.
> The old wildfile ran fine.

By "old wildfile", I guess you mean wildfile.vdm or wildfwiz.vdm?
The file open commands in wildfilew.vdm have not changed recently.

I made a test install of Vedit in "program files" directory.
Indeed, the error is displayed when the macro tries to open the .ini file.
Since the pathname contains spaces, double quotes are needed around the filename.

Here is new version of Wildfilew.vdm (v1.10), where the problem should be fixed.
I changed all commands such as
File_Open(@40,OVERWRITE+NOMSG+NOEVENT)
into
File_Open(*"|@(40)"*,OVERWRITE+NOMSG+NOEVENT)

I hope all the file commands are OK, I haven't tested it fully.

There is another small change in this version.
I added LOCAL option in the search command in CHECK_COMMENT routine. This speeds up the operation in case "skip comments" option is set and the file does not contain any comments.
(I am not sure if this could cause some comment delimiters to be missed, since I don't know exactly how the file buffering in Vedit works.)

The zip package contains only wildfilew.vdm. Get the other required files from v1.09 package.

--
Pauli

 
WILDFILEW110.ZIP (17KB)

 


Topic: New Wildfile for Windows (wildfilew.vdm) (42 of 44), Read 24 times
Conf: Wildfile, Other macros
From: Howard Goldstein
Date: Tuesday, November 30, 2010 09:01 PM

Well, it's only been about a year and a half but I finally decided to try this macro. I'm running version 1.10, (is that the latest?), in VEDIT 32-Bit version 6.15.2 installed in Program Files under Windows XP and I'm having a problem when I do a search with display mode set to "visual / edit." When a file containing the search string is displayed, I'm not allowed to make any changes. Whenever I type a character I'm told that I'm in browse mode or that the file is read-only. Once this has happened, pressing Visual Exit breaks out immediately rather than moving on to the next file. I'd appreciate some help resolving this. Thanks.

 


Topic: New Wildfile for Windows (wildfilew.vdm) (43 of 44), Read 33 times, 1 File Attachment
Conf: Wildfile, Other macros
From: Pauli Lindgren
Date: Sunday, December 12, 2010 05:21 PM

On 11/30/2010 9:01:16 PM, Howard Goldstein wrote:
>
> I'm running version 1.10, (is
> that the latest?),

There was v1.11, but I only sent it to Ted.

> I'm having a problem when I do a
> search with display mode set
> to "visual / edit." When a
> file containing the search
> string is displayed, I'm not
> allowed to make any changes.
> Whenever I type a character
> I'm told that I'm in browse
> mode or that the file is
> read-only. Once this has
> happened, pressing Visual Exit
> breaks out immediately rather
> than moving on to the next
> file. I'd appreciate some
> help resolving this. Thanks.

The problem is that the searched files are opened in browse mode in order to speed-up the search. I rarely use visual mode, so I did not notice that problem until recently.

On version 1.12, attached with this message, this has been fixed. When search is performed in Visual mode, all the files are opened in read/write mode and with events enabled (so that syntax highlighting is visible).

Changes from v1.10 to 1.11:

- Does not overwrite but updates wildfilw.ini, so that comments etc. are retained in the file.
- Check for empty search string when OK clicked.
- Check if directory exists when Browse or OK clicked
- Full dialog box: only 2 operation select buttons. Does not show buttons for currently displayed dialog.
- Help text "Double click..." displayed in search results window (if enabled).
- Added "Help level" setting in Options dialog. Combined "Dialog type" with "Start at" setting.

Changes from v1.11 to 1.12:

- If "Visual" search selected, open files in R/W mode.
- Dialog boxes relative to APP, not SCREEN so that they are displayed on correct monitor in dual-monitor systems.
- Help file in HOME directory, ini-file in USR-CFG directory
- Wildfilw.ini renamed to wildfilew.ini, search116.vdm to wildfilew-src.vdm.

To install this version of Wildfilew.vdm, unzip the files either in your user-mac directory or macros directory.
Then move wildfilew.chm and search.syn into Vedit home directory.

--
Pauli

 
Wildfilew.vdm V1.12

 


Topic: New Wildfile for Windows (wildfilew.vdm) (44 of 44), Read 35 times
Conf: Wildfile, Other macros
From: Howard Goldstein
Date: Monday, December 13, 2010 09:40 PM

Pauli,

1.12 is working great. Thanks!

I would like to make one more request. Please consider adding a search tab in the CHM file. Here's why. I am blind and use a screen reader to access my computer. I do not use a mouse; everything is done from the keyboard. When I read a help file, I like to be able to toggle focus between the table of contents treeview and the actual text. Pressing F6 does this in most CHM files, but not in simple ones like yours that don't have tabs on top. Well, actually F6 works once, switching focus to the text, but then there's no easy way to get back to the TOC using only the keyboard -- in Windows XP at least. So even though I'd almost never actually use the search feature, just having it there would make the help file much easier to navigate from the keyboard.

-- Howard