toclafane1 you seem to forget that some times channels have a specific purpose and idling in them is not what they are for. channels to request vhosts are an example, you use a command to request a vhost and then you're supposed to leave.
this isn't for regular channels where people talk, unless the owner has a twisted sense of humor lol.
@toclafane1
why remove the #pball? the way it's setup now is to work in 1 channel.
@Jethro
Why would my approach be ill-advised? If there are 10 normal users in a chan there would 10 timers with my method. Your method would have a single timer but have to loop through all the nicks at once. Is there that big of difference there?
Well I was just going to have a dialog with editboxes for rgb colors, but since you had to step it up I'll be doing scroll bars and the editboxes. So you can either just type in the number you like or scroll around for something.
You can use /did -c tablename id value to move scroll bars, it's not really documented but i knew one of the things for selecting stuff had to work with scroll bars.
just updated my post above to add a feature so you can click it to switch 12/24 hour mode and a little bug where am/pm wouldn't be shown.
xdesoto you started quite the craze here with clocks, lol. how long until someone makes an analog clock?
update:
there was a competition 11 or so years ago about making an analog clock in mirc
Abcdefmonkey you aren't understanding what I say. You have to resize the pictures manually inside a photo editing program. or I'll just post an archive of them if that's too hard to understand.
USE THESE PICTURES FOR THE SCRIPT I PASTED
http://www.mediafire.com/?amb99ah60gqt0ns
Well I went with what Firstmate did at first but I wanted a fixed width font which i didn't find in a digital clock style. So I went and jacked the pictures used in the original script and made a toolbar clock.
(Update) I added 12/24 hour time. type /clock to start in 24 hour mode and /clock 12 to use 12 hour mode. You can switch back and forth while it's running and /clockoff stops and removes the clock. Also it'll set itself to start on start if you exit with it open.
(update 2) removed leading 0 when in 12 hour time.
(update 3 or so) clicking the clock switches it between 12/24 hour time and I fixed a little bug where the am/pm wouldn't show up if you started with 24 hour then switched to 12 while it was running
DOWNLOAD THESE PICTURES FOR MY SCRIPT
http://www.mediafire.com/?amb99ah60gqt0ns
alias clock {
if (!$toolbar(clocksep)) toolbar -is clocksep
if (!$window(@clock)) window -nBj2kpw0 +f @clock 0 0 117 22
if (!$toolbar(clock)) toolbar -aux clock "" @clock 0 0 $iif($1 == 12,111,82) 16
clear @clock
set -l %time $asctime($iif($1 == 12,hhcnncsstt,HHcnncss))
set -l %num 1
while ($mid(%time,%num,1) != $null) {
if ($mid(%time,1,1) != 0) || (%num != 1) || ($1 != 12) drawpic @clock $gettok(0 12 24 29 41 53 58 70 $iif($1 == 12,87 99),%num,32) 0 $scriptdir $+ $mid(%time,%num,1) $+ .jpg
inc %num
}
toolbar -pu clock @clock 0 0 $iif($1 == 12,111,82) 16
toolbar -l clock "/clockchange"
.timerclock 0 1 clock $iif($1 == 12,$v1)
}
alias clockchange { clock $iif($timer(clock).com == clock 12,,12) }
alias clockoff {
.timerclock off
toolbar -d clocksep
toolbar -d clock
window -c @clock
}
on *:exit: if ($timer(clock)) set %startclock $timer(clock).com
on *:start: if (%startclock) { .timer 0 1 %startclock | unset %startclock }
I'll see what I can do with the side listbox idea, then only one note window would be needed. Yeah I was also thinking about seeing if entries could be edited. Perhaps selecting a single line and hitting a key like "e" for edit would put that line back in the edit line and when you hit enter it'd replace that line with the new text. I think having a key to initiate the edit would be easiest since you wouldn't know if a selected line is supposed to be edited other wise.
You are misinterpreting how the notes are formatted. There is the name of the note @Note_1 and the content, which is made up of separate lines due to using the listbox mode of the @window. So the ini would be formatted like so.
[@Note_1]
[size]= 100 100 300 200
1=line 1 of note
2=another line of note
3=and so on
I also realize having the window be in listbox mode has disadvantages like lines don't wrap so the length of a line is limited to how wide you can make the window. However I wanted to be able to add multiple items to the note and be able to interact with them, something I don't know if you can do with normal lines in an @window
I wanted this to be a simple system so I used built in things like @windows, if you want a complex note system a dialog would be the best method but it's not what I was going for.
wow I like there is finally on topic discussion for one of my scripts. but for something that started as a three line script things are getting complex fast. for the argument of long lines, that shouldn't be a problem for multiple reasons. the window is a listbox so lines don't wrap so you can only see the part of the line that fits in the window and this is a notes script and the point of a note is a short message to remember something.
also personally i feel an ini would just be easier than trying to create some structure to manage different notes when inis have sections and such.
actually Jethro is on the right track. [] work fine in ini files in pre v7 and post v7 mirc, though if you update from pre v7 to post v7 you have to manually change the ~~ to [] since v7+ changed the ini routine or something. I encountered that in my WB script and having to manually change the ini file when switching from 6.xx to 7.xx was the only problem.
There shouldn't be any problem with [] in the text inside an ini, even the title can have [] in it and it'll work fine. In older versions of mirc [] were changed to ~~ in the title portions of inis but not with mirc7.
Yeah I know the code is messy looking, but I purposely did that ^_^
Though I do end up unjumbling it every time I work on it, lol.
Two things, one where is the part that auto joins and two you should probably remove parts if they aren't included. Like the $cdir you should either include that custom identifier or remove it and edit the script so people can use it without editing it themselves. I personally feel scripts should work out of the box, especially if they are being publicly posted.