Index: work/fem/TODO.export.txt
===================================================================
--- work/fem/TODO.export.txt	(revision 22815)
+++ work/fem/TODO.export.txt	(revision 22816)
@@ -14,13 +14,32 @@
 2. user convenience ==========================================================
 
 ? optionally mesh resolution should have a tickbox for the user to
- just use the equation
- resolution = c0 / (f0+fc) / sqrt(substrate_epsilon) / unit / 25;
+ just use the equation.
+ resolution = c0 / (f0+fc) / sqrt(substrate_epsilon) / unit / lambda_frac;
  so that the user doesn't have to caculate it.
   -> no idea wat c0, f0, fc and unit are; please use pcb-rnd terms,
      reference to named fields of the dialog boxes with exact name
      or if you need new fields, make that explicit. We need: what
      _exactly_ is needed from pcb-rnd's side.
+  -> right now users enter 3 different mesh line densities (resolutions)
+     for copper, gap, and min spacing. if you user selects this feature these
+     densities would instead be calculated as fractions of lambda. Using
+     c0 = speed of light ( 299792458 m/s )
+     lambda_frac = what fraction of lambda they want to use for each of the
+     three densities. So the equation is used once for each density.
+     and ether
+     f0 = center frequency of the pulse
+     fc = 20dB cutoff frequency --> bandwidth is 2*fc
+     or
+     f_max = max frequency of interest (meaning the sweep is from 0 to this
+     number)
+     if the user has selected the ladder (f_max) the line that is currently 
+     FDTD = SetGaussExcite(FDTD, f_max/2, f_max/2);
+     is used.
+     if they select the former (f0 + fc) then that line should be
+     FDTD = SetGaussExcite( FDTD, f0, fc );
+     please note that in ether case it is encouraged to just put in the values
+     for f0, fc, or f_max and not assign a variable name and etc.
 
 
 ? optionally the ability to replace the bounds with the equation