Windows 8 and 8.1 has only one option to change your colors. All colors in your template are calculated from this one color! This program is developed to bring a bit. If the item is a separator, it is left in place and is otherwise ignored. If it's an irrelevant command, it's deleted. These include Create Shortcut, Cut. And Copy, which don't serve a useful purpose unless you're operating directly on a desktop icon. If an item is a valid command, I call the SetMenuItemInfo() AP1 function to change.

Basic format of the file Desktop entry files should have the.desktop extension, except for files of Type Directory which should have the.directory extension. Determining file type on basis of extension makes determining the file type very easy and quick. When no file extension is present, the desktop system should fall back to recognition via 'magic detection'.

For applications, the part of the name of the desktop file (before the.desktop) should follow the 'reverse DNS' convention, e.g. The name should be a valid D-Bus well-known bus name. The valid characters (aside '.' ) are [A-Z][a-z][0-9] along with dash (' -') and underscore (' _').

Components may not begin with a digit. Desktop entry files are encoded in UTF-8. A file is interpreted as a series of lines that are separated by linefeed characters. Case is significant everywhere in the file. Compliant implementations MUST not remove any fields from the file, even if they don't support them.

Such fields must be maintained in a list somewhere, and if the file is 'rewritten', they will be included. This ensures that any desktop-specific extensions will be preserved even if another system accesses and changes the file. • Values of type string may contain all ASCII characters except for control characters. Sauer 1913 Serial Numbers here. • Values of type localestring are user displayable, and are encoded in UTF-8. • Values of type boolean must either be the string true or false.

• Values of type numeric must be a valid floating point number as recognized by the%f specifier for scanf in the C locale. The escape sequences s, n, t, r, and are supported for values of type string and localestring, meaning ASCII space, newline, tab, carriage return, and backslash, respectively. Some keys can have multiple values. In such a case, the value of the key is specified as a plural: for example, string(s). The multiple values should be separated by a semicolon and the value of the key may be optionally terminated by a semicolon. Trailing empty strings must always be terminated with a semicolon. Semicolons in these values need to be escaped using.

Localized values for keys Keys with type localestring may be postfixed by [ LOCALE], where LOCALE is the locale type of the entry. LOCALE must be of the form lang_ COUNTRY. ENCODING@ MODIFIER, where _ COUNTRY,. ENCODING, and @ MODIFIER may be omitted. If a postfixed key occurs, the same key must be also present without the postfix.

When reading in the desktop entry file, the value of the key is selected by matching the current POSIX locale for the LC_MESSAGES category against the LOCALE postfixes of all occurrences of the key, with the. ENCODING part stripped.

The matching is done as follows. If LC_MESSAGES is of the form lang_ COUNTRY. ENCODING@ MODIFIER, then it will match a key of the form lang_ COUNTRY@ MODIFIER. If such a key does not exist, it will attempt to match lang_ COUNTRY followed by lang@ MODIFIER. Then, a match against lang by itself will be attempted. Finally, if no matching key is found the required key without a locale specified is used.

The encoding from the LC_MESSAGES value is ignored when matching. If LC_MESSAGES does not have a MODIFIER field, then no key with a modifier will be matched. Similarly, if LC_MESSAGES does not have a COUNTRY field, then no key with a country specified will be matched. If LC_MESSAGES just has a lang field, then it will do a straight match to a key with a similar value. The following table lists possible matches of various LC_MESSAGES values in the order in which they are matched. Note that the ENCODING field isn't shown. Recognized desktop entry keys Keys are either OPTIONAL or REQUIRED.

If a key is OPTIONAL it may or may not be present in the file. However, if it isn't, the implementation of the standard should not blow up, it must provide some sane defaults. Some keys only make sense in the context when another particular key is also present and set to a specific value. Those keys should not be used if the particular key is not present or not set to the specific value. For example, the Terminal key can only be used when the value of the Type key is Application. If a REQUIRED key is only valid in the context of another key set to a specific value, then it has to be present only if the other key is set to the specific value. For example, the URL key has to be present when and only when when the value of the Type key is Link.

Some example keys: Name[C], Comment[it]. Key Description Value Type REQ? Type Type This specification defines 3 types of desktop entries: Application (type 1), Link (type 2) and Directory (type 3). To allow the addition of new types in the future, implementations should ignore desktop entries with an unknown type. String YES Version Version of the Desktop Entry Specification that the desktop entry conforms with. Entries that confirm with this version of the specification should use 1.1. Note that the version field is not required to be present.

