Ticket #7642 (new defect)

Opened 6 years ago

Last modified 6 years ago

Switching to mesh/neighborhood view should hide control panel.

Reported by: cscott Owned by: marco
Priority: normal Milestone: 9.1.0-cancelled
Component: sugar Version: Development build as of this date
Keywords: Cc:
Action Needed: code Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Open the sugar control panel. Now press the 'mesh' key. Behind the control panel, the view changes, but we can barely see it because our view is completely obstructed by the sugar control panel.

When we switch views, we should show/hide the control panel. The window manager could do this automatically for us if we set an appropriate 'transient_for' property (and this works for switching to activities), but the mesh, neighborhood, and home views all share a single top-level window, so this doesn't work as it ought.

Change History

Changed 6 years ago by marco

  • next_action changed from never set to code
  • milestone changed from 8.2.0 (was Update.2) to 9.1.0

Doesn't sound critical for 9.1 to me, happy to consider different opinions though.

Changed 6 years ago by cscott

From discussion with eben, here's the use case: "well, for software updates, the typical behavior is that you open the updates control panel, click refresh and it tells you you're not connected to the network. so you press the mesh key --- and can't see anything."

This may be a bit of a special case, but it violates the user's expectations of how things will work. In particular, pressing the 'activity' key switches to an activity as you would expect; it's only the friends and mesh views which are abnormal.

Changed 6 years ago by cscott

See also #7882, which proposes treating the control panel as an activity, which would also address this issue.

Changed 6 years ago by mikus

In my case, I had clicked on 'Software update' and it was taking minutes. I got tired of looking at the Control Panel, and wanted to see (in Neighborhood View) what other users were connected.

Note: See TracTickets for help on using tickets.