Version 1.17 beta 16: Used js.gc(true) to force garbage collection at the beginning of the sub-board scan loops to ensure enough memory is available to continue doing the newscan.  This solved an issue where a "malloc failed" error was being returned.  I just saw that for the first time when doing a newscan with my reader today.

Version 1.17 beta 15: When deleting a message, any vote response messages that may exist for that message are also deleted.  Also, added a check in the GetMsgIdx() method that should (hopefully) avoid a 'msgNum not a number' error (as reported by Ragnarok).

Version 1.17 beta 14: Fixed a UI issue when displaying voting errors in the scrolling reader interface.

Version 1.17 beta 13: For poll votes, added the voters' date & time (not just the voter's name) to the message body when appending the names of people who voted on polls.  Makes use of the PollVoteNotice (787) line from text.dat.

Version 1.17 beta 12 - Bug fix for one of the methods: Now correctly returns 0 when there are no readable messages in the sub-board (messages with null headers or ones that are marked as deleted, unvalidated, etc.).  This would affect, among other things, listing messages in the sub-board.

Version 1.17 beta 10: Now the results of a poll vote are refreshed on the screen after the user submits a poll vote.  Also, fixed a bug in setting the user's vote for a poll.

Version 1.17 beta 9: Added initial support for voting on poll messages (in addition to up/downvoting).

Version 1.17 beta 8: Fixed a bug when getting the last-read message index after filtering out deleted messages (or any messages that are not readable due to not being verified, etc.).  Also, for voting, updated it to check whether the user has voted on the message before showing the vote prompt (thanks to echicken for describing how to check that).

Version 1.17 beta 7: Improved the voting input for the scrolling reader mode so that it doesn't have to refresh the whole screen when the voting process is done.  Also, fixed a bug in error output for voting in the traditional (non-scrolling) reader interface.

Version 1.17 beta 5: Added hotkeys to view vote results for a message (T) and vote on a message (V).  The vote-on-message functionality is still not implemented (when a function for doing that becomes available in Synchronet JavaScript, I will add it).

Version 1.17 beta 4: Bug fix - When going to the next area after reading the last message, it was showing empty messages.  This seems to be fixed now.

Version 1.17 beta 2: Working on filtering out messages that are deleted, unverified, poll/vote messages, etc. so they don't show up in the message list or reader interfaces.

Version 1.17 Beta 1: Implemented a workaround for handling message headers that are null (which are more common now with the message voting feature recently introduced in Synchronet).  Now such message headers won't cause weirdness in the message list.  Users won't be able to read such messages.  I'd like to find a way to not show such messages altogether in the message list - Will probably need to use the get_all_msg_headers() method in the MsgBase class to get all message headers except ones for vote messages.

Version 1.16: Added a new feature that allows users to forward a message to an email address or to another user on the BBS (using the O key).  This can be useful, for instance, if the user wants to send a message in a public sub-board to their personal email for future reference or send a message from a public sub-board to another user to discuss the topic privately.

Officially releasing version 1.15.  Contains the bug fix for private reply for a message on a networked sub-board, and also includes the new user-edit feature (using the U key, for sysops only), which lets the sysop edit the user account of the author of the message (only if the user account exists on the BBS).

Version 1.15 beta 2 - Contains a fix for a bug introduced in the previous version where private reply was no longer working.  Also includes a new user edit feature (for sysops only, using the U key).  The user edit will edit the user who sent the message, only if they're a user on the BBS.  It can be useful for BBSes that require new users to send an email to the sysop, in case the sysop needs to edit the user's account.

Version 1.13: A couple of bug fixes.  Now should no longer generate a message number error when a new user starts reading messages.  Also, it should now always successfully save a message header with the READ attribute when the user it was addressed to has read the message.  This should fix an issue where the same message would keep coming up in a newscan, etc.

Version 1.13 beta 1.  Bug fix: Message number error when a new user starts reading messages.  Now checks for a seemily special value for the message number to avoid an error.

Version 1.12: Updated the way the pause prompt is shown in the help screen, in case the sysop has configured an external module (Baja/JS) to run for a pause prompt.  Also made a potential bug fix: When translating a message number to a message index, added a check to ensure the value is a number, to (hopefully) avoid a potential crash.

Official release of version 1.11 of Digital Distortion Message Reader - Contains the update which will update the number of new posts read by the user during the session (bbs.posts_read) and the internal refactor making the .js file a little smaller.

Now updates bbs.posts_read so that the posts read for the current session is accurate.  Also did some internal code refactoring - Removed code which is no longer used (it was leftover code for an older-style reader interface from my message lister, now not used in favor of the new reader interface).  This is a "beta" version but seems to be fairly stable, so a non-beta release update will likely come soon.

Bug fix: The page number for message groups wasn't being updated in the area chooser when using the up & down arrow keys to go to the next/previous page.

Added notes about the message written dates to say that they will be adjusted to the BBS's local time zone so that the message written dates are all consistent that way.

Updated so that when using message written times in the message list & area chooser, the message written time will be adjusted to local BBS time so that they're all in the same time zone.  Also, changed the default options for msgAreaList_lastImportedMsg_time and msgListDisplayTime in the configuration file to written instead of imported.

Fixed a possible screen refresh issue when writing the area chooser header - Now it clears the header rows on the screen before writing the header, to clear away any text that might have been there before (such as from the help screen).

Fixed a bug in the method that displays the header file for the message area chooser - It no longer sets the color code back to normal at the end of each line, so that for .asc files (Synchronet color codes) it doesn't reset any color codes that might still need to be used.

Updated so that ANSI header files for the message and area chooser are displayed in their original ANSI format without being converted to Synchronet color codes first (if the user's terminal supports ANSI).  If the user's terminal doesn't support ANSI, then the header files will be converted to Synchronet color codes first (as was done previously).

Fixed a bug when returning from the help screen for the lightbar message area chooser - It wasn't displaying the header again when returning to the area list.

Refactored some code related to loading the header files for the reader interface and area chooser list.

Bug fix: The new postOnSubBoardInsteadOfGoToNext was affecting the behavior for searching & scanning, which I don't think is desirable.  Now it only affects behavior when doing a normal read (not when doing a search or newscan, etc.).  Renamed the postOnSubBoardInsteadOfGoToNext configuration option to readingPostOnSubBoardInsteadOfGoToNext to more reflect what that setting is for.

- Added a new configuration option, postOnSubBoardInsteadOfGoToNext, that affects what happens after the user reads the last message on a sub-board: If this is set to true, then the reader will prompt the user if they want to post on the sub-board, then exit (this is the stock Synchronet behavior).  If this is set to false, then the reader will prompt the user whether to go to the next sub-board after reading the last message on a sub-board.  Also, added the postOnSubBoard text configuration parameter for the theme filename, which specifies the text to use for prompting the user if they want to post on the sub-board after reading the last message.
- Added new configuration options areaChooserHdrFilenameBase and areaChooserHdrMaxLines.  These options specify the filename base for a header file to use for the message area chooser list and the maximum number of lines to use from the area chooser header file.  The filaname is without the extension - The reader will first look for an .ans version, then an .asc version.  Additionally, multiple header files can be used for different terminal widths - For example, chooserMsgHdr-80.ans for an 80-column terminal, choosrMsgHdr-140.ans for a 140-column terminal, etc.