Re: Singleton? Or something else

I've created a number of classes that wrap some 2D functionality for
game programs.

Sprite
Image
Mouse

among others. I have another class called Paddle that derives from
Sprite and depends on the position of the mouse when its Update method
is called. Using an object of class Mouse is necessary because the
API I'm wrapping only provides the state of the mouse and not
transitional status such as just clicked, which I have to track.

In the Paddle::Update() method I need to check the position of the
mouse from the mouse object. But in another part of the program I
need to check the button click status. I'm not sure of the approach
to take. If I have a named Mouse object it needs to be visible to all=

parts of the program but because of the way the API is designed I
can't instantiate it as a global object nor would doing so seem
appropriate to a system that has such interwoven classes.

What I'm thinking of doing is making some of the functionality of the
Mouse class static so I can just call

if (Mouse.Clicked(1)) {...}

instead of

Mouse mouse;
.
.
.
if (mouse.Clicked(1)) {...}

Is this elegant or unelegant? Is here another solution? Am I being=

clear?

--
Lilith