Don't assume the first null message index is the last message in the sub.  Don't create an Array just to have something to set arbitrary properties on.  This may fix the problem observed on Vert by KenDB3 (messages after mid Nov. 2016 not being displayed).

Bug fix: When posting a poll, now it makes sure the user's sub-board is correct.  Also, now it correctly handles the user quitting out of a couple menus with the ESC key (making no choice).

Added the ability to vote on a topic from the result viewer interface.  Also, updated the documentation a bit.
SlyVote now has just enough functionality to be a useful voting both door, but I still want to add & update a few things.  I want to implement the "Answer all topics" functionality, add the ability in the result viewer to type a topic number and jump to it, add the ability for sysops to delete voting topics (poll messages) from SlyVote, and also improve some of the screen displays a bit.  I might also possibly add a help/informational screen.

fix cleartoeol() and clearline() to clear relative to current frame offset (instead of absolute position)

On second thought, Frame.clear() will probably just be changed and my previous commit is unnecessary.

In ViewVoteResults, call Frame.cleardata before dumping new content into the Frame.  This effectively resets Frame.data_width and Frame.data_height, which ScrollBar uses in its calculations.

Worked on displaying the vote results - Got the poll result colors showing correctly in the frame and enabled frame scrolling and navigation between the poll result messages.  There are still some things remaining, such as enabling voting on a poll from the "view results" view, going directly to a poll message by typing in its number, and voting on all polls.

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

Trying to use a Frame to display poll message text to ensure it's scrollable.  Having an issue with it displaying Synchronet color attributes though..

Added a check to make sure the user is allowed to vote (by checking the V restriction).  Also, started working on the beginnings of reading poll results.  It's still a work in progress.

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.

Updated DDLightbarMenu to preserve the current selection when an item hotkey is pressed.  Also, updated SlyVote to preserve the main menu option when returning back to the main menu from an action.

Updated to check whether a user has voted on a topic before allowing them to vote on it, and display an error if so.

Implemented saving the user's vote.  Also fixed a bug in displaying the "registered to:" name.  Still a work in progress.

- When importing echomail packets and tossing to linked-nodes, don't loop
messages back to originating nodes, even if their address is not in the PATH or
SEEN-BYs.
- To get the full originating address of an echomail message (for loop-back
prevention), parse the Origin Line before tossing to links. If the Origin Line
cannot be parsed, log a warning message.

Made some small tweaks to how the poll question comments are displayed, and updated to display the poll question above the poll options menu.

Updated to retrieve & display the poll comment lines (up to 3 of them) and show the poll options for the user to choose from.  It's still a work in progress.

This is a very early beta version of SlyVote - A voting door for Synchronet which makes use of the new voting capabilities in Synchronet 3.17.  SlyVote was initially styled after DCT Vote, a voting door available in the 1990s.  This is in a very early development state and is not functionally complete yet.  Currently, it will display a list of poll topics in a sub-board.  The voting mechanism, displaying results, etc. are still to be implemented.

Updated so that when looking for an item's hotkey, it uses the first one it finds (in case multiple items have the same hotkey).  Previously it would have used the last.  Also, added some more methods: Remove(), RemoveAllItems(), RemoveItemHotkey(), and RemoveAllItemHotkeys().

Updated to wrap around when using the up & down arrows to navigate the selections.  That behavior can be disabled by setting the wrapNavigation property to false.

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).

Updated to use the right arrow in addition to the down arrow to move down, and the left arrow in addition to the up arrow to move up

Fixed a bug with using the PageDown key.  Also, updated the GetVal() method so that it resets the terminal color back to normal when it's done so that any text printed afterward will look good.

This provides a scrollable lightbar menu in the form of a JavaScript class.  Item colors (normal and selected) can be customized.  Allows scrolling of the menu items, so that if there are more items than can fit on the menu, the user can scroll through them.  Supports use of the up & down arrows, PageUp, PageDown, Home, and End keys, and the Enter key selects an item.  This requires an ANSI terminal.

Untested; try to determine the best address to reach the terminal server at; this is probably 127.0.0.1.

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.13: Updated the message area chooser to show the number of readable messages rather than the actual total number of messages in the sub-boards (in case some messages are deleted, unverified, etc.)

how "frequent" the progress meter/percentage displayed is updated.
Most uses of this function are now using a interval of 10 so that fast-running
searches aren't now "slow" due to the progress display.

Don't ident; commands.js will trust localhost instead. Should rid us of the 'incorrect password' log message, and another bug recently reported on DOVE-Net.