Why is Raz's AutoAttack timer code so crazy?
 

I don't understand why Raz's code seems to be more complicated than it really should be, am I missing something? I made one of my own that's like 10kb or so with just a composite and a few OnShow/OnHide triggers and it performs beautifully...am I missing something?

:) and :D and :nana:

(and I have no idea, I think it was just his code evolution)

Lol. I've had code evolution like that before, but usually when it gets out of hand I can't stand it and re-do it.

Prettｙ much though the problems people have with it are the dynamic data. I have a file that is nothing but progress bars and it runs into the same problems. (unless things have changed) Kind of ironic too!

EDIT: WOW WHY DOES IT HAVE A LITTLE ANGRY FACE THERE!!!

The only big problems that I see with it are when it is at 100% or 0% it is still visible. Because of this it requires a big workaround that doesn't even work completely.

I could probably make it WAY EASIER thinking about it. Gm9 pretty much hit it on the head though. I coded it from my original code, then dynamic data was added. Then after that it was changed a few times, at that point I could not be bothered to redo it every week.

I originally was going to clean up your code, but your code made my eyes bleed lol. Nonetheless I made one very similar to yours, but I started from scratch (I tried to use yours as a reference, but I couldn't) and tried to work out all the DynamicData problems with workarounds. You can take a look at the pretty simplified code if you want.

there is no workaround that I can think of, the problem is that it skips some times due to something with recovery time as far as I can tell.

Personally on windows 7 it has issues where it will stay 100% when auto attack is hitting/missing quite frequently, it is more stable on Vista for some reason. If you know why, and how to fix it, please help :)

Also ACT is set up to make a noise when auto hits, and on windows 7, it's randomly not doing it aswell. I'm thinking these issues in Win 7 are to do with write protected, since other programs seems to be having similar issues. But I'm not sure how to fix that.

I don't think it's just Windows 7. I'll do some more testing.

There needs to be at least some kind of OnEventFinished or something so we can get rid of some of these issues with progressbars. Or they can implement it w/in the data.

I was getting ready to patch some of the new stuff that got added! Though while I was doing that I saw this thread, updated it now. WAY less complicated, thanks for making me stop being lazy.

EDIT: I run windows xp still, I could reproduce it 80% of the time when I tested it last.

EDIT: T-T Hopefully not

I can't figure out what's wrong with my code. When I initially log on and do Ranged auto attack and then switch to Melee I can't see the Melee until pretty much the next encounter. Can anyone help find the problem please?

I played around with some ACT settings for beeps when auto attack goes off. It seemed semi-fixed after this. I think the problem might be server lag or something is wrong with my system that is affecting this and might not be Windows 7. My computer has been crashing every other day or so, and thus things may be wonky.

Since this is bumped let me ask! I loaded yours, mine and the test window I have made, I saw absolutely zero difference between them. So what was buggy about mine that yours fixed?

Well I was using an older version with your Razc ui before I made mine and there were a few things I didn't like. I'll try to check out your newest standalone version vs. mine.

I'm not here to compete. I tend to like to mod windows catered to my own needs.

After loading both of our updated and most recent code, I established within five minutes of testing that there are several factors that distinguish our mods from one another. Within the mentioned testing time, I saw no bugs in either of our mods.

Important differences/similarities:

Both of our mod's "core features":
- Functions as auto attack timers
- Horizontal resizeability
- Vertical resizeability that allows the user to hide the Secondary bar if so chosen
- Lock/Click through works flawlessly

Your mod "feature list":
- Toggles when you're hated

- Bars turn a different color when you're hated and not auto attacking

- If the frame is on, the Secondary bar does not remain visible when the Primary/Secondary delays are both the same

My mod "feature list":
- Toggles when auto attack is enabled/disabled

- Bars become tinted when auto attack is changed/disabled during an auto attack

- Secondary bar does not remain visible when the Primary/Secondary delays are both the same
- Bars turn red while you're casting
- 10%, 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90% visual indicators, which I will probably remove because their usefulness is minimal
- No "dead space"


Now to answer your question: I thought the "Toggles when you're hated" was some bug, obviously it was intentional.
Now to reply to your statement: Like I said in my previous most, I tend to like to mod windows catered to my own needs. The things that I listed on both your mod and my mod is what distinguishes our mods from one another. Everything I listed on both of our mod's "core features" is what you and me both implemented in our mods, which I like. Everything I listed on your mod is pretty much your "feature list", which I dislike. Everything I listed on my mod is pretty much my "feature list", which I like.

IMO, everything that has been mentioned above is enough to warrant two separate mods.

In no way did I take it that way bud, I was just curious about what bugs you had found.

As I mentioned in my previous post, I thought that the toggle when hated was a bug because with my Coercer I never had auto attack enabled when I was in combat, but the bars were up. I figured that was a bug.