Passing variables via click boxes?

So i was trying to come up with a clickbox method for healing in EQ. And opposed to writing a separate mapped keys for each healer, each heal, and each slot (which could come out to about 100 seperate mapped keys if you have 3 healers), i was wondering if there was a way to pass a slot variable via which box was clicked in a click bar. For example. If i have a click bar covering each of the 6 slots in a group. And i clicked box 1, it would pass a variable to the mapped key of "1" so that i could simply use Target Slot 1 variable keystroke as a method of targeting. That way i could reduce the number of mapped keys down to about 10-12. (provided i have a fast heal, slow heal, and group heal or hot for each of the 3 healers).

Or am i pretty much stuck simply making the 100 mapped keys for each heal type and slot # combination for each healer? Thanks for any help!

[lax]

You can use a Variable Keystroke Action that does "Target Slot {SLOT}", which is literally what the "Target Me" Mapped Key under Non-combat does. Or you can use a Do Mapped Key Action that does "Target Me" under Non-combat, with a Target of Window:Current (the "Me" in this case being the Target for the Action, so you would have whichever window they should Target do this, i.e. the window you're playing from).

You absolutely do not need 100 mapped keys for each heal type and slot # combination for each healer, no.

[bob]

There is a guide for that...

HOW TO: Click Bar healing
HOW TO: Advanced Click Bar healing

I understand there are guides on how to make click healing bars, and that there is the {slot} variable used in the Target Slot {Slot} variable key. This is what i was trying to utilize. The thing with the guides are, they are established. I'm just starting to learn ISBoxer and i find the best way to learn is to figure out new ways to do stuff on your own. So was simply curious if click boxes could pass a variable of WHICH box was clicked, to utilize in the Target Slot {Slot} variable key. For example: You name Button 1 "1" and button 2 "2". And lets say *hypothetically* the button passes the name of which was clicked through a variable called... say {button}. Ergo, i could write a key map that executed "Target Slot {button}". That way if there are 6 buttons, one keymap could potentially target all 6 slots depending on the variable passed by the which button was actually clicked. That's all. The guides are nice, just trying to come up with my own methods to learn the application better. But thank you for the suggestions.

[bob]

The guides are there to take you through the process of setting up click bars that can target a specific slot (or character if you like) in your character set depending on which button you happen to be on/over. If you use them for healing or something else, that is your choice. Most learning of stuff is doing by rote (whether verbal/written/action) and (hopefully) understanding via the same process. If you don't learn by following, and feel the need to try and figure it out on your own with no guidance, then you need to be able to search for stuff in the Manual (well, actually the WIKI, but it is called manual on the ISBoxer.com homepage).

As to variables, a search of the WIKI provides these.
http://www.isboxer.com/wiki/Variable
http://www.isboxer.com/wiki/WoW:Macro

Of the two, only the first will be applicable to EQ, so in fact, ISBoxer is pretty limited to variables as it goes.
The most common one is where {SLOT} is used to replace the current active slot number in a bunch of mapped keys, and you can see examples of this in the Standard MMO setup for Assist and Follow, where "Target Slot {SLOT}" will translate to "Target Slot 1", "Target Slot 2", "Target Slot 3", etc depending on the active slot number. On the odd occasion {SLOTx} (replacing x for a number) will work despite not being listed in the first link (the behaviour is the same as that noted in the second link).

IMO the most difficult part to get your head around is probably Targets, and how self (Window:Current) and targets not self apply.

edit: To answer the specific question of can a button pass a variable of the button number?, No it cannot. The only variables in ISBoxer 1 (well, this is v41 if you are following the current build numbers, but it is really ISBoxer v1), are are those noted in the links above.

Oh don't get me wrong. I've read all the guides. I was simply trying to find a different method of achieving it that could possibly be more modular, than what everyone else uses. It's just a learning method. And I've searched the manual (I'm a programmer, kind of have to get good at that), i just wanted to make sure i didn't miss something or if anyone had an idea of how to achieve an emulated variable.

[bob]

I emulate variables in a couple of ways

1. Action Target Groups, which you can use an Target Group Action, to enter/leave the group. Then other actions are configured to target the members of an Action Target Group. I use this setup to control a large in/out menu. The setup is a little convoluted and getting it to initially display the current setting takes almost as many mapped keys as the actual enter/leave setup. All in all I have about 100 mapped keys behind this (they are fairly repetitive, but needed because I have a higher level execution that uses {SLOT} and then runs the appropriate lower level numbered mapped key). I looked at ways of simplifying the setup and found that it wasn't really possible to do so (currently), and if I was programming it and did not have access to a loop (Do, While, Loop, For, Foreach), this this would take just as many steps too. That is probably the way to think of this method. A language with no loops.

It may be possible to do this in an easier manner if I wrote a program myself in Lavishscript, but I was interested in doing something in ISBoxer that others could use to. At some point I'll do the writeup so the steps can be seen.



2. Virtualization, or more specifically a Mapped Key Virtualization Action. This is pretty similar to that above, except it uses substitution of Sets of mapped keys. Depending on whether a character is healing or tanking, then I can swap in and out of specific rotation sets that all respond to the same keypress. The basics of this are covered in http://www.isboxer.com/wiki/Style:MMO_-_Pro, and there is a bunch of videos http://www.isboxer.com/forum/viewtopic.php?f=11&t=6826.
I've taken this a little further in that you can stack the virtualisation chain, but I have found little practical use for this, and you end up spending far more time fiddling than playing.

3. Similar to virtualization, Key Map State Action, which are in the Advanced Click Bar guide, and turn on and off Key Maps depending on where the mouse is (well, over a clickable button anyway). In the guide I made it simple with only the one Key Map, but it doesn't have to be.

[lax]

Oh don't get me wrong. I've read all the guides. I was simply trying to find a different method of achieving it that could possibly be more modular, than what everyone else uses. It's just a learning method. And I've searched the manual (I'm a programmer, kind of have to get good at that), i just wanted to make sure i didn't miss something or if anyone had an idea of how to achieve an emulated variable.

Passing parameters is just plain built into ISBoxer 2, which is currently in alpha. If you are really intent on a different, more modular method, I would not spend a lot of effort on it because it will just be handed to you on a silver platter in a matter of time here. (ISBoxer 2 is free software for Inner Space, just like ISBoxer 1. You will not need to make any separate payment for ISBoxer 2. Instructions for joining the Beta http://isboxer.com/wiki/ISBoxer_Beta -- beta will begin soon)