MR> Hi Tim!
 
Howdy!
TH> Because I am a bit of a perfectionist, I don't want to release
  > something that I think is not ready. Also, I don't want to 'give
  > away the farm.' I need to look into ways for protecting my
  > idea/potential product...
MR> Hmm, as far as I am concerned you don't have to fear that I will
  > steal any idea in order to use it within my own IDE (if it will
  > ever be started :). And: if it is as good as you wrote I don't
  > see a need for writing my own one :)
 
Oh, please, I wouldn't think *you* would take advantage of me. But, I
do believe I have something good, here; and need to copyright it.
Also, note that my editor *is* a functional IDE. It traps and points
to compile ewrrors, it will also do the same with run time errors now.
It even points to the error in $INCLUDE files. You can set
breakpoints, though not the same as the PB-IDE, and you can check on
register and variable status at run time or step mode. Am I missing
anything.
If you would like to be an 'alpha' or  'beta' tester, I would welcome
that very much. I am currently using my editor on all my PowerBASIC
development, and it seems solid enough to risk on my sacrid source
files. Only once did it truncate a file, and I'm not sure why. I don't
get any run-time errors. It's at a point in developmewnt where I am
hanging whistles and bells - ya know... functions and capibilities.
And improving how things work.
If you are interested, hollar back...
TH> Before I release it needs to prompt to save a 'changed' file.
  > Users can get very pissed if they exit the editor and lose an
  > hours worth work.  Ok, you're right. That would be a nice feature... :)
I think I should move it up a notch on the priority list. 
 
___ Blue Wave/QWK v2.12
--- Maximus/2 3.01
---------------