It is possible to include function key scripts which are multiple lines, but it involves locating them, replacing their alias with some other one and then adding that to your script..

sorry forgot a }

Code:
if $isalias(f3) == $true { writeini keys f3 }

quote:
Scripting and coding is like a woman you just have to keep workin her till she feels good
hahahahahahahhaa

aaaaaaaaaahhh yes very true :+)
then maybe just a if returned as $true a %var set
to set diglog as f2= as it opens
then that would let the user know not to set that one
just a thought

Code:
if $isalias(f3) == $true { writeini keys f3

like a little search engine
hope this helps

whobear: Hey, I'm glad you liked it! Anyway, your suggestion is well-taken and I've tried the $isalias() already. As I've said: the rework of the key function monitor will be somewhat difficult, but not too bad, based on the fact that my script already has xFx loaded as custom aliases, therefore the only way to have this work effectively with other scripts that contain custom function aliases would be to have a second .mrc file loaded that contains the list of F-keys and their entirety, of course removing those which are contained in other files.

There is, however, a catch to actual F-Key denomination. The problem lies within multi-line alias functions. ie:

alias F2 {
   multi-line-code
   is here
   and cannot be retrieved
   by $isalias(F2).alias
   You will only get:
   F2 {
}

I hope this makes sense and that I've been clear. Thanks again!

first, nice script Zmodem
this should help ya

$isalias(name)
Returns $true if the specified name is an alias command that exists in your aliases or scripts.

Properties: fname, alias

$isalias(join) returns $true if you have an alias for /join
$isalias(join).fname returns the filename in which the alias exists
$isalias(join).alias returns the alias definition for /join

this, if worked in to the script should show the fkeys if pre-existing function keys
exsample: if $isalias(f3) == $true { writeini keys f3 $isalias(f3).alias }
you will have to tweek it to work in your script

enjoy
hope this helps
and yes this is the Whobear from the colorteam.net

Okay, for those of you that have pre-existing function keys, for some reason this will not load those. I've tried $isalias().alias to retrieve your function's alias, but unfortunately when this snippet loads, it preemptively takes over the alias function, thereby making it impossible to retrieve your existing alias for your existing function key. If anyone can find a workaround for this, I'm all ears, but I ran through a series of tests and loops trying to do it and the only way I could even remotely think of would be scanning every script file and alias file for alias F and looking for lines that begin with that, as well as scanning the alias scripts and looking for any lines containing an F sequence, including cF and sF.

Eugenio: I'm still working on it finding the ones that you already have.

Still doesnt display any F-keys that I currently have but atleast it creates the .ini file for me and works.
/me rates 7

^Neptune: haha, it's funny 'cause I keep forgetting about $qt(). I always wind up doing it myself $+(",,") heh.

Update (28 August 2008):

1. This should make everyone happy, you no longer need to create the keys.ini file manually. When you load the snippet, it will do it for you.
2. Added a check for the F-Keys to make sure that isn't being returned, in which case you would get /: not connected to server.

I'm still working on finding out what to do about self-defined F-Keys when you load this file. I could use $isalias(), but I'm not sure about how to get the alias commands, especially if your F-Key has a long, drawn-out alias defined (ie: Multiples upon multiple lines). Any ideas are appreciated!

Heh, I think the problem lies with the filename . I had problems like this too. If the filename has spaces in it sometimes mIRC interprets the space as the end of the file.

Just always use $qt around the file to be safe :)

tbh I have to agree with pwnisher3, you should make it create it for us T_T

looks good but i don't want to make the document to use it

Another Good Idea Zmodem. This would obviously be great for someone building a new client.
Keep the new Ideas comeing. Good Work.

Hey, I'll have to check it out, but I'm pretty sure that I know what's wrong. The problem is I wasn't sure how to deal with people who already HAD function keys defined in their own alias/remote areas. This may present a problem, actually. I will return with more info later....

Yes I created the file with no luck
I dont think this worked for EL either......

I GET IT NOW! LoL. Let me redo the script and resubmit.

I cannot duplicate your issue at all, Eugenio. I've tried loading it into long folders and renaming the .mrc file to a long name, as well. I cannot seem to duplicate the issue. Anyone else?

Hopefully you didn't put the ini information in with the script itself. For instance, you've got a folder like this: C:|Program Files|mIRC|Function Keys Manager

Within that folder, you should have 2 files: fkeysman.mrc and keys.ini - (THIS IS NOT OPTIONAL, THE INI FILE MUST BE NAMED KEYS.INI)

So, you've got:

C:|Program files|mIRC|Function Keys Manager|fkeysman.mrc
and
C:|Program files|mIRC|Function Keys Manager|keys.ini

Right? Let me know!

On the other end, does anyone else seem to be having an issue with this?

I already have some Function Keys set but I dont see them in the list also it wont let me set or clear ones I already have since the only button I can press is exit, seems like you dont want me using your script.
/me cries

You did create a file called keys.ini and put all of the ini information, that I've included above the code, into it, right? That's the only time I could see the $null return. Also, make sure the keys.ini file is saved into the same folder as the mIRC script itself.

Dude i got Null on this=\