On Monday 07 September 2009, Jon A. Cruz wrote:
> On Sep 7, 2009, at 11:54 AM, Marco Martin wrote:
> > now i'm not sure about the current status of the tcp transport of
> > dbus, but
> > once it works i don't see particular problems, big endian machines
> > would have
> > to invert the bytes of the
On September 7, 2009, Jon A. Cruz wrote:
> On Sep 7, 2009, at 11:54 AM, Marco Martin wrote:
> > now i'm not sure about the current status of the tcp transport of
> > dbus, but
> > once it works i don't see particular problems, big endian machines
> > would have
> > to invert the bytes of the image
On Sep 7, 2009, at 11:54 AM, Marco Martin wrote:
> now i'm not sure about the current status of the tcp transport of
> dbus, but
> once it works i don't see particular problems, big endian machines
> would have
> to invert the bytes of the image by hand, that is something that
> somebody wi
On Sep 7, 2009, at 2:36 AM, Aurélien Gâteau wrote:
>
> A name like KSystemTrayItem would avoid such confusions. I know it is
> probably not very appropriate because it describe a visualization
> rather
> than the content, but I feel it would still be better than
> KNotificationItem (Think about
On Sep 7, 2009, at 10:11 AM, Marco Martin wrote:
> At the moment, (should make it more clear in the spec) is ARGB and
> is not
> designed to be network transparent, so the endian should be the same
> of the
> machine for both the client and the server
I'd say this point was a HUGE red flag.
On Monday 07 September 2009, Jon A. Cruz wrote:
> On Sep 7, 2009, at 10:11 AM, Marco Martin wrote:
> > At the moment, (should make it more clear in the spec) is ARGB and
> > is not
> > designed to be network transparent, so the endian should be the same
> > of the
> > machine for both the client an
On Monday 07 September 2009, Aurélien Gâteau wrote:
> Marco Martin wrote:
> > On Monday 07 September 2009, Aurélien Gâteau wrote:
> >> Hi,
> >>
> >> I am probably a bit late at this, but thought I would ask anyway.
> >>
> >> Why did you choose the term "KNotificationItem"? I am afraid this is
> >>
Marco Martin wrote:
> On Monday 07 September 2009, Aurélien Gâteau wrote:
>> Hi,
>>
>> I am probably a bit late at this, but thought I would ask anyway.
>>
>> Why did you choose the term "KNotificationItem"? I am afraid this is
>> going to cause confusion with the existing notification systems.
>
On Monday 07 September 2009, Aurélien Gâteau wrote:
> Hi,
>
> I am probably a bit late at this, but thought I would ask anyway.
>
> Why did you choose the term "KNotificationItem"? I am afraid this is
> going to cause confusion with the existing notification systems.
the choice of the name has bee
Hi,
I am probably a bit late at this, but thought I would ask anyway.
Why did you choose the term "KNotificationItem"? I am afraid this is
going to cause confusion with the existing notification systems.
A name like KSystemTrayItem would avoid such confusions. I know it is
probably not very ap
On September 5, 2009, Tom Albers wrote:
> (as rsibreak is a systray app, without mainwindow, users can get confused
> if rsibreak is running or not, so if they launch it a second time a popup
> is shown with a screenie of the tray and an indication which icon is
> rsibreak. But if the trayicon i
Op Saturday 05 September 2009 01:34 schreef u:
> questions and comments are more than welcome
In that case ;-)
Can I detect if a systray icon is hidden or not? I would need that to fix:
https://bugs.kde.org/show_bug.cgi?id=203654
(as rsibreak is a systray app, without mainwindow, users can get c
Hello everyone,
In the past few months in KDE we worked on a new way to represent the
systemtray icons to overcome the following limitations:
-lack of communication between the systemtray area and the items, that
mean we don't know about their status, their importance of if they are
being used or n
Hello everyone,
In the past few months in KDE we worked on a new way to represent the
systemtray icons to overcome the following limitations:
-lack of communication between the systemtray area and the items, that
mean we don't know about their status, their importance of if they are
being used or n
14 matches
Mail list logo
