ceil
Junior Beta Tester
Posts: 16
|
Post by ceil on Jun 29, 2007 10:39:48 GMT -5
This may be ludicrous or stupid, but I think it would be cool.
It'd be nice to be able to add script to run before or after a button push. Meaning, when I push a button, it would run a script, execute the button, then if I had ending script, it would run that.
Why do I want this? I want to add a /stopcasting macro to every button ,but I really don't to make an individual macro for every single spell. So sue me. It was just a thought.
|
|
wolftusk
Very Talkative Beta Tester
Posts: 140
|
Post by wolftusk on Jun 29, 2007 12:14:18 GMT -5
This may be ludicrous or stupid, but I think it would be cool. It'd be nice to be able to add script to run before or after a button push. Meaning, when I push a button, it would run a script, execute the button, then if I had ending script, it would run that. Why do I want this? I want to add a /stopcasting macro to every button ,but I really don't to make an individual macro for every single spell. So sue me. It was just a thought. I do not really understand what you mean. What would these pre and post macros do?
|
|
ceil
Junior Beta Tester
Posts: 16
|
Post by ceil on Jun 29, 2007 15:11:16 GMT -5
Internally, a Button is just a macro. I'd love to be able to append script to run before or after a button is pressed, without having to have it be an entire macro I make into a Lunarsphere button. So essentially, two internal macros for each button, one running before the action of the button, and one running after.
This would let us add things like checks and validations to buttons without the need to make a dozen macros that get lost easily, and all of it is stored in the LunarSphere mod data. I for one would love a /stopcasting macro before every spellcast, or to be able to do a level check on a target and cast a spell of appropriate level, things of that nature I am always wanting and having to make a ton of macros to do.
|
|
|
Post by lothaer on Jun 29, 2007 16:40:45 GMT -5
the spell by lvl is now Blizzard default. like on my Priest i only have to have my Max lvl Fort buff on my action bar and when i cast it on a lower lvl player it will automatically cast the max rank for for their lvl.
|
|
ceil
Junior Beta Tester
Posts: 16
|
Post by ceil on Jun 29, 2007 17:02:10 GMT -5
There are other purposes for such a feature.
It's just a suggestion. That's all.
|
|
|
Post by Moongaze on Jun 30, 2007 3:13:40 GMT -5
This can "kinda" be done. The nice thing about these buttons is that they can be assigned macros (which you already made) and macrotext (which is generated BY the addon and dumped into the button). Obviously, assigning a macro would require you to do the work ... and do it you would ... for every button (yuck) The macrotext offers more power, and is something I was thinking about tinkering with in the future. An example of this use would be for the new option under the "Drink" and "Food" groups for the Button click-type events. I'll be adding an option: "Drink best food and water" which will rely on "macrotext" which is dumped into the button, programmically. As for a "stop spellcast" feature, that can be added with the macrotext idea. The way I would impliment this would be something like the following: On the button settings window, there is a section near the bottom. It is split into two sections: "Pre-Click macro" and "Post-Click macro". Each section would have check boxes (one for each mouse click type) which would state which buttons get this addition, as well as a text box where you type your custom code. In the "Pre-click" box, you type in the macro to stop spellcasting. You then click all three click type checkboxes. This overwrites the original button's code (which just says to use an item, or use a spell) and replaces it with your pre-click macro AND the macro text to use your item or cast your spell. This, essentially, does what you would want. However the problem still remains: Do you just have one global pre-click and post-click macro that is applied to ALL buttons with a pre-click or post-click? Or is it a separate one per button? The global has it's benefits: you make it once, and use it for everything. But, you can't have two different pre-clicks. The per-button is good so you can assign it, per button ... but you will still need to make the macro text, per button, which is similar to making a macro button, for each button. With what you're asking, the global would make more sense, since you want to make sure that all spells have a "stop spellcast" before it is cast. If, in the end, you have 3-4 buttons that do level checks or whatever ... it would be best to just make a macro button and drag it to the sphere. Another option could be to add a few checkboxes to the button settings window that say: "Force cast-on-self," "Force cancel cast before casting assigned spell" and 1-2 others. Are any of these options suitable? Am I close? I can add this functionality to LS at a later time. I could totally see people using some of this functionality. I'll be looking into it after the public release. Thanks for the suggestion
|
|
ceil
Junior Beta Tester
Posts: 16
|
Post by ceil on Jul 10, 2007 10:24:01 GMT -5
I think I'd bear your children if you did.
I think the best way would be to be able to setup Pre-Click and Post-Click macros, and then have a fourth and fifth drop down selection per button that lets you select which one to apply.
|
|
|
Post by Moongaze on Jul 10, 2007 15:25:03 GMT -5
Alrighty. I'll be adding support for that in the future. Just need to wait a while (but it will be worth it =)
|
|