Tareim's Macro Help

Use control key and '+' or control key and '-' to speed up or slow down the macro.

why after i mess with the stall options via the + - keys do the insert and delete stop keys break and stop working?

Sigh, I have the console version, which doesn't have a problem. I'll see if I can dig up the graphical version...

I'm not sure what that means? Because I only have one version of the source to a program I wrote many years ago, that mean's I'm bad? Strengthen your logic, then come back at me, please.

As for Rowbearking, please let me know which version you have, or where you downloaded it from, that way I can further look into it for you.

I find it very amusing that I can make a comment about a shitty programmer, and you solely assume its in reference to having only one version of the source code? Strengthen your deductive reasoning, then you'll understand the elephant in the room is that you are unable to write such a simple piece of software with the full functionality intended. The foolish kid was complaining that increasing or decreasing the speed breaks the functionality; it was also supported by Frosty.

Get at you.

Angeldust,

Frosty, I am clearly missing something, can you get me a link to the version you can get from this site?

Cool, now I know what to look for, let me see if I can find the source.

Update: I don't have the source anymore. I do have an older version, but it wouldn't be worth updating. The macro program was actually built for educational purposes. The entire point was to create a system which allowed creating windows in C++ with ease and without using Microsoft Foundation Classes. It was a fun project, but it was never meant to be used in any real manner. Maybe if Faldon ever flourishes again my interest will grow. In the mean time I will throw out there that I believe there was a version out there that fixed this issue. There was also a version that wouldn't macro unless you were in the Faldon window. Where these went, I cannot say.

Honestly it never should have had trouble with any interval, that's a huge oversight. What that means is it was checking the delay instead of accepting input for on/off. I'm surprised I would have let that slip, even more surprised that it wouldn't have been mentioned to me when I actually worked on the game.