Index: dev_comm/excitation.txt
===================================================================
--- dev_comm/excitation.txt	(revision 23675)
+++ dev_comm/excitation.txt	(revision 23676)
@@ -5,10 +5,10 @@
 fc.
 
    center frequency
-f0=_____________Hz
+f0=____number___Hz
 
     20db cutoff frequency
-fc=_____________Hz (bandwidth = 2*fc)
+fc=____number____Hz (bandwidth = 2*fc)
 
 
 technically there is another variable but lets assume we aren't trying to
@@ -23,18 +23,48 @@
 Sinusoidal excitation
 
      sinewave frequency
-f0 = ______Hz
+f0 = _number__Hz
 
-FDTD = SetSinusExcite(FDTD,f0)
+FDTD = SetSinusExcite(FDTD,f0);
 
 **
 
+Custom Excitation
 
 
+
    nyquest rate
-f0=________ Hz
+f0=__number__ Hz
 
+   Excitation Function Name
+FuncName=___string____
 
+[x] Enter File containing function instead of direct entry
 
-FDTD = SetCustomExcite(FDTD,f0,funcStr)
+   Function (or File name if the user checked the above box)
+FuncName(t) = ___string____
 
+I don't think it makes sense to have a text entry window large enough to
+input. They could be entering a few term equation or a massive raw data file.
+So I suggest we include a single line string entry that is copied into the
+file ahead of the excitation line. 
+
+Doing that lets the user ether enter the string they want to use or the run
+command with a file name which will run the file to load the data.
+
+
+% If they checked the box we do the following
+run filename;
+% If they didn't it's entering the line
+functionname(t) = <some random stuff the user enters>;
+
+FDTD = SetCustomExcite(FDTD,f0,FuncName);
+
+**
+
+There is a whole other class of functions but they require a 3D box be entered
+and that requires more changes (probably attribute) elsewhere for a feature no
+one will want for the start.
+
+
+