Jump to content

Dan*

Members
  • Posts

    19
  • Joined

  • Last visited

About Dan*

  • Birthday 06/14/1991

Profile Information

  • Gender
    Male
  • Location
    Victoria, Australia
  • Country
    Australia

Dan*'s Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi again, Well with the bracket mis-match, is there any other code in that file which your dialogs are in?? Like, do you have an on START event or other events or alias's which are above your dialogs code, so it may be a mis match with those features rather than your dialog code?? If you paste or attach the whole file, I'd be happy to help you correct bracket problems Hope to hear from you soon Daniel
  2. Hey there, Well I dont mean to be too mean, but your code is fair messy especially with the Mis match of Brackets and dialog sidebar* { function which is left there.. and Obviously there is either other code in the same remote file which has an open bracket! I would highly recommend sorting it, because I do not believe things can function properly with mismatched Brackets, and especially if you close brackets in not the correct order... However By saying this, there could be many issues relating to your general problem... Some including... 1. Opening a new sidebar dialog and making it automatically dock, especially when there is already another dialog docked in the same position. 2. Your version of mIRC and your version of Rebar.dll for docking.. That could be an issue ?? Solutions.... A simple solution could be, just using 1 dialog structure, and hiding specific dialog controls?? So that when you click Next or back it hides and shows certain controls Including Icons and Images This I'd recommend as a better alternative instead of closing and re-opening dialogs! I'm a bit of a fan of DCX especially when people like yourself try a much more graphical interface... The DCX dll also includes a docking system, plus loads more features, including a few more options which include panels and layers, which in your case, could be possibly make it easier to hide and show different controls... I don't know if you have looked at this etc.. but it's only a suggestion Hope this helps Kind Regards, Daniel
  3. mmm, Well I did test the code out (Without MDX), and it seemed to add a variable called %password <my password> However your code has many issues with here is a copy of some edits I've made, to remove some of the errors ;------------------------------------------------------------------------------------------------------------------------------ ;------------------------------------------------------------------------------------------------------------------------------ ;------------[ Email Dialog ]-------------------------------------------------------------------------------------------------- ;------------------------------------------------------------------------------------------------------------------------------ alias signin dialog -m sign sign alias csign { dll $rebar UnDock center | dialog -x sign sign } alias rebar { return dll/rebar.dll } dialog sign { title "Pass Word Dialog [ /signin ]" size -1 -1 191 73 option dbu icon photos\icon.ico, 0 edit "", 1, 37 15 78 10, return autohs text Email:, 2, 9 16 25 8, center edit "", 3, 37 29 78 10, pass return button "Add", 4, 116 15 19 10, flat button "Delete", 5, 116 29 19 10, flat text Password:, 6, 9 30 28 8, center edit "", 7, 37 43 96 10, read return text Nick:, 8, 9 45 25 8, center box , 12, 5 10 182 47 box , 13, 5 10 134 47 button "Ok / Cancel", 14, 70 59 37 9, ok cancel text "By &Aimz ©2010", 11, 124 62 65 8, center edit "Pass Word Dialog [/PASSW]", 15, 50 4 80 10, center box "", 16, 2 0 188 71 icon 9, -38 -65 291 274, images\back.jpg, 0, noborder icon 10, 141 17 43 37, images\middle.jpg, 0, noborder icon 17, 2 74 187 126, Images\small.jpg, 0, noborder } on *:dialog:sign:init:*: { .timer -m 1 1 sign.an did -ra $dname 3 %password did -ra $dname 1 %email did -ra $dname 7 $buzz.decode($me) .splay mepart.wav | .timer.p 1 1 splay password.wav dll $rebar Dock $dialog($dname).hwnd > center dll $mdx SetMircVersion $version dll $mdx MarkDialog $dname dll $mdx SetFont $dname dll $mdx SetColor $dname dll dll\mdx.dll SetBorderStyle 1,3,2,6,8,2,6,7,8 14 50 Georgia Bold dll dll\mdx.dll SetColor $dname 1,3,2,6,8,2,6,7,8 text $rgb(%list1colour,%list2colour,%list3colour) dll $mdx SetFont $dname 1,3,2,6,8,2,6,7,8 40 Georgia Bold mdx SetFont 1,3,2,6,8,2,6,7,8 +a 12 100 Verdana colorize } on *:dialog:sign:sclick:*:{ if ($did = 4) { $iif($did(1), set %email $did(1)) | $iif($did(3), set %password $md5($did(3))) | .splay Data.wav | .echo $active 0,4Email & Password 0,12Added } if ($did = 5) { .unset %email | .unset %password | .echo $active 0,12Email & Password 0,4Deleted | did -r sign 5 } if ($did = 14) { .splay zip.wav } } alias refresh { did -r sign 5 } alias colorize { var %x 1 :lp dll $mdx SetDialog $dname bgcolor $rgb(155,0,0) dll $mdx SetColor $dname %x background $rgb(155,0,0) dll $mdx SetColor $dname %x text $rgb(255,255,255) dll $mdx SetColor $dname %x textbg $rgb(155,0,0) inc %x if (%x == 100) { goto nd } else { goto lp } :nd } alias sign.an { var %i 0 while (%i <= 191) { dialog -srb sign -1 -1 %i %i var %t 1 while (%t <= 73) inc %t inc %i } .timer -m 1 1 sign.tbar | .splay mepart.wav } alias sign { if ($dialog(sign)) { dialog -c sign sign dialog -mado sign sign } else { dialog -mado sign sign } } alias sign.die { var %i 231 while (%i >= 0) { dialog -srb sign -1 -1 %i %i var %t 1 while (%t <= 73) inc %t dec %i } dialog -c sign } alias -l sign.tbar { var %i 0 while (%i <= 24) { timer.tbar 1 0 dialog -t sign $left(Email Dialog,%i) var %t 1 while (%t <= 400) inc %t inc %i } } Okay, I haven't tested this new edit version But I'll explain some of the fixes I performed.. To my knowledge the /loadbuf command needs a filename specified to allow it to function... the .loadbuf command.. had not been specified a filename to perform correctly, so you would of experienced some "/loadbuf" error.. There were also 2 if ($did = 4) events, Pointless in my eyes... So I removed it to 1... You had a miss match with your brackets... you had 2 dialog sign{ } commands.. You had 2 alias's which performed the same command.. stick to 1 for every function Example: alias sign { dialog -m sign sign } and signin {dialog -m sign sign } But, apart from that try it See what works etc.. As I mentioned at the start, I tested your original code by removing the icons and MDX.. and it worked However my edits are based on just knowledge, and you could be experiencing these problems down the track Unlikely, but your problem may also be not evalutating the $did(3) in the $md5() identifier, but this shouldnt be the case because I tested it without adding $eval() or [ ] brackets to evaluate it before hand Hope this helps Kind Regards, Daniel
  4. Dan*

    Away Alias

    No worries mate, It's likely to be a bug or issue with DCX.dll rather than the mIRC Client. This is due to the xdock feature and how it docks into the Toolbar, because without the DCX.dll you wouldnt have the feature of even docking to the Toolbar itself.... Anyway, Glad I could help =) Kind Regards, Daniel
  5. Dan*

    Away Alias

    Hey there buddy, Yea I encountered a similiar problem mate! I had a little bit of a look through the help file and found the mIRC Command /toolbar... Now I'm not very familiar with this command, however after a little bit of playing with it, I discovered I could change the size of the icons... This example below may not be the best one, but at least its a start and you could try The default size of the mIRC Toolbar Icons is I think about 16x16... So what I did was clear the whole toolbar... by typing: /toolbar -c Then I added a button to the toolbar with a larger icon size... by typing: /toolbar -axk0n2z2u test testing mirc.exe Then I opened my DCX Dialog toolbar to dock in the toolbar I've just made using the /toolbar commands... Suggestions: What you could do instead of typing this /toolbar code all the time is once you've done the above commands, you could save the changes in file by typing: /toolbar -fs Then on START your mIRC will automatically load your new changes! If you dont want this, then I'd recommend you adding the /toolbar commands into an alias so you can choose when to modify the toolbar Also to help you, heres a quote from the mirc.hlp file which shows what the different flags mean from the /toolbar command. Hope this helps you get an idea of it all... Just one last thing, I think 32x32 sized icons on your DCX Dialog is the max that will fit on the toolbar... for when using this technique I've shown.. Kind Regards, Daniel
  6. Dan*

    Mdx To Dcx

    Um.. Good try, but unfortunately its not correct... From using your code... you need... to have a your DIALOG EVENT commands.. then a seperate Alias which will be your callback... on *:dialog:k_bart:*:*: { if ($devent == init) { dcx Mark $dname k_bart_cb xdialog -b $dname +mntyz } } alias k_bart_cb { if ($2 == sclick) { if ($3-4 == 1 1) echo -s Testing this! } } Notice the k_bart_cb in your Dialog INIT where it has... "dcx Mark $dname k_bart_cb" This means that it has already set your CallBack Alias... All you need to do is create the alias... That is where the alias "k_bart_cb" comes in... Using the the Guide of... You create an "If Statement" saying.. if ($2 == sclick) AND if ($3-4 == 1 1) THEN echo -s testing! Just like the alias shows! Does this make sense?? Hope this helps, Kind Regards, Daniel
  7. Dan*

    Mdx To Dcx

    Hey there, Just to extend on what Travis was saying, I thought I'd provide you with a sampler, just to help you out so you can know what to do Cause DCX is a tad tricky especially when your new to it! ;// So you have your Dialog Table... dialog mf_tb_table { title "" size -1 -1 625 37 } on *:DIALOG:mf_tb:init:0:{ ;// YOU NEED THIS!! It allows the Call back alias to work! dcx Mark $dname cb_function xdialog -c $dname 1 toolbar -3 -3 496 34 flat top list tooltips arrows tabstop xdid -l $dname 1 32 xdid -m $dname 1 0 xdid -w $dname 1 +n 0 C:\Users\Liam\Kaleidoscope\sys\k.ico xdid -a $dname 1 1 +cv 100 1 $rgb(255,0,0) Button $chr(9) Tooltip ;//Docks toolbar .timertb_dock 1 0 xdock -m $dialog($dname).hwnd +t } alias cb_function { if ($2 != mouse) echo -s $1- } Okay, so thats the full example code, and just to explain bits of it.. In your INIT Dialog Event, you need to have a line such as: dcx Mark $dname <callback alias> This allows the dialog to know that, when theres activity with the mouse, or keyboard involving the dialog... It will resort to reading this alias... (In basic terms) alias cb_function { if ($2 != mouse) echo -s $1- } Is your call back alias.. (You can change the name whatever suits ) So what this above alias does is, when your dialog is open, test your dialog by clicking on buttons or typing in edit boxes, and in your status window, you will receive a DEBUG type of code, something like... So.. basically these are general ideas... So how do we put all this so something happens when I click a button.... We go back to your callback alias.. and enter the neccessary code! alias cb_function { if ($2 != mouse) echo -s $1- if ($2 == sclick) { if ($3 == 1) && ($4 == 1) echo -s Hello I clicked the button!!! } } The above example is for a toolbar button, while the below example is for like a button and a toolbar! alias cb_function { if ($2 != mouse) echo -s $1- if ($2 == sclick) { if ($3-4 == 1 1) echo -s You click the Toolbar Button! elseif ($3 == 4) You clicked a button! } } Anyway, I've started to babble a bit, so I'm sure you can see and get the idea behind it! Hope this helps! Kind Regards, Daniel
  8. Glad you found yourself a comfortable forum mate Looking great mate! Keep up the good work Kind Regards, Daniel
  9. Dan*

    Nick List Icon

    This download file should help you, all you'd need to do is change the paths of the icons, so they suit your icons http://www.tg007.net/dls/index.php?action=file&id=1322 Hope this helps, Kind Regards, Daniel
  10. Hey there Cyanide, Sounds like your on the right path for what types of protection you want, however if you are concerned about a room take... There is a little bit of protection server side with the introduction of the "SuperOwner" (Mode +Q). This allows full control of the room, and the user who created the room will have this status of Super Owner. The rules of a Super Owner is that there is only 1 Super Owner per room This Super Owner would probably be your life line to helping your room from being taken over Though, for other owners and hosts, there is just the standard use and they may possibly be kicked or even removed of the privledges if someone tried to take over the room Anyway, I hope this clears up your thoughts on Room Takes Kind Regards, Daniel
  11. Ah fair enough, My Bad there haha! I was just using this example and saw the issue which i thought was an issue! haha Sorry bout that, I'm interested though in a better method?? Would it involve Hash Tables? Kind Regards, Daniel
  12. Hey there, I know this topic was posted years ago, but only recently discovered the idea of the findfile2 function thanks to warrior! However just thought I'd help out and fix a little bug with the above code... This was the previous Code: alias findfile2 { if (!%findfile2. [ $+ [ $1- ] ]) || (!$exists(%findfile2. [ $+ [ $1- ] ])) set %findfile2. [ $+ [ $1- ] ] $shortfn($findfile($mircdir,$1-,1)) return %findfile2. [ $+ [ $1- ] ] } This works fine, but if mIRC cannot find the file, it will still create a blank global variable... For example: If you use $findfile2(mdx.dll) and it cannot find the file, it will still create a global variable called %findfile2.mdx.dll However this variable will be blank! A possible fix is provided below: alias findfile2 { if (%findfile2. [ $+ [ $1- ] ]) && ($exists(%findfile2. [ $+ [ $1- ] ])) return %findfile2. [ $+ [ $1- ] ] else { var %file = $findfile($mircdir,$1-,1) if (%file) { set %findfile2.[ $+ [ $1- ] ] $shortfn(%file) return %findfile2. [ $+ [ $1- ] ] } } } Hope this helps Kind Regards, Daniel
  13. Hey there buddy, Yea you can do this but you need to use a .DLL file which will provide a helping hand!! haha On the downloads here at TG007, you can download either SmilesView.dll or imgmirc.dll I think the SmilesView.dll is more popular however... Anyway here are the 2 links, I'm not sure if there is another dll or something else out there which will help, if there is I'm sure another member will point you in the right direction.. SmilesView.dll is: http://www.tg007.net/dls/index.php?action=file&id=846 imgmirc.dll is: http://www.tg007.net/dls/index.php?action=file&id=849 I'm pretty sure both downloads will contain information about how to get you started Hope this helps, Kind Regards, Daniel
  14. haha, wow thats amazing!! Way to much time on this mans hands haha, but very clever and imaginative!
  15. Thanks chain for the handy link Kind Regards, Daniel
×
×
  • Create New...