String NO 1-3 Name Specific name of the application, for example 'Mozilla'. Localestring YES 1-3 GenericName Generic name of the application, for example 'Web Browser'. Localestring NO 1-3 NoDisplay NoDisplay means 'this application exists, but don't display it in the menus'.

This can be useful to e.g. Associate this application with MIME types, so that it gets launched from a file manager (or other apps), without having a menu entry for it (there are tons of good reasons for this, including e.g. The netscape -remote, or kfmclient openURL kind of stuff).

Boolean NO 1-3 Comment Tooltip for the entry, for example 'View sites on the Internet'. The value should not be redundant with the values of Name and GenericName. Localestring NO 1-3 Icon Icon to display in file manager, menus, etc. If the name is an absolute path, the given file will be used. If the name is not an absolute path, the algorithm described in the will be used to locate the icon.

Localestring NO 1-3 Hidden Hidden should have been called Deleted. It means the user deleted (at his level) something that was present (at an upper level, e.g. In the system dirs). It's strictly equivalent to the.desktop file not existing at all, as far as that user is concerned. This can also be used to 'uninstall' existing files (e.g. Due to a renaming) - by letting make install install a file with Hidden=true in it.

Boolean NO 1-3 OnlyShowIn, NotShowIn A list of strings identifying the desktop environments that should display/not display a given desktop entry. By default, a desktop file should be shown, unless an OnlyShowIn key is present, in which case, the default is for the file not to be shown. If $XDG_CURRENT_DESKTOP is set then it contains a colon-separated list of strings. In order, each string is considered.

If a matching entry is found in OnlyShowIn then the desktop file is shown. If an entry is found in NotShowIn then the desktop file is not shown. If none of the strings match then the default action is taken (as above). $XDG_CURRENT_DESKTOP should have been set by the login manager, according to the value of the DesktopNames found in the session file. The entry in the session file has multiple values separated in the usual way: with a semicolon. The same desktop name may not appear in both OnlyShowIn and NotShowIn of a group. String(s) NO 1-3 DBusActivatable A boolean value specifying if D-Bus activation is supported for this application.

If this key is missing, the default value is false. If the value is true then implementations should ignore the Exec key and send a D-Bus message to launch the application. See for more information on how this works. Applications should still include Exec= lines in their desktop files for compatibility with implementations that do not understand the DBusActivatable key.

Boolean NO TryExec Path to an executable file on disk used to determine if the program is actually installed. If the path is not an absolute path, the file is looked up in the $PATH environment variable. If the file is not present or if it is not executable, the entry may be ignored (not be used in menus, for example). String NO 1 Exec Program to execute, possibly with arguments.

See the for details on how this key works. The Exec key is required if DBusActivatable is not set to true. Even if DBusActivatable is true, Exec should be specified for compatibility with implementations that do not understand DBusActivatable.

String NO 1 Path If entry is of type Application, the working directory to run the program in. String NO 1 Terminal Whether the program runs in a terminal window. Boolean NO 1 Actions Identifiers for application actions. This can be used to tell the application to make a specific action, different from the default behavior. The section describes how actions work. String(s) NO 1 MimeType The MIME type(s) supported by this application. String(s) NO 1 Categories Categories in which the entry should be shown in a menu (for possible values see the ).

String(s) NO 1 Implements A list of interfaces that this application implements. By default, a desktop file implements no interfaces. See for more information on how this works. String(s) NO Keywords A list of strings which may be used in addition to other metadata to describe this entry.

This can be useful e.g. To facilitate searching through entries. The values are not meant for display, and should not be redundant with the values of Name or GenericName. Localestring(s) NO 1 StartupNotify If true, it is KNOWN that the application will send a 'remove' message when started with the DESKTOP_STARTUP_ID environment variable set. If false, it is KNOWN that the application does not work with startup notification at all (does not shown any window, breaks even when using StartupWMClass, etc.).

If absent, a reasonable handling is up to implementations (assuming false, using StartupWMClass, etc.). (See the for more details).

Boolean NO 1 StartupWMClass If specified, it is known that the application will map at least one window with the given string as its WM class or WM name hint (see the for more details). String NO 1 URL If entry is Link type, the URL to access. String YES 2. The Exec key The Exec key must contain a command line. A command line consists of an executable program optionally followed by one or more arguments. The executable program can either be specified with its full path or with the name of the executable only. If no full path is provided the executable is looked up in the $PATH environment variable used by the desktop environment.

