______________________________________________________________________

              GoldED 4.00.Alpha1 "New Dawn", mm dd 1998

        THIS IS AN ALPHA OR BETA RELEASE - IT MAY BE UNSTABLE,
     CONTAIN BUGS AND HAVE BROKEN FEATURES. YOU HAVE BEEN WARNED!
______________________________________________________________________


______________________________________________________________________

                           Notes for Alpha1
______________________________________________________________________

! The overlay handling in the DOS version has been modified. The
  OVERLAY keyword is now obsolete. It has been replaced by commandline
  options: -OEMS for EMS memory, -OEXT for extended memory and -ODISK
  for disk-based overlaying.

______________________________________________________________________

              Notes in common with 3.00.Beta1 and Beta2
______________________________________________________________________


- Fixed several bugs in connection with FIDOUSERLIST that may cause
  crashes or strange behaviour.

- Fixed bug that NODEV7MODEM b0 was not displayed even if correctly
  configured.

+ Added support for V7+. It's automatically used if your NODEPATHV7 is
  set correctly. If GoldED shows "xxxx / NODEX.DTP" at the bottom of
  the browser window, the displayed information is taken from the raw
  nodelist entry.

______________________________________________________________________

               Notes for "3.00.Alpha6" (never released)
______________________________________________________________________

! The default logfile name is now GOLDED.LOG for all platforms.

- Fixed the internal editor range check error when using the block cut
  function.

- Fixed the zero-bytes SOUP replies file. This happened when your
  email/news areas were defined as local areas (to prevent being
  scanned out by the mail processor) in, for example, Fastecho, but
  redefined with SOUPEMAIL, AREAISEMAIL, AREAISNEWS and/or
  SOUPNEWSRCFILE.

- Fixed crash when commandline option -N was used.

- Fixed zero bytes allocation at [gmxbbs4.cpp,332].

+ New keyword: JAMSKIPDELETED <yes/no>. Default NO. If enabled, GoldED
  will silently skip (soft-)deleted msgs in JAM areas. However due to
  nature of JAM, they are still counted in the arealist and show up in
  the messagelist. Not tested.

- When the Imm attribute was toggled on, the Hld attribute (if any)
  was not cleared, and vice versa.

- COLOR READER CURSOR now works again.

