| 2011-01-26 17:45:06 |
Marco Trevisan (Treviño) |
bug |
|
|
added bug |
| 2011-01-26 17:45:06 |
Marco Trevisan (Treviño) |
attachment added |
|
libindicator-scroll-entry-signal-support.patch https://bugs.launchpad.net/bugs/708180/+attachment/1808663/+files/libindicator-scroll-entry-signal-support.patch |
|
| 2011-01-26 17:45:44 |
Marco Trevisan (Treviño) |
attachment added |
|
indicator-application-catch-entry-scroll-signal-and-emit-to-indicator.patch https://bugs.launchpad.net/ayatana-ubuntu/+bug/708180/+attachment/1808672/+files/indicator-application-catch-entry-scroll-signal-and-emit-to-indicator.patch |
|
| 2011-01-26 17:46:05 |
Marco Trevisan (Treviño) |
attachment added |
|
libappindicator-support-for-scroll-event-signal-sent-on-scroll-event-over-indicator.patch https://bugs.launchpad.net/ayatana-ubuntu/+bug/708180/+attachment/1808673/+files/libappindicator-support-for-scroll-event-signal-sent-on-scroll-event-over-indicator.patch |
|
| 2011-01-26 17:46:34 |
Marco Trevisan (Treviño) |
attachment added |
|
indicator-applet-send-scroll-entry-signal-on-scroll-over-indicator.patch https://bugs.launchpad.net/ayatana-ubuntu/+bug/708180/+attachment/1808680/+files/indicator-applet-send-scroll-entry-signal-on-scroll-over-indicator.patch |
|
| 2011-01-26 17:46:57 |
Marco Trevisan (Treviño) |
attachment added |
|
unity-send-scroll-entry-signal-on-scroll-over-indicator.patch https://bugs.launchpad.net/ayatana-ubuntu/+bug/708180/+attachment/1808681/+files/unity-send-scroll-entry-signal-on-scroll-over-indicator.patch |
|
| 2011-01-26 21:04:30 |
Marco Trevisan (Treviño) |
bug task added |
|
libindicator |
|
| 2011-01-26 21:05:19 |
Marco Trevisan (Treviño) |
bug task added |
|
libappindicator |
|
| 2011-01-26 21:05:49 |
Marco Trevisan (Treviño) |
bug task added |
|
unity |
|
| 2011-01-26 21:06:19 |
Marco Trevisan (Treviño) |
bug task added |
|
indicator-applet |
|
| 2011-01-26 21:07:17 |
Marco Trevisan (Treviño) |
bug task added |
|
indicator-application |
|
| 2011-01-26 21:08:32 |
Marco Trevisan (Treviño) |
indicator-application: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-26 22:49:26 |
Marco Trevisan (Treviño) |
description |
Actually the only indicator which supports scrolling over it, is the indicator-sound. However libindicate support that signal for every indicator, but not for indicators (like indicator-application) which contain many other child entries.
So, in the current situation it's impossible to create an appindicator which get a signal on scroll-event over its icon (for example for making an indicator that controls the brightness of the screen...).
This is an implementation that allows that; basically:
* libindicator support the new "scroll-entry" signal (which get called using the
target entry as parameter too) I think that maybe we could simply rewrite the
"scroll" signal, but I kept it there for compatibility reasons; however,
actually just the indicator-sound should be fixed in case of switch...
* indicator-application now is listening for that signal ("scroll-entry"),
registering a call-back function. When it gets called, it finds the scrolled
application and informs (via dbus) indicator-application-service that a scroll
event has been registered for that application. Now the service (that is
connected to every indicatorapp running) sends (via dbus, again) to the
correct application the scroll-event informations.
* libappindicator now when it gets a dbus call from indicator-application about
the incoming scroll event, sends a "scroll-event" signal to the appindicator
application.
* unity (panel-service, in fact): now sends also a "scroll-entry" signal when
an indicator is scrolled, with the target entry as parameter.
* indicator-applet (like unity): now sends also a "scroll-entry" signal when
an indicator is scrolled, with the target entry as parameter.
As results, you can do
AppIndicator *indicator;
...
g_signal_connect (indicator, "scroll-event", G_CALLBACK (scroll_event), NULL);
To get the scroll event
Imho this is can be needed, and also should be an architecture to be used for other signals ("over-indicator" signal for example... or others related to the indicator, more than its content). |
Actually the only indicator which supports scrolling over it, is the indicator-sound. However libindicate support that signal for every indicator, but not for indicators (like indicator-application) which contain many other child entries.
So, in the current situation it's impossible to create an appindicator which get a signal on scroll-event over its icon (for example for making an indicator that controls the brightness of the screen...).
This is an implementation that allows that; basically:
* libindicator support the new "scroll-entry" signal (which get called
using the target entry as parameter too) I think that maybe we could
simply rewrite the "scroll" signal, but I kept it there for
compatibility reasons; however, actually just the indicator-sound
should be fixed in case of switch...
* indicator-application now is listening for that signal
("scroll-entry"), registering a call-back function. When it gets
called, it finds the scrolled application and informs (via dbus)
indicator-application-service that a scroll event has been
registered for that application. Now the service (that is connected
to every indicatorapp running) sends (via dbus, again) to the correct
application the scroll-event informations.
* libappindicator now when it gets a dbus call from
indicator-application about the incoming scroll event, sends a
"scroll-event" signal to the appindicator application.
* unity (panel-service, in fact): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
* indicator-applet (like unity): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
As results, you can do
AppIndicator *indicator;
...
g_signal_connect (indicator, "scroll-event", G_CALLBACK (scroll_event), NULL);
To get the scroll event
Imho this is can be needed, and also should be an architecture to be used for other signals ("over-indicator" signal for example... or others related to the indicator, more than its content).
|
|
| 2011-01-26 23:44:31 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/libindicator/scroll-event-support |
|
| 2011-01-26 23:44:45 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/indicator-application/scroll-event-support |
|
| 2011-01-26 23:44:59 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/libappindicator/scroll-event-support |
|
| 2011-01-26 23:45:14 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/indicator-applet/scroll-event-support |
|
| 2011-01-26 23:45:22 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/unity/scroll-event-support |
|
| 2011-01-28 12:35:07 |
Mirco Müller |
unity: status |
New |
Incomplete |
|
| 2011-01-28 12:35:30 |
Mirco Müller |
unity: status |
Incomplete |
New |
|
| 2011-01-28 12:43:44 |
Mirco Müller |
unity: status |
New |
Confirmed |
|
| 2011-01-28 12:43:47 |
Mirco Müller |
unity: importance |
Undecided |
Low |
|
| 2011-01-28 14:28:27 |
Ted Gould |
libindicator: status |
New |
Fix Released |
|
| 2011-01-28 14:28:44 |
Ted Gould |
indicator-applet: status |
New |
Fix Released |
|
| 2011-01-29 01:01:49 |
Marco Trevisan (Treviño) |
indicator-application: status |
New |
In Progress |
|
| 2011-01-29 02:40:31 |
Marco Trevisan (Treviño) |
indicator-application: status |
In Progress |
Fix Committed |
|
| 2011-01-30 12:17:57 |
Marco Trevisan (Treviño) |
libappindicator: status |
New |
Fix Committed |
|
| 2011-01-30 12:17:57 |
Marco Trevisan (Treviño) |
libappindicator: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-30 12:18:40 |
Marco Trevisan (Treviño) |
unity: status |
Confirmed |
Fix Committed |
|
| 2011-01-30 12:18:40 |
Marco Trevisan (Treviño) |
unity: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-30 12:19:19 |
Marco Trevisan (Treviño) |
ayatana-ubuntu: status |
New |
In Progress |
|
| 2011-01-30 12:19:38 |
Marco Trevisan (Treviño) |
indicator-applet: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-30 12:19:44 |
Marco Trevisan (Treviño) |
libindicator: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-30 12:19:52 |
Marco Trevisan (Treviño) |
ayatana-ubuntu: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-01-31 21:32:56 |
Marco Trevisan (Treviño) |
unity: status |
Fix Committed |
Fix Released |
|
| 2011-02-03 17:28:35 |
Marco Trevisan (Treviño) |
indicator-application: status |
Fix Committed |
Fix Released |
|
| 2011-02-04 03:48:47 |
Marco Trevisan (Treviño) |
libappindicator: status |
Fix Committed |
Fix Released |
|
| 2011-02-04 03:49:41 |
Marco Trevisan (Treviño) |
ayatana-ubuntu: status |
In Progress |
Fix Released |
|
| 2011-07-01 15:21:42 |
Marco Trevisan (Treviño) |
branch linked |
|
lp:~3v1n0/unity-2d/scroll-event-support |
|
| 2011-07-01 15:22:08 |
Marco Trevisan (Treviño) |
bug task added |
|
unity-2d |
|
| 2011-07-01 15:22:27 |
Marco Trevisan (Treviño) |
unity-2d: assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-07-01 15:22:30 |
Marco Trevisan (Treviño) |
unity-2d: status |
New |
Fix Committed |
|
| 2011-07-01 15:24:33 |
Marco Trevisan (Treviño) |
description |
Actually the only indicator which supports scrolling over it, is the indicator-sound. However libindicate support that signal for every indicator, but not for indicators (like indicator-application) which contain many other child entries.
So, in the current situation it's impossible to create an appindicator which get a signal on scroll-event over its icon (for example for making an indicator that controls the brightness of the screen...).
This is an implementation that allows that; basically:
* libindicator support the new "scroll-entry" signal (which get called
using the target entry as parameter too) I think that maybe we could
simply rewrite the "scroll" signal, but I kept it there for
compatibility reasons; however, actually just the indicator-sound
should be fixed in case of switch...
* indicator-application now is listening for that signal
("scroll-entry"), registering a call-back function. When it gets
called, it finds the scrolled application and informs (via dbus)
indicator-application-service that a scroll event has been
registered for that application. Now the service (that is connected
to every indicatorapp running) sends (via dbus, again) to the correct
application the scroll-event informations.
* libappindicator now when it gets a dbus call from
indicator-application about the incoming scroll event, sends a
"scroll-event" signal to the appindicator application.
* unity (panel-service, in fact): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
* indicator-applet (like unity): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
As results, you can do
AppIndicator *indicator;
...
g_signal_connect (indicator, "scroll-event", G_CALLBACK (scroll_event), NULL);
To get the scroll event
Imho this is can be needed, and also should be an architecture to be used for other signals ("over-indicator" signal for example... or others related to the indicator, more than its content).
|
Actually the only indicator which supports scrolling over it, is the indicator-sound. However libindicate support that signal for every indicator, but not for indicators (like indicator-application) which contain many other child entries.
So, in the current situation it's impossible to create an appindicator which get a signal on scroll-event over its icon (for example for making an indicator that controls the brightness of the screen...).
This is an implementation that allows that; basically:
* libindicator support the new "scroll-entry" signal (which get called
using the target entry as parameter too) I think that maybe we could
simply rewrite the "scroll" signal, but I kept it there for
compatibility reasons; however, actually just the indicator-sound
should be fixed in case of switch...
* indicator-application now is listening for that signal
("scroll-entry"), registering a call-back function. When it gets
called, it finds the scrolled application and informs (via dbus)
indicator-application-service that a scroll event has been
registered for that application. Now the service (that is connected
to every indicatorapp running) sends (via dbus, again) to the correct
application the scroll-event informations.
* libappindicator now when it gets a dbus call from
indicator-application about the incoming scroll event, sends a
"scroll-event" signal to the appindicator application.
* unity (panel-service, in fact): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
* unity-2d (unity-2d-panel in fact): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
* indicator-applet (like unity): now sends also a "scroll-entry"
signal when an indicator is scrolled, with the target entry as
parameter.
As results, you can do
AppIndicator *indicator;
...
g_signal_connect (indicator, "scroll-event", G_CALLBACK (scroll_event), NULL);
To get the scroll event
Imho this is can be needed, and also should be an architecture to be used for other signals ("over-indicator" signal for example... or others related to the indicator, more than its content). |
|
| 2011-07-20 18:20:44 |
Didier Roche-Tolomelli |
unity-2d (Ubuntu): status |
New |
Fix Committed |
|
| 2011-07-20 21:45:04 |
Marco Trevisan (Treviño) |
unity-2d (Ubuntu): assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-07-20 21:45:22 |
Marco Trevisan (Treviño) |
bug task added |
|
unity (Ubuntu) |
|
| 2011-07-20 21:45:34 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
New |
Fix Committed |
|
| 2011-07-20 21:45:37 |
Marco Trevisan (Treviño) |
unity (Ubuntu): assignee |
|
Treviño (Marco Trevisan) (3v1n0) |
|
| 2011-07-20 21:45:53 |
Marco Trevisan (Treviño) |
unity (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-07-21 17:31:37 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2011-08-12 16:07:22 |
Florian Boucault |
unity-2d (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2011-08-12 16:07:29 |
Florian Boucault |
unity-2d: status |
Fix Committed |
Fix Released |
|