The name or path of the executable program may not contain the equal sign ('='). Arguments are separated by a space.

Arguments may be quoted in whole. If an argument contains a reserved character the argument must be quoted. The rules for quoting of arguments is also applicable to the executable name or path of the executable program as provided.

Quoting must be done by enclosing the argument between double quotes and escaping the double quote character, backtick character ('`'), dollar sign ('$') and backslash character (' ') by preceding it with an additional backslash character. Implementations must undo quoting before expanding field codes and before passing the argument to the executable program. Reserved characters are space (' '), tab, newline, double quote, single quote (''), backslash character (' '), greater-than sign ('>'), less-than sign ('. Code Description%f A single file name (including the path), even if multiple files are selected. The system reading the desktop entry should recognize that the program in question cannot handle multiple file arguments, and it should should probably spawn and execute multiple copies of a program for each selected file if the program is not able to handle additional file arguments. If files are not on the local file system (i.e.

Are on HTTP or FTP locations), the files will be copied to the local file system and%f will be expanded to point at the temporary file. Used for programs that do not understand the URL syntax.%F A list of files. Use for apps that can open several local files at once.

Each file is passed as a separate argument to the executable program.%u A single URL. Local files may either be passed as file: URLs or as file path.%U A list of URLs. Each URL is passed as a separate argument to the executable program.

Local files may either be passed as file: URLs or as file path.%d Deprecated.%D Deprecated.%n Deprecated.%N Deprecated.%i The Icon key of the desktop entry expanded as two arguments, first --icon and then the value of the Icon key. Should not expand to any arguments if the Icon key is empty or missing.%c The translated name of the application as listed in the appropriate Name key in the desktop entry.%k The location of the desktop file as either a URI (if for example gotten from the vfolder system) or a local filename or empty if no location is known.%v Deprecated.%m Deprecated. A command line may contain at most one%f,%u,%F or%U field code.

If the application should not open any file the%f,%u,%F and%U field codes must be removed from the command line and ignored. Field codes must not be used inside a quoted argument, the result of field code expansion inside a quoted argument is undefined. The%F and%U field codes may only be used as an argument on their own.

Interfaces The Implements key can be used to declare one or more interfaces that a desktop file implements. Each interface name must follow the rules used for D-Bus interface names, but other than that, they have no particular meaning. For instance, listing an interface here does not necessarily mean that this application implements that D-Bus interface or even that such a D-Bus interface exists.

It is entirely up to the entity who defined a particular interface to define what it means to implement it. Although it is entirely up to the designer of the interface to decide what a given interface name means, here are some recommended 'best practices'. Key Description Value Type REQ? Name Label that will be shown to the user. Since actions are always shown in the context of a specific application (that is, as a submenu of a launcher), this only needs to be unambiguous within one application and should not include the application name. Localestring YES Icon Icon to be shown togheter with the action. If the name is an absolute path, the given file will be used.

If the name is not an absolute path, the algorithm described in the will be used to locate the icon. Implementations may choose to ignore it. Download Free Games For Samsung Wave Y S5380d on this page.

Localestring NO Exec Program to execute for this action, possibly with arguments. See the for details on how this key works. The Exec key is required if DBusActivatable is not set to true in the main desktop entry group. Even if DBusActivatable is true, Exec should be specified for compatibility with implementations that do not understand DBusActivatable. Implementation notes Application actions should be supported by implementors. However, in case they are not supported, implementors can simply ignore the Actions key and the associated Desktop Action action groups, and keep using the Desktop Entry group: the primary way to describe and invoke the application is through the Name, Icon and Exec keys from the Desktop Entry group.

It is not expected that other desktop components showing application lists (software installers, for instance) will provide any user interface for these actions. Therefore applications must only include actions that make sense as general launchers. • Type=MimeType is deprecated as there is a new standard for this now, see the for more information. In consequence the Keys Patterns (various file name extensions associated with the MIME type) and DefaultApp (the default application associated with this MIME type) are also deprecated. • Using.kdelnk instead of.desktop as the file extension is deprecated.

• Using [KDE Desktop Entry] instead of [Desktop Entry] as header is deprecated. • The Encoding key is deprecated. It was used to specify whether keys of type localestring were encoded in UTF-8 or in the specified locale. Possible values are UTF-8 and Legacy-Mixed. See for more details. • Deprecated Exec field codes:%m (the mini-icon associated with the desktop entry, this should be expanded as two arguments, --miniicon and the content of the MiniIcon key, it can also be ignored by expanding it to no arguments),%v (the device as listed in the Dev key in the desktop file),%d (the directory of a file),%D (the directories of files),%n (the base name of a file) and%N (the base names of files). • Deprecated keys: MiniIcon (small icon for menus, etc.), TerminalOptions (if the program runs in a terminal, any options that should be passed to the terminal emulator before actually executing the program), Protocols, Extensions, BinaryPattern, MapNotify.