+ Added support for the MOOD kludge. New keyword: MOOD <mood text>. No
  default. Can be used globally and in groups. New key command:
  READchangemood. Defaults to Ctrl-M (^M). Allows you to change the
  default mood by selection from a menu. If a MOOD kludge is found in
  a message, the content is displayed in the lower right side of the
  header, in front of the GIF indicator, if any.

  GoldED by default does NOT add the MOOD kludge, even when a number
  of moods are defined. The MOOD kludge is *only* added when you
  manually select one of the defined moods from the menu, or if you
  put the keyword in a group.

  The MOOD kludge was invented by Bo Bendtsen, and was first used in
  his "TerMail" mail reader component of Terminate. Here is a list of
  moods, taken from the Termail configuration:

    MOOD Always happy :-)
    MOOD Extremely happy :-)
    MOOD Singing and dancing :-D
    MOOD You are a friend :-)
    MOOD Thankful :=)
    MOOD Forgiving and happy ;-)
    MOOD Best day of my life :-D
    MOOD Strictly official :-|
    MOOD Please get serious ;-]
    MOOD Please forgive me ;-)
    MOOD Ohh noo you again :-?
    MOOD Worried :-!
    MOOD Proudly presents :=)
    MOOD Annoyed :-[
    MOOD Strongly sarcastic ;-)
    MOOD Dangerous and violent ;-/
    MOOD Very serious :-|
    MOOD Very angry :-(
    MOOD Sad :-(
    MOOD Argghhhhhh!! :-#

  TerMail allows only up to 20 moods to be defined. GoldED has no
  limit.

  NOTE: The MOOD kludge is regarded by some/many? as "stupid and
  useless", and it is a fact that it adds a few extra bytes to your
  messages. I strongly ugre you to NOT use this feature except perhaps
  in some echoes where you KNOW it won't be frowned upon.

  This feature took only about an hour to add and because I took the
  opportunity to cleanup and merge some duplicated code, it actually
  DEcreased (relatively) the EXE by a few kbs.

- If Write-to-file was aborted with ESC, GoldED tried to print the
  message.

- The menu to select origins/taglines from a file, named with
  @filename, didn't work well if there were long lines. Additionally,
  the CR/LF characters were not properly stripped. Not tested.

- When quote-replying a mail in a AREAREPLYDIRECT YES area with <N>
  and selecting a different area than the default, GoldED used the
  wrong area for the @oecho and @odesc tokens.

- During the first nodelist lookup, the statusline said "Checking
  nodelists ...", but the previous statusline was not recovered after
  checking. Not tested.

- LOADLANGUAGE didn't work as intended when used globally. Not tested.

+ Added SEMAPHORE SCANNETMAIL/PMSCANNETMAIL <file>. If GoldED finds
  this semaphore, it will scan or pmscan all netmail areas.

- Fixed -install and AREAFILE Squish for the situation when SET SQUISH
  points to a filename. Not tested.

- With FRQOPTIONS FAST and AREAFREQDIRECT YES, GoldED did not create
  more than one frq message when there were more files than could fit
  in one subject.

- Some bugs were introduced as a consequence of the separated msgbase
  code: EDITMSGSIZE didn't work. DISPSOFTCR didn't work in JAM areas,
  the -Y debugging commandline parameter didn't work in Hudson,
  Goldbase, JAM, Squish and Fido areas. Logging of msgbase errors and
  warnings was fatally flawed - GoldED would simply crash if such an
  event occurred.

- Fixed the annoying charset translation problem that caused erratic
  translation of ASCII 225 (german sharp s) and other characters, when
  in the presence of LATIN-1. Specifically, the characters were
  translated wrongly when you entered a new message while "on" a
  message with kludge "^aCHRS LATIN-1 2".

- Fixed sound support in GoldED/2. If enabled, it caused a crash
  (SYS3175) when attempting to play a sound, typically the startup
  sound.

- In newsgroups and e-mail areas, GoldED now *forces* the use of "Re:"
  in reply subjects, regardless of the EDITREPLYRE setting. The reason
  why it is forced in these areas, is because that is the standard for
  internet mail/news. Not tested.

+ Enabled EDITREPLYRE to work in groups as well as globally. Not
  tested.

+ Added support for the new Fastecho 1.46 groups 1-6.

+ In addressmacros and in NAMES.FD, the '@' character is now allowed
  in the macro name.

- Fixed unfree'd allocation at [gerand.cpp,158] and [geread2.cpp,242].

- In the msglist, there were circumstances when double lines appeared
  below the list of messages.

- The replies window was deformed when there was many replies.

- Fixed a few things to keep the cursorline number better updated in
  the internal editor. Not tested.

+ Added new color definitions for highlightning of unread and unsent
  mail in the messagelist:

  COLOR MENU UNREAD     <colors> When a msg is unread.
  COLOR MENU UNREADHIGH <colors> Additional highlight of to/from.
  COLOR MENU UNSENT     <colors> When a msg is unsent.
  COLOR MENU UNSENTHIGH <colors> Additional highlight of to/from.

  If a msg is both unread and unsent, the unsent colors are used.

  The definition of "unread" in this case is a message where the
  "timesread" field contains the value 0 (zero) or some kind of "seen"
  attribute is not set. See also the description of the new
  HIGHLIGHTUNREAD keyword.

  In msgbases where there is no timesread field or "seen" attribute,
  GoldED currently fakes it and always returns a 1 (one) in the
  timesread field, so that msgs won't be listed as unread all the
  time.

  If the HIGHLIGHTUNREAD keyword is set to NO, the UNREAD colors are
  deactivated.

  Currently I haven't made any defaults for these colors, so they are
  all just grey on black for now. Suggestions are welcome!

+ Added new keyword HIGHLIGHTUNREAD <yes/no>. Defaults to NO. If set
  to YES, GoldED updates (increases) the "timesread" field in each
  message that you read. If set to NO, it doesn't touch the message.
  The YES setting causes a slight performance decrease, because the
  header of each message has to be read, the timesread field updated
  and the header written back to disk. The update happens immediately
  after the message is displayed, so you may not notice it at all. A
  message is only updated if the timesread field contains the value 0
  (zero).

  This keyword only works in the following msgbase formats: Fido
  (*.MSG), Hudson, Goldbase, JAM, Squish, Ezycom and AdeptXBBS. In
  Squish and Ezycom, there is no timesread field, but I have annexed a
  reserved message attribute (in Squish, 0x00080000, now called
  MSGSEEN; in Ezycom, extattr 0x80) for the purpose of marking a
  message as read at least once. The other formats (PCBoard, WildCat)
  have no timesread field, but they have reserved fields or attributes
  which *could* be used. Let me know if you want this.

- A bug caused the area description to be used instead of the path in
  a few situations: The GOLDAREA.INC file, the quotebuffer file,
  PCBoard.

______________________________________________________________________

        Previous notes were for GoldED 3.00.Alpha5 and older.
______________________________________________________________________

