Bug 702938 - No emblems tab in nautilus
Summary: No emblems tab in nautilus
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 15
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-08 14:10 UTC by Daniel Belton
Modified: 2015-03-03 23:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-09 13:26:52 UTC
Type: ---


Attachments (Terms of Use)

Description Daniel Belton 2011-05-08 14:10:40 UTC
Description of problem: No tab in nautilus to assign an emblem to a file


Version-Release number of selected component (if applicable): nautilus 3.0.1.1-1.fc15


How reproducible: Open up properties for a file in nautilus, There should be a tab to assign an emblem to the file. It's not there.


Steps to Reproduce:
1.
2.
3.
  
Actual results: Can't set an emblem for a file.


Expected results: having an emblem tab to set an emblem for the file


Additional info:

Comment 1 Cosimo Cecchi 2011-05-09 13:26:52 UTC
This was intentionally removed upstream during the last development cycle, see http://mail.gnome.org/archives/nautilus-list/2010-July/msg00023.html

Comment 2 Daniel Belton 2011-05-10 12:39:04 UTC
this is getting to be a trend. 

Removing useful things and adding totally worthless crap. :( 

So, is there any way to set an emblem for a file? I know emblems are still supported in nautilus because the some of the system files have them set and I can see them.

Comment 3 Cosimo Cecchi 2011-05-11 13:55:40 UTC
(In reply to comment #2)

> So, is there any way to set an emblem for a file? I know emblems are still
> supported in nautilus because the some of the system files have them set and I
> can see them.

Not really; extensions (e.g. the Dropbox extension does) can add emblems programmatically using the libnautilus-extension API though.


Note You need to log in before you can comment on or make changes to this bug.