From: John K. <jmk...@fa...> - 2008-05-21 03:28:16
|
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 |