The problem with using == as a condition, is that its practically impossible to exactly get a situation where the values are "equal", due to the time calculation is calculated in milliseconds, and the values can be very high. And since the engine doesn't run once per millisecond, a equal condition might never be true, because the update might have taken 1 millisecond too long to be a match.
but I'm willing to test a equal condition, but its little different than a "ordinary" equal. I have added that if the time value is higher than the time at the previous update, and lower/equal to, than the current time during the current update, its considered equal and returns true.
I don't know how well it will work, so this needs to be tested properly before it can be accepted into the final code. But I'm releasing it now anyway so you can test it and see how it works.
I also added "Less or equal" and "Greater or equal" to the "Check counter value"-function.
New update is online! The latest version is now 1.07!
Check Counter Value
I added '==', '<=' and '>=' to the conditions in this function.
Although these conditions are still under testing (read above for more information), and they might change in later updates.
Remove Single Counter
his function removes a single counter from the Time Manager. I added this to get the option to remove unwanted timers that would only take up a spot in the Time Manager list and, in larger amount, more time to calculate active counters.
I hope this update will be of big use for all of you who uses this plugin. To get the whole change list and more information, go to the top original post and get the new update now!
Thank you everyone for your feedback, suggestions and support! <img src="smileys/smiley1.gif" border="0" align="middle">