ubuntu-sdk-bugs team mailing list archive

[Kyle Fazzari <kyle@xxxxxxxxxxxxx>]

Public bug reported:

When using regular-old QtCreator, hitting the "play" button in the
Application Output pane runs the application and toggles the button to a
"stop" button. Hitting the "stop" button then kills the application.
Also, if one closes the application manually, QtCreator notices and
toggles the "stop" button back to "play."

When developing scopes in the Ubuntu SDK, however, the usage of the stop
button changes. When deploying to a device (either physical or
emulated), the "play" button installs and runs the scope, but the "stop"
button only uninstalls the scope-- it doesn't kill it. Also, if one were
to exit the scope manually, the SDK doesn't notice and the "stop" button
remains available, which gives the impression that the scope is still
"running."

Summary
---------------

Expected behavior: Be consistent with other usages of QtCeator.

1) Click "play" button in Application Output pane -> Deploy application to device and run application, toggle button to "stop"
2) Click "stop" button in Application Output pane -> Remove application from device and kill application, toggle button to "play"
3) Manually stop application on device -> SDK should notice, and remove application from device and toggle button to "play"

Actual behavior:

1) Click "play" button in Application Output pan -> Deploy application to device and run application, toggle button to "stop"
2) Click "stop" button in Application Output pane -> Remove application but it's still running, even though button has been toggled back to "play"
3) Manually stop application on device -> SDK does not notice, and the button is still a "stop" button, which gives the impression the application is still running.

** Affects: qtcreator-plugin-ubuntu (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtcreator-plugin-ubuntu in
Ubuntu.
https://bugs.launchpad.net/bugs/1450769

Title:
  SDK makes stop button usage inconsistent

Status in qtcreator-plugin-ubuntu package in Ubuntu:
  New

Bug description:
  When using regular-old QtCreator, hitting the "play" button in the
  Application Output pane runs the application and toggles the button to
  a "stop" button. Hitting the "stop" button then kills the application.
  Also, if one closes the application manually, QtCreator notices and
  toggles the "stop" button back to "play."

  When developing scopes in the Ubuntu SDK, however, the usage of the
  stop button changes. When deploying to a device (either physical or
  emulated), the "play" button installs and runs the scope, but the
  "stop" button only uninstalls the scope-- it doesn't kill it. Also, if
  one were to exit the scope manually, the SDK doesn't notice and the
  "stop" button remains available, which gives the impression that the
  scope is still "running."

  Summary
  ---------------

  Expected behavior: Be consistent with other usages of QtCeator.

  1) Click "play" button in Application Output pane -> Deploy application to device and run application, toggle button to "stop"
  2) Click "stop" button in Application Output pane -> Remove application from device and kill application, toggle button to "play"
  3) Manually stop application on device -> SDK should notice, and remove application from device and toggle button to "play"

  Actual behavior:

  1) Click "play" button in Application Output pan -> Deploy application to device and run application, toggle button to "stop"
  2) Click "stop" button in Application Output pane -> Remove application but it's still running, even though button has been toggled back to "play"
  3) Manually stop application on device -> SDK does not notice, and the button is still a "stop" button, which gives the impression the application is still running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1450769/+subscriptions