Topic: Dashboard.vdm (1 of 5), Read 29 times, 1 File Attachment Conf: VEDIT Macro Library From: Scott Lambert Date: Monday, June 20, 2011 05:04 PM Dashboard.vdm tells you many things about your Vedit installation and saves its report to dashboard.txt in your user_home folder. My hope is it might be useful for the newish user, especially those not used to the new directory structure. Is it of any use to anyone? What other info might be useful to include. My thinking was it would be useful to include the report with a support request. Feedback requested. Thank you. Scott

  DASHBOARD.VDM (3KB)

Topic: Dashboard.vdm (2 of 5), Read 26 times Conf: VEDIT Macro Library From: Peter Rejto Date: Monday, June 20, 2011 09:41 PM On 6/20/2011 5:04:29 PM, Scott Lambert wrote: > >Dashboard.vdm tells you many >things about your Vedit >installation and saves its >report to dashboard.txt in >your user_home folder. > >My hope is it might be useful >for the newish user, >especially those not used to >the new directory structure. > >Is it of any use to anyone? >What other info might be >useful to include. > >My thinking was it would be >useful to include the report >with a support request. > >Feedback requested. > >Thank you. > >Scott Thanks Scott, I would appreciate, having the strings for my TOOL Menu and USER Menu included. I would also appreciate, having the actual content of these menus included. I believe, they are T-Registers 123 and 124. I am in the process of migrating from USTARTUP.VDM to Pauli's PRESET.VDM, so I was glad to see the USTARTUP information included. OOPs, I just thought of it. You have included many of the Vedit Config_String-s. I did not have a chance to check whether you included all of them. -peter -peter

Topic: Dashboard.vdm (3 of 5), Read 26 times Conf: VEDIT Macro Library From: Pauli Lindgren Date: Tuesday, June 21, 2011 04:34 AM On 6/20/2011 5:04:29 PM, Scott Lambert wrote: > >Dashboard.vdm tells you many >things about your Vedit >installation and saves its >report to dashboard.txt in >your user_home folder. > >Is it of any use to anyone? >What other info might be >useful to include. > >My thinking was it would be >useful to include the report >with a support request. Since you are displaying info about event T-regs, you could include T-reg 116 (double-click event macro). For support requests, it would be good idea to include version information: Vedit version, Windows version etc. (there are several macro commands for these). -- Pauli

Topic: Dashboard.vdm v2 (4 of 5), Read 23 times, 1 File Attachment Conf: VEDIT Macro Library From: Scott Lambert Date: Tuesday, June 21, 2011 12:15 PM Attached is dashboard ver 2 Now also gives: name of tool and user menus Vedit's full version info Windows version info tells if trial version tells if support period is expired tells if starup.vdm was executed tells status of double click event macro Scott

  DASHBOARD(1).VDM (5KB)

Topic: Re: Dashboard.vdm v2 (5 of 5), Read 18 times Conf: VEDIT Macro Library From: Ted Green Date: Friday, July 01, 2011 02:26 PM At 12:15 PM 6/21/2011, you wrote: >From: "Scott Lambert" (scottmacros@...) >Attached is dashboard ver 2 > >Now also gives: > >name of tool and user menus >Vedit's full version info >Windows version info >tells if trial version >tells if support period is expired >tells if starup.vdm was executed >tells status of double click event macro Another useful item would be the VEDIT_EXE string value which is the pathname to the executing vpw.exe file. Ted.