Launcher - The Nautilus and USB drive icons in the Launcher should be valid drop targets for all types of files and folders

[John Lea]

The Nautilus and USB drive icons in the Launcher should be valid drop targets for all types of files and folders

When a user starts dragging a file or folder, Launcher icons that are valid drop targets are highlighted by means of all the other Launcher icons dimming. However HOME and USB drive launcher icons do not currently remain illuminated even though they should be valid drop targets for all files and folders.

Desired solution:
- HOME and USB drive icons (and any other icons that represent storage devices) in the Launcher should remain illuminated when a user starts performing a file or folder drag action.

- The exception to the above statement is when the drag originates from a Nautilus window. In this case the originating Launcher icon should not be highlighted, e.g. when dragging a file from a USB drive, the USB drive the file is being dragged from should not illuminate.

- Dropping a file or folder on to a HOME and USB drive icon should copy that file or folder to the directory that is currently in focus. For example, if no HOME window is currently open, dropping a file on to the HOME icon should copy that file into the /home/[User]/ directory. However if Nautilus has been opened by clicking on the HOME Launcher icon and is currently displaying the /Pictures/ directory, dropping the file on to the HOME launcher icon should copy the file to the /Pictures/ directory.

- If multiple Nautilus windows have been opened by clicking on a single Launcher entry (e.g. by middle clicking several times on the HOME icon), droping a file on to the Launcher entry (e.g. HOME icon) copies the file to the most recently focused of these windows.

- In line with the standard Launcher drag and drop behavour, if there multiple windows have been opened from a single storage icon (e.g. HOME), holding the file over the Launcher icon should trigger a spread. This enables the user to then choose which window they would like to copy the file into.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.1.1

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity - 7.1.2+13.10.20131011-0ubuntu1

---------------
unity (7.1.2+13.10.20131011-0ubuntu1) saucy; urgency=low

  [ Stephen M. Webb ]
  * bump upstream version to 7.1.2

  [ Brandon Schaefer ]
  * Remove the ibus workaround, as im-config has been updated to use
    'auto' as its default choice. This means ibus-daemon will start up
    correctly now.

  [ Andrea Azzarone ]
  * Fix rendering of italic text in StaticCairoText. (LP: #1190275)

  [ Marco Trevisan (Treviño) ]
  * Volume: remove FileManager instance, handle opened status in
    VolumeLauncherIcon. (LP: #1236468)
  * VolumeLauncherIcon: copy files to device on DnD Use filemanager to
    perform the copy action. If needed, delay the procedure until we
    don't have the volume mounted (using a magic utility function to
    share the code). (LP: #838731)
  * LauncherIcon: Add monitor parameter to GetTipPosition. (LP:
    #1236631)
  * AP, TestSpread: assertWindowIsNotScaled may fail when getting the
    Xid. (LP: #1236872)
  * ApplicationLauncherIcon: remove the icon when setting a null
    application. (LP: #1237161)
  * SourceManager: add RemoveAll public method.
  * ApplicationLauncherIcon: don't unset the app if the icon has been
    already removed In this case the app is unset when removed, doing it
    twice causes the app->seen flag to be reset and this breaks the
    assumtions of the LauncherController, making it to recreate a new
    app for the same BamfApplication. (LP: #1237182)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 3565
 -- Ubuntu daily release <email address hidden> Fri, 11 Oct 2013 06:17:18 +0000