egghelp/eggheads community

Channel-Specific Information

2003-02-18T05:41:58-04:00

It would be simpler to combine #1 and #2 together.

Store current settings in memory. Read them at startup, save them at shutdown, save/read on rehash.

Statistics: Posted by ppslim — Tue Feb 18, 2003 5:41 am

Channel-Specific Information

2003-02-18T04:40:44-04:00

Aren't files also inconvenient? You have to edit the file each time you want to change the setting. You may want to add a dcc command to let the owner change settings from the dcc console. That brings you the ease of use of #3 with the compatibility of #1 and #2.

Statistics: Posted by stdragon — Tue Feb 18, 2003 4:40 am

Channel-Specific Information

2003-02-18T04:40:05-04:00

hmm... on a slightly different topic, as I'm using the settings files for the moment... how would you count the number of files in a directory? (eg. the number of channels with settings)

either the search function doesn't like me, I'm blind, or it's not been asked

Cheers,

Mike

Statistics: Posted by mike-c — Tue Feb 18, 2003 4:40 am

Channel-Specific Information

2003-02-18T04:19:35-04:00

I've coded it using method #1 (setting files), and it works great....

I went off #2 as that is actually harder than #1 to change things (requires rehash)

#3 is the ideal, but if it's only on the cvs release, I guess i'll wait (I'm on 1.6.13 atm)

when 1.6.14 is out, i'll think about rewriting it

thanks

Mike

Statistics: Posted by mike-c — Tue Feb 18, 2003 4:19 am

Channel-Specific Information

2003-02-18T04:09:50-04:00

For #2, you're best off using arrays. Instead of having channame_setting1 as the var, why not have setting1(channame)? Then your config section will look something like

Code:

set setting1(#chan1) abcset setting2(#chan1) defset setting1(#chan2) ghiset setting2(#chan2) jklproc info_pub {nick uhost hand chan text} {  global setting1 setting2  set chan [string tolower $chan]  blah blah $setting1($chan)}

#3 is possible... but only with eggdrop 1.6.14 (current cvs version). Yes, people can access it with using the .chanset dcc command. If you want to do it, it goes something like:

Code:

setudef str setting1setudef str setting2proc info_pub {nick uhost hand chan text} {  set val [channel get $chan setting1]}

Statistics: Posted by stdragon — Tue Feb 18, 2003 4:09 am

Channel-Specific Information

2003-02-18T03:20:23-04:00

Hi,

Please excuse the length of this post, it needs explaining

I'm looking to write a script that gets channel-specific details, and uses them accordingly...

I've thought of 3 ways to do this (although i'm not sure if 2 of them are possible):

1) text file for each channel, 1 setting per line
2) have 'set channel_var whatever' in the tcl
3) Use .chanset settings

#1 I'm sure could be done easily, but this is not my preferred option, as it requires the editing of text files to change the settings (without writing fancy text editing code from dcc commands)

#2 I have attempted - I've tried various things but cannot get it to interpret the settings:

Code:

bind pub -|- "!info" Info_pubproc Info_pub {nick uhost hand chan text} {  set channel [string tolower $chan]  set mychannel_setting1 foo  }

If I use:Code: 
set Setting1 $[string trimleft $channel #]_setting1
the code later on puts this to the channel:Channel Info: $mychannel_setting1
(The channel is #mychannel) - it's returning it as a string, not the value of it.

Now if I use:Code: 
set Setting1 [$[string trimleft $channel #]_setting1]
I get a tcl error sayingTcl error [Info_pub]: invalid command name "$mychannel_setting1"
No matter what I try, it doesn't return the actual value of the variable... How can this be done? (if it can be)

#3 is my preferred method, but I'm not sure if it's possible...  Is it possible to store strings using .chanset, like you do with .chanset #mychannel need-op ...
... can you create custom settings?  And then how do you read those settings?


If you managed to read this far, thank you   I'm really stuck on this, i've been trying to solve it all night.  All help appreciated 

Cheers,

MikeStatistics: Posted by mike-c — Tue Feb 18, 2003 3:20 am