Index: dev_comm/excitation.txt
===================================================================
--- dev_comm/excitation.txt	(revision 23726)
+++ dev_comm/excitation.txt	(revision 23727)
@@ -36,14 +36,6 @@
 
 Custom Excitation
 
-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.
-
 User Inputs:
  f0
    long name: Nyquest Rate
@@ -50,28 +42,23 @@
    type: integer
    unit: Hz
    help:
+ funcStr
+   long name: Custom Function
+   type: string
+   unit: N.A.
+   help: f(t) = _____
+   
+   Notes: funcStr should have it's name selected by the user. The size of that
+   varaible can be any length from a single character to multiple megabytes. I 
+   strongly suggest offering the option to read this from another file via the 
+   run command.
 
-   Excitation Function Name
-FuncName=___string____
-
-[x] Enter File containing function instead of direct entry
-
-   Function (or File name if the user checked the above box)
-FuncName(t) = ___string____
-
 % output format:
-% 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);
+FDTD = SetCustomExcite(FDTD,f0,funcStr);
 
 **
 
-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.
 
 
-