• The SwallowTitle and SwallowExec keys are deprecated. The SwallowTitle key is of type localestring and specifies the title of the window if is swallowed onto the panel. The SwallowExec key is of type string and specifies the program to exec if swallowed app is clicked.

• The SortOrder key is deprecated. It is of type string(s) and may be used to specify the order in which to display files. The defines another mechanism for defining the order of menu items. • The FilePattern key is deprecated.

The value is a list of regular expressions to match against for a file manager to determine if this entry's icon should be displayed. Usually simply the name of the main executable and friends. • Historically some booleans have been represented by the numeric entries 0 or 1. With this version of the standard they are now to be represented as a boolean string. However, if an implementation is reading a pre-1.0 desktop entry, it should interpret 0 and 1 as false and true, respectively.

• Historically lists have been comma separated. This is inconsistent with other lists which are separated by a semicolon. When reading a pre-1.0 desktop entry, comma separated lists should continue to be supported. D. The Legacy-Mixed Encoding (Deprecated) The Legacy-Mixed encoding corresponds to the traditional encoding of desktop files in older versions of the GNOME and KDE desktop files.

In this encoding, the encoding of each localestring key is determined by the locale tag for that key, if any, instead of being UTF-8. For keys without a locale tag, the value must contain only ASCII characters. If the file specifies an unsupported encoding, the implementation should either ignore the file, or, if the user has requested a direct operation on the file (such as opening it for editing), display an appropriate error indication to the user. In the absence of an Encoding key, the implementation may choose to autodetect the encoding of the file by using such factors as. Encoding The name given here is listed here is typically the canonical name for the encoding in the GNU C Library's iconv facility.

Encodings marked with (*) are not currently supported by the GNU C Library; for this reason, implementations may choose to ignore lines in desktop files that resolve to this encoding. Desktop files with these encodings are currently rare or non-existent. Aliases Other names for the encoding found in existing desktop files. Tags Language tags for which this is the default encoding. This table above covers all tags and encodings that are known to be currently in use. Implementors may choose to support encodings not in the above set. For tags without defaults listed in the above table, desktop file creators must specify the.

ENCODING part of the locale tag. Matching the. ENCODING part of the locale tag against a locale name or alias should be done by stripping all punctuation characters from both the tag and the name or alias, converting both name and alias to lowercase, and comparing the result.

This is necessary because, for example, Big5 is frequently found instead of BIG5 and georgianacademy instead of GEORGIAN-ACADEMY. Desktop files creators should, however, use the name as it appears in the 'Encoding' column above. E. Desktop File ID The desktop file ID is the identifier of an installed desktop entry file. To determine the ID of a desktop file, make its full path relative to the $XDG_DATA_DIRS component in which the desktop file is installed, remove the 'applications/' prefix, and turn '/' into '-'. For example /usr/share/applications/foo/bar.desktop has the desktop file ID foo-bar.desktop. If multiple files have the same desktop file ID, the first one in the $XDG_DATA_DIRS precedence order is used. For example, if $XDG_DATA_DIRS contains the default paths /usr/local/share:/usr/share, then /usr/local/share/applications/org.foo.bar.desktop and /usr/share/applications/org.foo.bar.desktop both have the same desktop file ID org.foo.bar.desktop, but only the first one will be used.

If both foo-bar.desktop and foo/bar.desktop exist, it is undefined which is selected. If the desktop file is not installed in an applications subdirectory of one of the $XDG_DATA_DIRS components, it does not have an ID.

Sounds like just the product for you! It's free for personal use. From their website: Fences is a one-of-a-kind program, allowing you to draw labeled shaded areas on your desktop, which become movable & resizable containers for your desktop icons. These groups can help bring organization and consistency to your computer's desktop, solving the 'constant mess' problem that has plagued the desktop since its inception. Fences also helps you finally appreciate the wallpaper you have hiding behind all that clutter. In addition to its organizing features, Fences offers a novel quick-hide feature (in-patenting-process).

Double click your desktop, and all your icons will fade out. Double click again, and they'll return. There's a great walkthrough on setting it up and using it at the.