Topic: Dashboard v3.0 (1 of 13), Read 42 times, 1 File Attachment
Conf: VEDIT Macro Library
From: Scott Lambert
Date: Saturday, July 02, 2011 12:00 PM


Attached is Dashboard v3.0.

It now tells that path of the vedit exe file, and also the file backup option select (copy to vedit\backup, copy to .bak, off)


Scott

 
DASHBOARD(2).VDM (6KB)

 


Topic: Re: Dashboard v3.0 (2 of 13), Read 41 times
Conf: VEDIT Macro Library
From: Ted Green
Date: Saturday, July 02, 2011 12:49 PM

----- Original Message -----
> From: "Scott Lambert" ( scottmacros@... )
> Attached is Dashboard v3.0.
>
> It now tells that path of the vedit exe file, and also the file
> backup option select (copy to vedit\backup, copy to .bak, off)

Excellent. Could you please also let it leave the output on the screen (in addition to saving it in a file). This way the user can easily copy it to the clipboard and then email it to us. We will then ask users to do this for all tech support requests. I will add it to the {HELP} menu.

Thank you!

Ted.

 


Topic: Re: Dashboard v3.0 (5 of 13), Read 33 times
Conf: VEDIT Macro Library
From: Scott Lambert
Date: Sunday, July 03, 2011 12:24 PM

On 7/2/2011 12:49:10 PM, Ted Green wrote:
>----- Original Message -----
>> From: "Scott Lambert" ( scottmacros@... )
>> Attached is Dashboard v3.0.
>
>Excellent. Could you please
>also let it leave the output
>on the screen (in addition to
>saving it in a file). This way
>the user can easily copy it to
>the clipboard and then email
>it to us. We will then ask
>users to do this for all tech
>support requests. I will add
>it to the {HELP} menu.
>
>Thank you!

Hi Ted,

I must be mis-understanding what you want. At least on my copy, when the macro ends, the user is looking at the report. It does leave it on the screen, and I am using the same version of macro as I uploaded.

I am happy you find it useful.

Scott

 


Topic: Re: Dashboard v3.0 (6 of 13), Read 27 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Friday, July 15, 2011 05:13 AM

Scott,

A big thank you for Dashboard Version 3.00.

I have downloaded the new Vedit 6.21.1 and did run it from the {Help,Dashboard} menu.

In short, it runs like a charm!

I also tried to run it from my Version 6.15 Vedit Home directory. Of course it did not find the config string,
USER_HOME_DIRECTORY. So, it stopped.

I glanced at your macro and have a hunch that it would be easy to sort out the config strings according to version numbers. It is great that Ted is adding predefined strings in each new version ! Or may be just say that this string is empty in this version ? I just do not know.

Incidentally, Dashboard refers to folders and not directories. Is this on purpose ?


Now a self-survey.

One of my favorite macros is to launch a new copy of Vedit and go to a given line number. Since my MikTex previewer, Yap.exe does the job for me and since it is late I do not know the specifics. I do not know how to handle the Vedit instance parameter either. I did it by trial and error.

So, for me it would be great if I could do this in a systematic manner. In other words, it would be great if Dashboard would tell me the instance parameter. I looked up
the topic Running Multiple Instances Of Vedit in the Version 6.15 On Line Help. So this is the parameter I am interested in.


Oops. Since I plan to run Dashboard for different installations I will have many report files. So I would like to add the minutes and may be the seconds to the time stamp. Then, I would like to append each new report to the old one.

PS. I did put a simple macro on my USER_MENU, which calls the Vedit Config_String command. May be a possible option would be to redirect the result to the Dashboard report ?

Thanks again,


-peter

 


Topic: Re: Dashboard v3.0 (7 of 13), Read 27 times
Conf: VEDIT Macro Library
From: Scott Lambert
Date: Friday, July 15, 2011 10:40 AM

On 7/15/2011 5:13:36 AM, peter rejto wrote:
>Scott,
>
>A big thank you for Dashboard
>Version 3.00.
>

You are welcomed.

>
>I also tried to run it from my
>Version 6.15 Vedit Home
>directory. Of course it did
>not find the config string,
>USER_HOME_DIRECTORY. So, it
>stopped.

Easiest way to fix that is on your 6.15 version, comment out the following lines:

ins_text("User HOME folder location: ")
ins_text(USER_HOME)
ins_newline(2)


>Incidentally, Dashboard refers
>to folders and not
>directories. Is this on
>purpose ?

As I understand it, under windows, you refer to directories as folders. It is only under the command prompt you refer to them as directories.

>
>

>So, for me it would be great
>if I could do this in a
>systematic manner. In other
>words, it would be great if
>Dashboard would tell me the
>instance parameter.

I found the correct config command:

Config( U_INSTANCES, "Instances control (0=Auto, 1=One,2=Multiple)", 1 )

