Implemented this a couple of days ago, but just realized it isn't working right. You DO need the +1 for real-time, but not for game time. Geniuses they a'int.

Ya it does bug me. I'd really like to see the fix rolled into the next zip especially since it's trivial.

I'd buy that argument _maybe_ for the numerical month value, but not for the stringification routine. The internal representation should never matter to that.

If you want to learn to program, the best way is to program. After about twenty years of it you'll start to get good.

Type libraries are related to COM interfaces. MQ2 doesn't have one. You'll have to settle for the compiler generated browse information.

Okay, it took a full Norrathan year, but I've verified this as a bug. The month number goes right from 13 for December to 2 for January. There is no month number 1.

eqjoe wrote:Edit the source to his plugin to call your macro.



-j

Obvious and wholy not the point. I want the buttons to be configurable from within EQ, not to require a recompile of the plugin every time I make a change.

When you call a macro it ends the macro currently running and starts the new one you called, it doesn't return to the original one. What you need to do is add Sub functions inside the macro already running, and in these functions you should specify what the other macros you have, do. Well aware of ...

This is not normally something I do, but it seemed the simplest solution when using the MQ2MyButtons plugin (i.e. have a set of fixed macros called by the buttons which then called your custom macros). The problem I'm having is that apparently the first /declare in the called macro is not being reco...

I thought I might have missed that "extra" month, but it's been a day and a half and we're still in "January". It's looking like all the months have the month number high by 1.

Fair enough. If DisplayName is what I'm looking for and it gets documented that should solve the problem. I think you may have been looking at the wrong code though. CleanName does _not_ move the article though there may be an internal routine with the same name that does or perhaps there's a flag. ...

Nice try, but the new month (if any) would appear to come before January (2) not after December.

Rusty~ wrote:i've just been using ${Target.DisplayName} over ${Target.CleanName}

Bah. I'll look at this, but "DisplayName" is not in the docs and may well go away. (I have verified that it exists and that you aren't insane, but my statement stands).

Amadeus wrote:I have this fixed ...will put it in for the next zip.

Thanks

One of the first macros I made when I started using MQ2 was an assist macro. I was using it in an LDoN and it worked fine until we came upon a named. My macro (using the target's CleanName) output something like "Assisting OurTank with #Whirling Pain in the Ass". I'm still trying to figure...