light toolbar beta

By sukhbira on Feb 13, 2013

well update this one very soon. this is very usefull toolbar
Author's Description:
DLL that lets you dock dialogs around mIRC's Client area. You can also show/hide mIRC's switchbar/toolbar/menubar with the dll that uses mIRC's internal values for these.
Download ultradock.dll
http://www.mirc.net/projects.php?download=1092687442

dialog operator {
  title "Quick Control"

  size 0 -0 615 44

  button "+o", 1, 0 0 22 21
  button "-o", 2, 0 22 22 21
  button "+v", 3, 22 22 22 21
  button "-v", 4, 22 0 22 21
  button "k+ban", 5, 44 0 44 44
  button "+ochan", 6, 88 0 44 22
  button "-ochan", 7, 88 22 44 22
  button "infochan", 8, 132 22 44 22
  button "infonick", 9, 132 0 44 22
  button "Why", 10, 176 22 44 22
  button "Whois", 11, 176 0 44 22
  button "sop list", 12, 220 0 44 22 
  button "aop list", 13, 220 22 44 22
  button "sop del", 14, 264 0 44 22 
  button "aop del", 15, 264 22 44 22
  button "ak add", 16, 308 0 44 22
  button "ak del", 17, 308 22 44 22 
  button "ak list", 18, 352 0 44 22
  button "mdeop", 19, 352 22 44 22
  button "whois", 20, 396 0 44 22
  button "Ping", 21, 396 22 44 22
  button "+MR", 22, 440 0 44 22
  button "-MmiRl", 23, 440 22 44 22 
  button "+c", 24, 484 0 44 22
  button "-c", 25, 484 22 44 22
  button "join", 26, 528 0 44 22
  button "nick", 27, 528 22 44 22
  button "identify", 28, 572 0 44 22
  button "id chan", 29, 572 22 44 22
  button "",111, 0 235 120 10, OK default

}
on *:DIALOG:operator:sclick:1:{
  if ($me isop $active) {
    mode $active +o $snick($active,1)
  }
}
on *:DIALOG:operator:sclick:2:{
  if ($me isop $active) {
    mode $active -o $snick($active,1) 
  }
}
on *:DIALOG:operator:sclick:3:{
  if ($me isop $active) {
    mode $active +v $snick($active,1)
  }
}
on *:DIALOG:operator:sclick:4:{
  if ($me isop $active) {
    mode $active -v $snick($active,1)
  }
}
on *:DIALOG:operator:sclick:5:{
  ban $active $snick($active,1)
  kick $active $snick($active,1) %rona
}
on *:DIALOG:operator:sclick:6:{
  chanserv op $active $snick($active,1)
}
on *:DIALOG:operator:sclick:7:{
  chanserv deop $active $snick($active,1)
}
on *:DIALOG:operator:sclick:8:{
  chanserv info $active
}
on *:DIALOG:operator:sclick:9:{
  nickserv info $$?="what nick you want to info?"
}
on *:DIALOG:operator:sclick:10:{
  chanserv why $active $snick($active,1)
}
on *:DIALOG:operator:sclick:11:{
  whois $snick($active,1)
}
on *:DIALOG:operator:sclick:12:{
  chanserv sop $active list
}
on *:DIALOG:operator:sclick:13:{
  chanserv aop $active list
}
on *:DIALOG:operator:sclick:14:{
  chanserv sop $active del $$?="who u wnat del from sop list"
}
on *:DIALOG:operator:sclick:15:{
  chanserv aop $active del $$?="who u want del from aop list"
}
on *:DIALOG:operator:sclick:16:{
  chanserv akick $active add $$?="enter hostmask to addit to akick list"
}
on *:DIALOG:operator:sclick:17:{
  chanserv akick $active del $$?="enter hostmask delet from akick list"
}
on *:DIALOG:operator:sclick:18:{
  chanserv akick $active list
}
on *:DIALOG:operator:sclick:19:{
  chanserv mdeop $active
}
on *:DIALOG:operator:sclick:20:{
  /whois $nick
}
on *:DIALOG:operator:sclick:21:{
  ctcp $snick($active,1) ping
}
on *:DIALOG:operator:sclick:22:{
  mode $active +Mm | /timer 1 30 /mode $active -mRi
}
on *:DIALOG:operator:sclick:23:{
  mode $active -MmiRl
}
on *:DIALOG:operator:sclick:24:{
  mode $active +c
}
on *:DIALOG:operator:sclick:25:{
  mode $active -c
}
on *:DIALOG:operator:sclick:26:{
  join $$?="enter #channel name to join!"
}
on *:DIALOG:operator:sclick:27:{
  nick $$?="enter The new nick "
}
on *:DIALOG:operator:sclick:28:{
  nickserv identify $$?*="Enter Your nick password"
}
on *:DIALOG:operator:sclick:29:{
  chanserv identify $$?="Channel Name With #"$$?*="Password For The 
  Channel" 
}
alias toolattivo {
  dialog -ma bar bar
  dll Dlls/UltraDock.dll Dock 0 $dialog(bar).hwnd bottom bar
} 

Comments

Sign in to comment.
Sorasyn   -  Feb 13, 2013

It's important to include all resources required for the posted snippet to function. I see you call the use of a DLL, yet have no link to the DLL, nor is it included with the snippet. Along with multiple executables, and sound files.

Be sure to "mainstream" your code so it doesn't require an enormous amount of adaptation to operate even partially proper. Personal code make bad snippets to share for that very reason.

Hawkee  -  Feb 14, 2013

Yes, and please title your snippets and descriptions with proper case and punctuation. Using all lowercase looks very sloppy. Just put a little more effort into your posts.

Sign in to comment

Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.