Nux

BaseWindow should notify change on the visible state

Bug #702702 reported by Alejandro Piñeiro on 2011-01-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
Fix Released
Undecided
Jay Taoko
Unity
Fix Released
Undecided
Unassigned
nux (Ubuntu)
Undecided
Unassigned
unity (Ubuntu)
Undecided
Unassigned

Bug Description

This bug is related to bug 702700.

BaseWindow has the state isVisible, but it would be required to have a signal to notify this change.

In the same way, it would be required to be able to connect to that signal without knowing the BaseWindow instance before connecting to this instance.

The use case of this feature is know if any BaseWindow has become visible, so we could get the specific instance and do thing with it.

I already talked about it with Jay Taoko via email and personally, and seems feasible. Just creating the bug in order to track this feature, and know when we could start to work on bug 702700

tags: added: a11y
Jay Taoko (jaytaoko) on 2011-01-18
Changed in nux:
status: New → In Progress
assignee: nobody → Jay Taoko (jaytaoko)
Didier Roche (didrocks) on 2011-02-21
Changed in unity:
status: New → In Progress
Changed in nux (Ubuntu):
status: New → In Progress
Alejandro Piñeiro (apinheiro) wrote :

This bug was solved some time ago, I will copy here a private mail from Jay dated of 27 January:

"In Nux/WindowCompositor.cpp/.h I added the following signals:
    sigc::signal<void, BaseWindow* > sigVisibleViewWindow
    sigc::signal<void, BaseWindow* > sigHiddenViewWindow

Both signals are emitted when a BaseWindow becomes visible or
hidden. You probably noticed that signal name carry the name
"ViewWindow". That is because I am in the processes of rename
BaseWindow to something else (possibly ViewWindow).

You connect to sigVisibleViewWindow and sigHiddenViewWindow through
the global WindowCompositor class (GetWindowCompositor ()).

BaseWindows themselves emit their own signal: sigVisible and
sigHidden. You can connect to these signals if you have access to a
BaseWindow object."

So closing the bug on the first two states, not sure how it works in the last one (packaging)

Changed in nux:
status: In Progress → Fix Committed
Changed in unity:
status: In Progress → Fix Committed
Alejandro Piñeiro (apinheiro) wrote :

BTW, I still have pending to use this stuff to solve bug 702700, but in theory those signals added would be enough

Didier Roche (didrocks) on 2011-02-24
Changed in unity:
milestone: none → 3.4.6
Didier Roche (didrocks) on 2011-02-24
Changed in nux (Ubuntu):
status: In Progress → Fix Committed
Didier Roche (didrocks) on 2011-02-24
Changed in nux:
status: Fix Committed → Fix Released
Changed in unity:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nux - 0.9.28-0ubuntu1

---------------
nux (0.9.28-0ubuntu1) natty; urgency=low

  * New upstream release:
    - BaseWindow should notify change on the visible state (LP: #702702)
  * Cherry-picked:
    - Unity FTBFS on armel due to Nux (LP: #721118)
  * debian/rules:
    - bump shlib
 -- Didier Roche <email address hidden> Thu, 24 Feb 2011 20:16:04 +0100

Changed in nux (Ubuntu):
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers