Sorry if I was nasty.Didn't mean so.We all have life beyond.......;)

I wouldn't recommend doing it. Attention seeking modifiers would 'update' their script by doing minor, unnecessary things just to get their code at the top of the list.

Amy, Shhhh! I had plans for the smallest changes to even my old vb2 hacks. :cross-eyed:

You've ruined Bob's plan for World Domination now!!! :(

He was going to take over the world, one "updated" hack at a time... :(

Chris

Ermmm....I meant that this would bump the updated hacks in search for installed hacks not hacks listing

What would be more help would be this. If the author updates a mod, the status should show red 'updated' until we click a button that says we updated our board. (the button doesn't need to notify the author. just mark it for our own use) Then, when he updates again, the mod would go red again - indicating another update. As it stands now, it's useless for multiple updates.

I have no idea what Amy just said, but I agree with her general view that this is not needed - I can see which hacks have been updated just fine - in the list of hacks I have installed - the bright red sticks out a mile.

It should be a matter of just caching the output instead of outputting it immediately.

So right now there is a 'bit' template and you eval it evertime as you walk through the query results. Somewhere in there you determine if there is an update.

So, add the eval results to two different variables - $install_output and $update_output, and then don't actually output them until you've stepped through all the results.

Pretty minor change really.

What I said Paul is that the red should go away once we install the update. And the red should come back if the author updates the mod again. :D

Isn't that what happens now ? AFAIK, that's how it works. :)