egghelp/eggheads community

Wee bit o help needed

2003-04-11T06:52:17-04:00

Yup, it keeps the file stored after restart now

All i can say is a big thanks to you.

Statistics: Posted by Weirdo — Fri Apr 11, 2003 6:52 am

Wee bit o help needed

2003-04-11T05:04:03-04:00

Damn, that toook longer than I thought.

Download again, I now have it working, and I don't know what I did to fix it though

Statistics: Posted by ppslim — Fri Apr 11, 2003 5:04 am

Wee bit o help needed

2003-04-11T04:41:34-04:00

OK, the error you are getting is a fault on your part. As I have noted, the -init setting is to initilise the variable.

This is done in 1 of three ways.

1: If the variable allready exists, do not change the value, leave it as it is. This is for a .rehash.

2: If not, then check to see if it is in the file. If it is, set it to the value in the file.

3: If not in the file, use the default value given and save this to the file.

The default should only ever be used on the very first attempt, or the line has been deleted from the file.

The error given to you, says it is unable to find a file called default. Well, it's pretty damned obvious what the error means. You could do with a "file exists" check in the pub:picoday command.

You might also want to update my script again, I have made a change. However, I am abotu to go do some testing on it myself, because it is doing my head in.

Statistics: Posted by ppslim — Fri Apr 11, 2003 4:41 am

Wee bit o help needed

2003-04-10T15:37:25-04:00

[20:32:36] [20:32] Tcl error [pub:potdinfo]: could not read "default": no such file or directory

{picoday default} < picoday.db.file

Updated the file to show what the script is now.

Statistics: Posted by Weirdo — Thu Apr 10, 2003 3:37 pm

Wee bit o help needed

2003-04-10T15:13:04-04:00

I have made one change to the script, you may wish to download it again.

1: After the bots has started, make a change using the !pic_set command.

2: Goto the shell, edit the database file, and look at what the contents are.

3: Issue a .restart

4: Edit the file again, and see fi the file changes.

Statistics: Posted by ppslim — Thu Apr 10, 2003 3:13 pm

Wee bit o help needed

2003-04-10T12:13:53-04:00

File was created before i made it.

Good news is, she is retaining a variable now. But, as the default line did make it, the variable became...

{picoday default}

upon restart

What i was figuring is if instead of replacing the last line, which the script seems to have done, is to just check what the last line was, and extract the filename from there? As it would create some pseudo form of logging of what pictures have been used as the picture of the day. Will probably do some playing with writing to files tonight, see if i can figure getting info from lines and stuff

Statistics: Posted by Weirdo — Thu Apr 10, 2003 12:13 pm

Wee bit o help needed

2003-04-10T09:27:44-04:00

First off, you should move the "setsave -init" line further down. Below the "set:save" proc.

I noticed why there was a missing bracket now. It was when I hadn't cleared up funny and tidying the code. At this time, using "-init" causes this problem.

Redownload

Aditionaly, did you create the file as noted?

Statistics: Posted by ppslim — Thu Apr 10, 2003 9:27 am

Wee bit o help needed

2003-04-10T08:22:12-04:00

if picoday is set using

setsave -init picoday default

I do still have to use the

setsave picoday [file join $dir(main) $dir(filename)]

in the proc pub:picoday?

[edit]

Re-Read the instructions above, understand where to put it now. Think i need both, but setsave -init outside of a proc

Changed the download to show the script

[edit2]

{picoday filesys/incoming/1044150826579.jpg} is what it records And DOES change when a new image is set.

only one problem

At restart, this occurs

[13:28:24] [13:28] Tcl error [pub:pic]: can't read "picoday": no such variable

Which means the variable has been wiped, and i done it wrong

Statistics: Posted by Weirdo — Thu Apr 10, 2003 8:22 am

Wee bit o help needed

2003-04-10T08:17:27-04:00

First off, I have changed the script again. It fixes the missing bracket, and also prevents the error you have shown.

However, you should also have a "setsave -init" line.

Without this line, your script will not re-load the previously set value when the bot died.

It will need to be below the "proc setsave" definition.

Use

Code:

setsave -init picoday default

This will make it reload the value each time.

Statistics: Posted by ppslim — Thu Apr 10, 2003 8:17 am

Wee bit o help needed

2003-04-10T07:45:25-04:00

Was missing a close brace, added it

Giving me a Picoday - no such variable error now. Thats the variable i am using for set save. I have uploaded the changed tcl file to the link above

Statistics: Posted by Weirdo — Thu Apr 10, 2003 7:45 am

Wee bit o help needed

2003-04-10T07:29:02-04:00

Re-download the file form the link. I remember thinking about that when making it, but thought it wasn't need (WRONG)

It will only create one line for each variable.

This prevents the file from becoming bloated.

It should never cause a error, but when file doesn't exist, all data is lost. So you will also need to create the file first. Quickest way, is to use "touch file.name" on the shell.

