Cadence

Thanks for the info, I really appreciate the help! Accursed typos. The sad part though is that that typo got in just before release, I have a bad habit of overhauling the code at the last minute as things occur to me, very bad habit.

As for the nil error, I was wondering about that, I was debating with myself whether it would be best to define the local text after the check (using a next() as table key validation) or whether I should simply set the text variable and then use a more simple 'if not text then'. I was using that originally but I switched over to the more complex version to be more professional. I should've gone with what works, that was silly.

Okay, I have both bugs fixed now. I'm just going to do a tiny bit of rewriting (to move where the local text is spawned, should've done that before release but I forgot) and to test, then I'll release it. Thanks again for the help.

(Edit)

Oh wait, I see it! The problem is actually caused (bad assumption on my part) by the lack of a return when the schedule is cancelled. Doy, that was foolish. Okay, this is looking good so I'll have a release ready soon.

(Edit)

There you go, that code should be much more sturdy at the end of a queue now, let me know how it goes.

No, thank you!

I'm going to have another release out soon, there's just another little change that's occurred to me that I want to make before I head into game. The defaults really should indicate which race they're meant for, so I need a naming schema for that. I'm likely going to use 'Title (Race)' so you'll all know which race a particular cadence is intended for.

As I understand it, the original cadences were put together by a talented group of people long ago for the original mod and they are very funny, I'd love to get some more in there though too so if anyone has any ideas, funny conversations, Horde-ish songs or just about anything else that would work, let me know and I'll see about getting it in.

Speaking of which, it's been fun to use so I am tempted to try to put together a few myself for the Draenei, since they're my current playing race. I have a few in there already which are just basically Russian folk songs (which suits the Draenei so well). I oft have my Draenei singing away whilst fishing (it's something to do). So if you happen to find a fishing, singing Draenei technoshaman, it's probably me.

In this new version, I've done a lot of general cleaning up and I've added the ability to call dynamic info from cadences. For example, [name] would call a character's name. Check out the manual for the full details.

If there are any dynamic-info tags that any of you would like to see, let me know and I'll see what I can do. Just about any string-based info from the API could be included but I'd like to stay away from stuff like iterating over the bags as that would bloat the code.

(Edit)

Whoops, I left one of my old test files in there, I often use those to test out pattern matching things because they never quite work in my head unless the Lua parser has looked them over. Mostly I delete them but this time I forgot. You can just delete that test.lua if you like (and any others you see in my Addons). Basically, no harm, no foul, just an unnessescary file.

Really?! I can't find that ...

I'll make you a deal though, if you can get me the table, the entries or point me at a place that has the version with the Gnome one in, I'll get it converted over post-haste. How's that?

Thanks! I try. I really do want everyone to enjoy my work as much as I do, so I take the time to put together the best manual I can. If you find any mistakes, typos or you have any suggestions towards building a better manual, let me know. Anyway, I do appreciate the compliment so thanks.

Just so you know, you can do that already by putting the following in a macro...

/cad add [Cadence Name]
/cad run

The queue wipes automatically on completion, so you don't have to worry about wiping the queue unless you stop it early. I just wanted to throw that out there though so you know.

With that out of the way, I certainly could add this kind of feature in. What you'd be looking for is perhaps a command that works like this?

/cad single [Cadence Name]

That would go through the process of the above two commands, basically, just combining them into one. If there are any features you want or any modifications to this idea, let me know. As soon as I've got confirmation that this is what you're after, I'll code it in.

(Edit)

Cripes, the size of the gaps between the editboxes and the text below is unholy. I've removed my own linedowns there.

Do you still want that feature, then? I'll put it in if you do.

Okay, second milestone. A lot of spit and polish in this release, I spent a while digging around in the murky depths of Dewdrop and FuBar to find out just what I could do with the menus, my findings lead me to rewrite how my menus and the icon work and I'm pleased with the results.

I've also got the single option in there (check out the manual for details but basically), it works as a toggle and when the mode is engaged, simply adding an entry will cause it to run automatically, so all that's needed is '/cad add [Cadence Name]' to start it going.

Well, that's it. I'm going back to bed.