Since macros are only text files, I personally have no need of fancy functionality in a library or utility. The current Elecraft K3 utility works beautifully.
So for me, a simple Web site (or shared Google doc) listing macro examples is all the functionality that I think is needed. 73, Barry N1EU On Thu, Feb 4, 2016 at 12:17 PM, Phil Hystad <phys...@mac.com> wrote: > The recent comments regarding Wayne’s new Noise Blanker experiment > reminded me of something I wanted to suggest awhile back but forgot all > about it. > > This has to do with Macros and command sequences used to program or alter > some specific setting in a temporary (maybe) way. Many of these are posted > here as well as found on some web sites including Elecraft. > > But, there is something missing that would be nice. And, that is a > documented library hosted on Elecraft’s web site as well as a utility > program feature to automatically download and manage the macro programs. > > As a library, the documentation should be embedded in the Macro file > itself per a standard format that declares the purpose (brief abstract), > more detailed user instructions, and any known side effects. Also, > author’s name and date and maybe a revision history. > > The utility programs would include a new feature to download (maybe > abstracts or complete macro file) and list available macro programs > displaying the brief abstract on the display. The utility program would > allow the user to select macros for download that copy them to a known > location on the user’s computer managed by the utility program. Also, this > new feature set would support the loading of the macro to the K3/K3S/KX3. > Actually, a very nice “extra” would be to undo the macro act. Of course, > this could get complicated since a Macro can do anything and many things > that should not be done. But, one way to undo is to automatically save and > then allow restoration of the rig settings, say in some kind of test mode. > Of course, this could be done by the user but it might be faster to do it > as part of a test sequence supported by the utility program. > > It seems like the only complicate part of this process is setting up a > repository and managing it in a way that ensures the integrity of the > standards: documentation, layout, and anything else. The enhancements to > the utility programs do not seem to be all that hard to do (I am a retired > programmer of about 50 years programming experience). > > There could be a network of volunteers that accept the new macros to be > included and they test and vet those macros per the definition of purpose > and the standards set forth for this repository. > > 73, phil, K7PEH > > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to n1eu.ba...@gmail.com ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