Would you also need the Process ID (string PID)?

>
>Oops. Since I plan to run
>Dashboard for different
>installations I will have many
>report files. So I would like
>to add the minutes and may be
>the seconds to the time stamp.
>Then, I would like to append
>each new report to the old
>one.

Yes, appending to an existing report is certainly possible. Perhaps dashboard could ask for a name for the report, so you could type in something like:

v6.15 report July 22/11 10:05 am

This would help you remember the conditions each report was generated under.

Comments?

Scott

 


Topic: Re: Dashboard v3.0 (8 of 13), Read 28 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Friday, July 15, 2011 11:18 AM

On 7/15/2011 10:40:32 AM, Scott Lambert wrote:

>>I also tried to run it from my
>>Version 6.15 Vedit Home
>>directory. Of course it did
>>not find the config string,
>>USER_HOME_DIRECTORY. So, it
>>stopped.
>
>Easiest way to fix that is on your 6.15
>version, comment out the following
>lines:
>
>ins_text("User HOME folder location: ")
>ins_text(USER_HOME)
>ins_newline(2)

Aha, so these are the version 6.2 Config Strings.


>
>>So, for me it would be great
>>if I could do this in a
>>systematic manner. In other
>>words, it would be great if
>>Dashboard would tell me the
>>instance parameter.
>
>I found the correct config command:
>
>Config( U_INSTANCES, "Instances control
>(0=Auto, 1=One,2=Multiple)", 1 )
>
Great !

>Would you also need the Process ID
>(string PID)?

Yes, if possible.

At present all that I know is that Yap.exe issues the command

c:\vedit\vpw.exe -cGoto_Line(%l)%f

Here as per the yap manual, %l is the place holder for the line number and %f is the place holder for the file name.
I did put in the rest.


>Yes, appending to an existing report is
>certainly possible. Perhaps dashboard
>could ask for a name for the report, so
>you could type in something like:
>
>v6.15 report July 22/11 10:05 am
>
>This would help you remember the
>conditions each report was generated
>under.

This would be nice.

>Comments?


Thanks again,

-peter

 


Topic: Re: Dashboard v3.0 (11 of 13), Read 7 times
Conf: VEDIT Macro Library
From: Pauli Lindgren
Date: Sunday, July 17, 2011 09:21 AM

On 7/15/2011 10:40:32 AM, Scott Lambert wrote:
>
>Yes, appending to an existing report is
>certainly possible. Perhaps dashboard
>could ask for a name for the report, so
>you could type in something like:
>
>v6.15 report July 22/11 10:05 am

I would not want to type in a filename when executing dashboard. It would only make it more difficult to use.
If you want to give the file another name, you can always manually save the file with a new name.

I don't know why anybody would want to append a new report at the end of old one. But if someone does, that can be done simply by copy-pasting the new report to the end of the old report.

--
Pauli

 


Topic: Re: Dashboard v3.0 (12 of 13), Read 8 times
Conf: VEDIT Macro Library
From: Scott Lambert
Date: Sunday, July 17, 2011 09:32 AM

On 7/17/2011 9:21:17 AM, Pauli Lindgren wrote:
>On 7/15/2011 10:40:32 AM, Scott Lambert
>wrote:
>>
>
>I would not want to type in a filename
>when executing dashboard. It would only
>make it more difficult to use.
>If you want to give the file another
>name, you can always manually save the
>file with a new name.

It worked out in the end to be a report subtitle, so Peter could add remarks concerning the conditions the report was generated under.


>I don't know why anybody would want to
>append a new report at the end of old
>one.

Ask Peter, he is the one that asked for it. I don't ask why, I just code what people want...

Scott

 


Topic: Re: Dashboard v3.0 (13 of 13), Read 8 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Sunday, July 17, 2011 11:59 AM

On 7/17/2011 9:32:18 AM, Scott Lambert wrote:
>On 7/17/2011 9:21:17 AM, Pauli Lindgren
>wrote:
>>On 7/15/2011 10:40:32 AM, Scott Lambert
>>wrote:
>>>
>>
>>I would not want to type in a filename
>>when executing dashboard. It would only
>>make it more difficult to use.
>>If you want to give the file another
>>name, you can always manually save the
>>file with a new name.
>
>It worked out in the end to be a report
>subtitle, so Peter could add remarks
>concerning the conditions the report was
>generated under.
>
>
>>I don't know why anybody would want to
>>append a new report at the end of old
>>one.
>
>Ask Peter, he is the one that asked for
>it. I don't ask why, I just code what
>people want...
>
>Scott

Hi,

I am in the process of migrating from my USTART.VDM to an adaptation of Pauli's PRESET.VDM. I have reported on my efforts in the Installation, Configuration Conference. Specifically, at webboard.vedit.com/read?6732.31

At present I did hit a snag. Specifically, the User Auto macro that I presented there does not restore my original {USER} and {TOOL} menus if I start a new instance of Vedit.

So, I thought to experiment with these parameters. Therefore, it is very useful for me to have written records of these parameter experiments. Appending the report to the old file is one way to keep track of my experimental parameters. It has the advantage that there is only one file and I can use Vedit to search it.

Oops, I just thought of another option: If my experiments did not go anywhere, then I would like to have the option of not reporting at all. In short automating these parameter experiments and managing the resulting data base are two contradictory requirements. I just do not know what is the optimal solution.

I vaguely remember that Pauli mentioned that he does not wish to type in a file name. I agree with him. I wish to use Dashboard as an aid to automate my experiments with the parameters of my User Auto macro. So, most of the time I just would like to press the key. however, if I am lucky and come with a good result, I would like to have the option of saving that file under a specific name.

I also would like to mention that I modeled this on my Seatools program, which is a Seagate diagnostic program.

Last time my Harddisk failed to respond, I used Seatools and learned that my Harddisk parameters did not change. So, I concluded that I have a software issue. Sure enough, reinstalling Windows did solve my problem.

PS: I am fascinated by the ongoing discussion of Vedit 6.21.1. Since I am not a programmer, most of it is above my head. However, I have a hunch that there are many special cases that I could use. So, recently, I have not done any experiments with my User Auto macro.

Thanks for everything.

-peter

 


Topic: Dashboard-PR v1.0 (9 of 13), Read 26 times, 1 File Attachment
Conf: VEDIT Macro Library
From: Scott Lambert
Date: Friday, July 15, 2011 02:24 PM


Hi Peter,

Attached is a version of Dashboard called Dashboard-PR (one guess what PR stands for...) that does what I think you want.

1. give status of instance control

2. gives process id number

3. asks on the statusline for a subtitle (aka description)

4. save report to Dashboard-PR.txt, so can fully co-exist with the dashboard that now comes with vedit.

Scott

 
DASHBOARD-PR.VDM (6KB)

 


Topic: Dashboard-PR v1.0 (10 of 13), Read 12 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Friday, July 15, 2011 03:50 PM

On 7/15/2011 2:24:43 PM, Scott Lambert wrote:
>
>Hi Peter,
>
>Attached is a version of
>Dashboard called Dashboard-PR
>(one guess what PR stands
>for...) that does what I think
>you want.
>
>1. give status of instance
>control
>
>2. gives process id number
>
>3. asks on the statusline for
>a subtitle (aka description)
>
>4. save report to
>Dashboard-PR.txt, so can fully
>co-exist with the dashboard
>that now comes with vedit.
>
>Scott

Great,

I just learned that my instance control is set to "AUTO"
and the Process ID number of this instance of Vedit.

I wonder are there any other Vedit users who use several instances of Vedit ?

I certainly would appreciate hearing from them.

-peter

 


Topic: Dashboard v3.0 (3 of 13), Read 41 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Saturday, July 02, 2011 08:12 PM

On 7/2/2011 12:00:23 PM, Scott Lambert wrote:
>
>Attached is Dashboard v3.0.
>
>It now tells that path of the
>vedit exe file, and also the
>file backup option select
>(copy to vedit\backup, copy to
>.bak, off)


Thanks Scott,

I have a related question. I wonder whether you are using Firefox for your web browser. If not, I hope that somebody who does use it, will answer my question.


I have upgraded to Version 4 and wanted to save your DASHBOARD(2).VDM to my computer. I barely could do it.

Here are the specifics: If I double click on the macro, then Firefox opens it in Vedit and I can save it in Vedit.
However, I do not have the option of saving it as a file,
directly.
For example I tried to save a .ZIP file and could not.


Thanks as always,

-peter

 


Topic: Dashboard v3.0 (4 of 13), Read 46 times
Conf: VEDIT Macro Library
From: Christian Ziemski
Date: Sunday, July 03, 2011 01:42 AM

On 7/2/2011 8:12:36 PM, peter rejto wrote:
>
>I have upgraded to [Firefox] Version 4 and wanted
>to save your DASHBOARD(2).VDM to my computer. I barely could do it.
>
>Here are the specifics: If I double
>click on the macro, then Firefox opens
>it in Vedit and I can save it in Vedit.
>However, I do not have the option of
>saving it as a file,
>directly.
>For example I tried to save a .ZIP file
>and could not.

I tried it with Firefox 4.
It behaves as normal:
A single click on the macro opens the Firefox dialog asking whether to execute or save the file.
Or a right click on the macro opens the context menu giving the choice to "save target as" (I don't know the exact English expression).

So all is fine with Firefox and the macro here.

Probably you have told Firefox to execute "*.vdm" files immediately. Just change that back in Firefox' Options - Applications to "always ask".

Christian