It doesn't work like that.
I guess you're using mouse_b...?
If so, it just says whether or not the mouse button is down. Rate has nothing to do with it. You just need a variable that says whether or not the button was down last frame. This might work for your needs (untested!):

Ooh, so you're wanting a minimum amount of time a user can click? So if the user is clicking blazing fast, the mouse event that occurs will happen slower? In this situation, you'll have to add some timer logic to your code.

What you have above looks fine, what's the code you use for actually doing something when the mouse button is clicked?

The only time the mickey_left and/or mickey_right should be set to FALSE is when the "mouse_b & 1 (or 2)" is not set, like you did in the above code (a few posts up). You're setting it to false in the event, the mouse is still being pressed, so it sets it back to true and then the event sets it back to false. You've effectively defeated the purpose of the mickey_left/right flags.

You're right, I'm reading too skipilly (definitely not a word). Anyway, on the post above (the one where you first said "Still too fast"), notice how when you set mickey_left to true that that only happens once until mouse_b & 1 is not true? That's the logic you need for the actual event to happen. You can either put the event code in that logic above or create another boolean flag for each mouse button event.

Setting a flag to be true and then checking if that flag is true is the exact same thing as seeing if mouse_b & 1 is true.

I don't know if this might help, but in a game i've developed I had the same problem with the keyboard in that when a key was pressed the sprite moved multiple times instead of just the once.

The way I solved it was to use a variable for a key delay so that as soon as the key was pressed the key delay variable was set to a number, say 10, then each time through the game loop this variable was reduced by 1 until it reached 0. While ever the key delay variable was more then 0, any key presses for that key were ignored. This slowed down the key presses and you can use a different number in your key delay variable to slow the presses down to what you want.

So, I suppose you could use the same method for your mouse button, use a button delay variable so that as soon as the mouse click is registered, the button delay variable is set so that any future clicks will not register until the button delay is back at 0, and reduce the button delay variable each time through the game loop until it gets to 0.

You're welcome

I'm quite a newbie to C and Allegro and only written 1 game so far, but loads of ideas for new ones - is this code for a game ur developing? and if it is what, can u say wot ur developing?

Yes, this is a very bad thing, try to use just flags.

If you use a timer in your game the delay should reduce at the same rate on different computers. I thought the idea was not to get multiple mouse clicks from 1 click, so if someone holds the mouse button down it should register another click when the delay reached 0 after a short delay, and if the game requires it you should control how fast a user should be able to click a button

That's my opinion, but I've only just started developing games and that's the solution i've found so far