Delete Duplicate File GUI

Overview

The GUI or graphical user interface is the key to using the Delete Duplicates Application. Root documentation at: Python Delete Duplicates This page is the documentation for the GUI.

Screen Shot

This is what it looks like, details on each part below. Still working on it. Note that this screen shot was taken during a debugging session and has some artifacts that will soon disappear, then a new screen shot will be placed here.

1000x2500px

What Does What

General

There are 4 major areas of functionality. Read this guide first then get more information on each at:

• Clipboard Transformations
• Clipboard Snippets
• Clipboard Snips
• Clipboard Commands

The Controls

Control is mostly through buttons. There are two lists at the bottom, clicking on one puts a "snippet" in the clipboard, clicking on the other opens a "snip file" in your system's editor. Outside of the GUI there is also a parameter file which controls start up, your preferred system editor, and many other setting.

Working from top to bottom:

At the Top

• <Window title> Program name and some additional info including version, mode, and the name of any "extra" parameter file ( see Smart Terminal Parameter Examples ).
• <ID Color Band >The red band under the title is an optional component, its height and color is set in the parameter file. It is normally useful only if you are running 2 similar looking applications and want a quick way to tell them apart.

Top Button Row

• <Edit Log> opens an editor on the system ( needs to be configured in parameter file self.ex_editor = <name of executable or link> ) to view the python logging file for the app.
• <Edit Parms > opens an editor on the system to edit the parameters.py file. See <Edit Log>.
• <Restart> Restarts the application ( usually fast ) using new values ( if any ) in the parameter file(s).
• <Help> Will open some sort of help file, text, pdf, or url, depending on configuration in parameter file.
• <About> More or less standard help box.
• <Test> May not be present, for debugging, not generally useful or predictable, you would need to look through the code to see what it might be doing, press at your own risk.