Guest
Sep 3, 2010, 2:51 am UTCHome arrow Ramblings arrow Big Monster Update
header image
Big Monster Update
Written by Dreamless Dancer   
Feb 02, 2008 at 12:35 PM

Overall, this was a monster of a fix, the biggest being that I included a means to hard fix the IP address which furbot uses for connecting to the server. I looked into several different options, finally deciding to go with this method because the possibility may occur in the future where this will be needed again. So now, in configuration, there's the means to not only use the Hard IP address of the server, but also, bonus, select which port you want to use.

Other fixings include the harding the database system to avoid runtime crashes caused by preforming database operations on an unopened database, that's now got a flag which is set when the database is opened. If the botscript executes an operation which requires an open database, and it's not, it won't do anything but deliver an error message.

And there there was a strange error with the clock variables not updating past midnight, dunno how I overlooked that one, a recursion check on procedures, was possible to lock the bot solid by recalling the procedure you were in, and a stopper for the bot should the username and password not match, or kin events which prevent the bot from connecting.

Then I put the User buttons in! Yea!

User buttons execute procedures, and are set anywhere and anytime with a simple command in which you specify the button you want to affect, the procedure you want to use, a caption, and optional tooltip.

Trigger Name: Start Up
Program starts
   No Additional Conditions.
THEN:
      Set user button {0} to run procedure {Online Button}

with the caption of {Online}

and tooltip of {Displays Members Online}
      Set user button {1} to run procedure {Display Who}

with the caption of {Who Here}

and tooltip of {Displays The Visitor List}
      Set user button {2} to run procedure {Dump Tally}

with the caption of {Activity}

and tooltip of {Dump A List Of Active Members}
      Set user button {3} to run procedure {Where}

with the caption of {Where}

and tooltip of {Where The Camera Is}

Oh, that rocks. Love it. Can put in instant front panel functions eliminating the need to go through the Debug Execute menu. Something to remember though about this, currently, you can only have one procedure running at a time, so until I install a better means of recursion checking, any procedures you use elsewhere for purposes of computation or what not, if you need that code, you will have to duplicate it to the button procedure at this time.

Last Updated ( Feb 02, 2008 at 12:44 PM )
<Previous   Next>
header image