Re: [Emc-developers] halscope mod

[Mario. <em...@gm...>]

This is all great gyus, but I still have the feeling it would be nice
to mention this in the documentation. Remember the guides and manuals
fall into obsolescence with every one - no matter how good
improvement. :)

On 5/21/08, John Kasunich <jmk...@fa...> wrote:
> Dewey Garrett wrote:
>  > I've been using halscope frequently for a number of distinct purposes but don't
>  > like setting it up or wrangling the config file (.scope.cfg) each time so I
>  > made a simple change to halscope that lets a user specify an input file to read
>  > and/or an output file to write for configuration items.
>  >
>  > Modified behavior:
>  >
>  >   $ halscope -h
>  >   Usage:
>  >     halscope [-h] [-i infile] [-o outfile] [num_samples]
>  >
>  > The current behavior is not affected.
>  >
>  > John Kasunich suggested I post about it here to see if there's
>  > any interest in adding a patch to CVS.
>  >
>  > The one modified file (scope.c) is posted at:
>  >
>  >     http://pastebin.ca/1021409
>  >
>  >
>  > dgarrett
>  >
>  >
>
>
> Dewey:
>
>  Well it took me several weeks to get around to it, but I committed your
>  patches - both the halscope one mentioned above, and the hal_joystick
>  one that you sent me privately.  I tweaked the latter a bit so that the
>  pin names remain "joystick.0.foo" unless you specify a prefix with -p.
>  The default component name is now "hal_joystick" and the default prefix
>  is "joystick.0".  The -p option changes both name and prefix to whatever
>  is specified.
>
>  Thanks for your contributions!
>
>  Regards,
>
>
>  John Kasunich
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Emc-developers mailing list
>  Emc...@li...
>  https://lists.sourceforge.net/lists/listinfo/emc-developers
>