Statistics: Posted by ppslim — Thu Apr 10, 2003 7:29 am

Wee bit o help needed

2003-04-10T07:19:38-04:00

W...o....w

Ill give it a go.

Slight Question on when it adds to the file. Does it add a new line for each file that is set?

http://sucess.faereal.net/sebstuff/picoday.tcl

thats the file as it is at the moment. Currently getting a variable error on the !set_pic command.

[12:16:36] [12:16] Tcl error [pub:picoday]: can't read "mode": no such variable

Statistics: Posted by Weirdo — Thu Apr 10, 2003 7:19 am

Wee bit o help needed

2003-04-10T06:02:26-04:00

I have been nice, and produced a nice little script for you. It is a replacment for the "set" command, which you should only use of stored variables.

Code:

set setfile "/path.to.file/containing/vars"proc setsave {name value {type {}}} {  if {$type != ""} {    set mode $name    set name $value    set value $type  }  global $name  switch -- [string tolower $mode] {    {-init} {      if {[info exists $name]} { return $[subst $name] }      if {![catch {set int [set:read $name]}]} { set $name $int; return $int }      set $name $value; return [set:save $name $value]    }    default {      return [set:save $name $value]    }  }}proc set:read {name} {  global setfile  if {![file exists $setfile]} { return "" }  set fp [open $setfile r]  set list [read nonewline $fp]  close $fp  if {[set idx [lsearch -glob $list "$name *"]] == -1} { error "Not set here, do your thing" }  return [lindex [lindex $list $idx] 1]}proc set:save {name value} {  global setfile  if {![file exists $setfile]} { return "" }  set fp [open $setfile r]  set list [read -nonewline $fp]  close $fp  if {[set idx [lsearch -glob $list "$name *"]] != -1} {    set list [lreplace $list $idx $idx [list $name $value]]  } else {    lappend list [list $name $value]  }  set fp [open $setfile w]  puts $fp $list  close $fp  return $value}

Also download at http://www.ppslim.ukshells.co.uk/prov/e ... rapper.tcl

This has two uses, it will prevent set over-writting when you rehash the bot, so long as you use it correctly.

Use it like follows

When defining the default settings for a script, you normaly use the set command near the top of the file, but not in a procedure (proc). Replace

Code:

set defaultscriptsetting "value"

Code:

setsave -init defaultscriptsetting "value"

This does one of three things.

1: On a rehash, it will check to see if the setting exists, if it does, leave it as it is, and do not replace its current value with "value".

2: It will try and read the setting from a file (on start or .restart). If the setting is in the file, it uses this setting, instead of "value"

3: If not in memory, or in the file, it saves "value" to the file, and uses "value" as the setting.

When you create a command in a script, that is designed to changes a setting (EG, you make a public kick script, and you are using a command to change the DEFAULT kick message), instead of making the setting global and chanign the value, use the "setsave" command

EG, from

Code:

setsave -init defaultkick "Goodbye"proc kickchange {nick uh hand chan arg} {  #do some checking  global defaultkick  set defaultkick $arg}

This will only change it while the setting is in memory

CHange it too

Code:

setsave -init defaultkick "Goodbye"proc kickchange {nick uh hand chan arg} {  #do some checking  setsave defaultkick $arg}

Note there is no -init in this.

When there is no -init, it simply saves the new setting to the file.

This setsave only works on global variables. You then use the variables the way you normaly do.

These command just take care of the save and read functions.

Warning: I havn't tested the code in any way. If you have any problems, just ask.

Statistics: Posted by ppslim — Thu Apr 10, 2003 6:02 am

Wee bit o help needed

2003-04-09T19:00:05-04:00

Right, so definate writing to the first line of a variables file. perhaps could write something that could write new line for each time the script is set and a new pic set as $picoday, then add a line at end of file. Then, when !picoday is ran again, it checks last line of file, resets the variable, perhaps that can be done on reboot of the bot.

Got any links for file manipulation in this manner. Definately my weakpoint at the moment?

Statistics: Posted by Weirdo — Wed Apr 09, 2003 7:00 pm

Wee bit o help needed

2003-04-09T18:33:40-04:00

This would require that you save and restore the data amnualy to some form of database, be it a flatfile (simple write and read file) or full blown mysql DB.

The bot should survive a .rehash, so long as you don't overwrite the variable in the global context when reading the script.

EG

Code:

set a testproc blah {} {  blah}

When a rehash takles place, $a will be set to test, even if a change has taken place elsewhere in the script.

SOmthing like

Code:

if {![info exists]} { set a test }

Will stop rehash from overwritting it.

A .restart wipes the memory, and is in effect, the same as doing a ".die" and starting the bot from the shell, except the bot doesn't die. No variables survive this.

".die" means memory is totaly freed, and it doesn't survive.

and a PC reboot is obvious.

Statistics: Posted by ppslim — Wed Apr 09, 2003 6:33 pm