Version 1.17 beta 36: Updated the newscan loop to wait 10ms at the end of the loop to avoid causing CPU usage to go high while the newscan loop is running (CPU usage was getting to 99% on my BBS system).  With the 10ms wait, CPU usage went down to 65-70% on my BBS system, so it seems this should help keep the CPU workload from getting so high.

Version 1.17 beta 35: Updated the threshold for the percentage of ANSI codes to convert to Synchronet (& strip out any ANSI that's difficult to convert) rather than display as ANSI (previous was 6%, now 7%), due to a message with ~6.4% ANSI codes.

Version 1.17 beta 34: Updated the way it deals with rogue ANSI codes that seem to be added to certain messages (including cursor movement characters) which probably weren't intended to be there, which can mess up the display of messages when using the scrolling interface.

Version 1.17 beta 33: Improved to better handle message text that starts with "By <name> to <name> on <date>" - Some of those messages have ANSI codes (such as cursor movement codes, etc.) in that part of the text, which can mess up the display of the message when using the scrolling interface.

Version 1.17 beta 32: Fix for some (new) instances where it wasn't checking the sub-board code to see if it was "mail" before checking the can_read property

Added a revision history note for version 1.17 (even though it's still in 'beta').  Also, updated the readme to include some notes on voting, and added a list of lines from text.dat used by the reader.

Version 1.17 beta 31: Added some checks to ensure the user won't be able to read a sub-board if they don't have permission to (if the sub-board's can_read property is false).

Version 1.17 beta 30: Made an update that should (hopefully) fix a message number error when a new user does a newscan for the first time (I thought I had fixed that some time ago, but it looks like I didn't fix it for all cases).

Bug fix: When getting the message text, now checks if it's reading personal email before checking if it's a moderated message area, avoiding an 'undefined' error.

Started working on a way to validate a message in a sub-board where the message requires moderation.  Doesn't seem to be successfully saving the updated message header though.

Version 1.17 beta 25: Refactored the newscan code a bit (removed some code duplication).  Should not affect the behavior.

Version 1.17 beta 24: Implemented an update for message newscans which should (hopefully) fix the bug where the correct last read/newscan message wasn't being used.  Now it should hopefully show the correct first unread message during a newscan.

When creating a Frame object (for viewing & scrolling ANSI messages), it now removes the HIGH attribute from the default frame attributes.

Version 1.17 beta 22: Fixed a couple of bugs related to viewing messages with ANSI content and scrolling them.

Version 1.17 beta 21: Updated to check whether the user is allowed to vote before letting them vote on the message (by checking the V restriction).  Also, fixed a display update bug that happened if the user quit out of voting on a poll/message.

Version 1.17 beta 20: Updated to fix an issue reported by KenDB3 - Line 9588 was trying to use MSG_POLL without checking to see if MSG_POLL was defined (which could be the case if the JavaScript files have not been updated on the BBS machine).

Version 1.17 beta 19: When changing to another message area, it now correctly shows the number of readable messages (in case any are deleted, unverified, etc.) rather than the total numbre of messages in each sub-board

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.