need a transition state for indicators reflecting laggy backends

any changes to the icons displayed require modifications on the indicator-network-service.

system-settings is not affected.

oh, ignore comment #2. if we indeed do modify the switch items then it affects system-settings as well.

iiuc, what design wants is the user toggle for airplane mode to stand alone as a reflection of user intent.
And the icons in the top bar to be reflective of the networks connection state.

e.g.
user toggles airplane mode off/on
- the toggle itself does not change ever until the user changes it
- the icon shows the transition (...) until it disconnects (airplane) or connects (radio bars)
- and in the case of user turning airplane mode off & fails to reconnect, the the radio bars would just show empty after some time is the search is given up

Now, there is a question, do we want to prevent the user from interacting with the toggle during the transition time ? as i realize this may be easier to deal with technically (forcing a response to the request, and not allowing the client request state to change)

From a dupe:

Ben says: When the user switches to airplane mode, if the mode change fails, pop up a system dialog that says "Unable to switch to Airplane mode. Please try again." [OK] and the switch reverts to airplane off state.

Description updated with details of the desired resolution. Design solution signed off by John and Ben.

We're probably going to need a more complex mechanism for indicator related actions than what we have now if we want popups and such things.
At the moment we are using dbus modelled gactions; as far as i know, there is no feedback available for this as to indicating success/failure other than "not changing the setting".

Status changed to 'Confirmed' because the bug affects multiple users.

Need design input and some rearch here, ww05-2015 would be the earliest this could happen.

The fix for https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1393488 improves the visual behaviour but the recommendation is that this still gets redesigned to provide a more robust solution

setting to new for the canonical system image product team.
I would propose we either close this "critical" bug out & spawn a new one.
Or downgrade the criticality "high".
(personally i'd vote for the downgrade to keep continuity in the bug)
We've delivered some measure of change to make this better.

But everyone is in agreement that we need to take a closer look to redesign this frontend/backend flow, which will take longer than ww03.

lower priority based on comments

May move out further for final fixes

As nick stated in comment #7 we need more detailed API than the current GAction based one. I'm thinking something along the line of having QML API's that return a progress object when you call methods such as "enableFlightMode". The caller would then use the object to track the status of the operation.

Once we do have the ability to track the progress of an Operation in the UI level we can either "disable" the switches for the duration of the ongoing operation or animate them with a "progress spinner" or something.

Hm, i didn't see the new description before I posted. Based on the new one from John, it doesn't look like we need to change the API if we don't need to track the transition.

The current method we use in Unity8 should suffice with a little tweaking. Currently we only wait 1.5 seconds for the server state to "re-assert" itself, which is why the switch "flips out" a bit if it takes longer.
Increasing this to 30 seconds, adding a "currently in transition" animation and buffering other changes until the state change is confirmed or 30 seconds is up should suffice.

And while indicator-network waits for the flight mode change request to be applied, it can change to the network-idle.svg icon.

Alternatively, instead of buffering the interactions with the Switch, you could disable the Switch (grey it out) while the operation is in progress

Since we don't have a clear idea for fixing this yet, I'd say this should be dropped off the RTM list.

track on later milestone as this experience needs a solution

The upcoming Qt port for the indicator disables the GActions for the wifi and flight mode toggles for the duration of the transition.

There is currently no way for the unity8 side to know if the transition is still going on and whether it succeeded or failed, so I think the fix for this firmly stands in the court of the indicator.

This bug was fixed in the package indicator-network - 0.5.1+15.04.20150401~rtm-0ubuntu1

---------------
indicator-network (0.5.1+15.04.20150401~rtm-0ubuntu1) 14.09; urgency=medium

  [ Pete Woods ]
  * Port all dbus interactions to QDBus (LP: #1390136, #1427064,
    #1245951)
 -- CI Train Bot <email address hidden> Wed, 01 Apr 2015 15:31:25 +0000

Fixed in silo ubuntu/landing-006 today for vivid. At least, the checkbox stays in one state and won't respond or change until the transition is complete, which seems acceptable.

This bug was fixed in the package indicator-network - 0.5.1+15.04.20150401.2-0ubuntu1

---------------
indicator-network (0.5.1+15.04.20150401.2-0ubuntu1) vivid; urgency=medium

  [ Marcus Tomlinson ]
  * Add integration tests for indicator
  * Port all D-Bus interactions over to QDBus (LP: #1390136, #1427064,
    #1245951)

  [ Pete Woods ]
  * Add integration tests for indicator
  * Port all D-Bus interactions over to QDBus (LP: #1390136, #1427064,
    #1245951)
 -- CI Train Bot <email address hidden> Wed, 01 Apr 2015 15:31:55 +0000

This bug was fixed in the package unity8 - 8.02+15.04.20150409.1-0ubuntu1

---------------
unity8 (8.02+15.04.20150409.1-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Focus the shutdown dialog (LP: #1417991)
  * Make url-dispatching scope activation when the dash is not on the
    main scopes (LP: #1364306)
  * We use autopilot3 now

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk. added: po/or.po

  [ Daniel d'Andrada ]
  * Make tst_PreviewListView and tst_GenericScopeView work in out-of-
    source builds
  * MouseArea that shows the indicators panel should cover the
    indicators bar only (LP: #1439318)
  * Surface gets active focus also with mouse clicks

  [ Josh Arenson ]
  * Add a mode option to unity8 for selecting greeter mode in the future
  * Remove PkgConfig include from Launcher plugin to fix cross-compile
    (LP: #1437702)

  [ Leo Arias ]
  * Fixed the check for string in the lock screen test. (LP: #1434518)

  [ Michael Terry ]
  * Make sure the edge tutorial is destroyed when we receive a call
    during the wizard. (LP: #1436349)
  * Skip parts of the edge tutorial that require a touch device (like
    spread and bottom edge). (LP: #1434712)

  [ Michael Zanetti ]
  * Don't hide stages just because they're empty (LP: #1439615)
  * [Launcher] fix bug where an item would disappear even though the app
    is running (LP: #1438172)

  [ Nick Dedekind ]
  * Fixed autopilot test failures related to udev input failure for
    power button.
  * Made improvements for laggy indicator backends (lp#1390136). (LP:
    #1390136)

  [ Pete Woods ]
  * GPS only goes active when the Dash is in the foreground (LP:
    #1434379)

  [ handsome_feng<email address hidden> ]
  * Modified the wrong time format in ScreenGrabber (LP: #1436006)
 -- CI Train Bot <email address hidden> Thu, 09 Apr 2015 14:01:11 +0000

This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150430.1-0ubuntu1

---------------
ubuntu-system-settings (0.3+15.04.20150430.1-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk.

  [ Ken VanDine ]
  * Include supported frameworks and arch when checking for updates (LP:
    #1449582)

 -- CI Train Bot <email address hidden> Thu, 30 Apr 2015 19:38:05 +0000