Changes in version 0.0.2.0 alpha 2 - 24 June 2007

New:
  -  For the video editor, two new items in the row button menu,
     Jump to Start Frame and Jump to End Frame. Another great idea from a user,
     thanks towtruck, aka Andy

Fixes:

() Huge bug in my method of reducing memory leaks when using AviSynth API.
   Some users would experience sudden program termination when switching to
   a viewer.

() Script syntax or AviSynth error should prevent loading the video display.
   Error text displayed in Test box, last error retained see
   AviSynth Options | Display AviSynth Version

() Loading Script with an error directly using media viewer terminated FilmCutter
   after reporting error.

() When using the function lookup in AviSynth documentation feature with the path
   to the documentation incorrect, the SafeString update and pointer audits broke
   this. Only a new user or new installations would ever see this. If you did see
   it you had trouble.  List of outcomes is very long.

(a1) Found the cause of encoder dialog window title haveing the encoder path
     almost off the page.

(a1) FilmCutter has had a string white space stripping ghost for sometime.
     Exercised one in the function parameter parser in mydlg.h

(a1) Encoding interface code had a few unintentional message boxes, sorry.

(a1) For those that edit using projects, if you had occasion to use the tabs on
     the editor they should work ASAP instead of waiting for the mouse to move.
(a1) Alpha video window poped a message box when closed

(a1) An illegal resourse assignment has been fixed 98 & ME and nt4 users, sorry I
     didn't know, rejoyce.(IanB)

(a1) Another issue with dynamic memory allocation resolved in the video
     interface.(IanB)

(a1) FilmCutter would choke on a corrupted ini file and loop endlessly.

(a1) Dialog bug in alpha 1 options dialog help button opens lots of help windows.
     Wow!

(a1) Ever wonder what your screen saver keeps coming back. You turn it off, it comes
     back.  Oops, FilmCutter can disable screen saver and power saver settins
     but always restores them.  If now checks the states and preserves your system
     settings.

(a1) Play was activate-able without a loaded video.

(a1) Script writing options dialog proc had some window errors.

Changes:

() More pointers to buffers corralled up so the memory associated can be reused or
   Released.

() Moved many local variable definition statements out of conditional branches in
   WinMain with much care taken to make sure that memory allocated is reused not
   recreated.

() FilmCutter would warn the user about needing SciLexer.dll and then go on to crash.
   FilmCutter now warns the user then terminate gracefully.

() If the video viewer was in play mode when the user exited FilmCutter the system
   values for the following items remained false. Oops!
      SETSCREENSAVEACTIVE
      SETPOWEROFFACTIVE
   FilmCutter how issues a play stop command before exit, which changes the values
   to true.

() If you change the file filtering in the file saves / open dialogs FilmCutter
   remembers your last file type, i.e. *.txt, *.avs, if you change it. Believe it
   or not that is not automatic.

(a1) While bug hunting the parameter help dialog I added code to prevent parameter
   strings from exceeding 260 characters (max path length).