Mattias Gaertner wrote:
I don't see, what registering a class has to do with. Maybe your
initialization section is too automatic?
Systray Icons don't really exist on Mac OS X. What exists is a Taskbar
Icon witch behaves somewhat like a System Tray Icon. i.e. he can be
drawn at will, and respond to mouse messages, etc.
There can be only 1 of those taskbar icons on Mac OS X, and I think it
is always visible. So, to ensure that the Icon is correctly initialized
with the Application, I set it to be created on the initialization
section. This way people can use the SystrayIcon object instead of the
class. It is the exact same idea behind Application, Mouse and Screen
objects.
This may be wrong, because I am not a Mac programmer, but it my best
guess of how I should go to support Mac OS X.
The object will include support for multiple icons (not very
multiplatform) on itself, so multiple instances are not necessary.
Making the visual component a wrapper around the SystrayIcon object will
make sure that if someone drops 3 components on his form, they will work
as one instead of raising errors.
Felipe
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
