Here is some more info from Dewey on the gui.
Hi,
I look at the forum now and then (a great resource) and notice
in your recent post:
> I create a desktop launcher and use the following to launch each one. Of course
> the name would change for each file.
> /home/john/emc2/ngcgui/ngcgui.tcl --cwidth 25 --vwidth 0 -S /home/john/emc2/nc_files/id.ngc -a
I just wanted to mention that the -a option should actually be followed with
a file name like:
-a tst1.ngc
or -a tst2 (this will become tst2.ngc)
When -a is not followed by a filename, it sort of accidentally
works but only if it is the last item on the command. (it uses
the name auto.ngc). A problem could occur if you tried to do
something like have another option following -a and the error
handling isn't so good for that (I'll try to improve it).
The help text is kind of standard format but it may be confusing since the
-a works without the autosend_file specifier if it is the last item.
$ ngcgui.tcl --help
Usage:
ngcgui.tcl --help
ngcgui.tcl [Options] -D nc_files_directory_name
ngcgui.tcl [Options] -i emc_inifile_name
ngcgui.tcl [Options]
Options:
[-S subroutine_file]
[-p preamble_file]
[-P postamble_file]
[-o output_file]
[-font [big|small|fontspec]] (default: "Helvetica -16 bold")
[-horiz|-vert] (default: -vert)
[-a autosend_file] (autosend to axis)
(width of comment field)
(width of varname field)
Another small note -- Starting with a launcher is a good idea but if
you have problems, you probably don't get to see some error messages.
So if you have a startup problem, testing from the command line
may be useful.
Also, when starting from a launcher some of the helpful buttons like
Ctrl-h Show key bindings
have nowhere to write stuff to help -- I should work on this too
so a widget pops up. Since I use command line for most things,
I never thought of the consequences of using a launcher.
keep up the great work!
dewey
--
Dewey Garrett