71 lines
9.6 KiB
HTML
Executable File
71 lines
9.6 KiB
HTML
Executable File
<html>
|
|
<head>
|
|
<title>advanced</title>
|
|
<link href="hydrus.ico" rel="shortcut icon" />
|
|
<link href="style.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class="content">
|
|
<h3>this is non-comprehensive</h3>
|
|
<p>I am always changing and adding little things. The best way to learn is just to look around. If you think a shortcut should probably do something, try it out! If you can't find something, let me know and I'll try to add it!</p>
|
|
<h3>advanced mode</h3>
|
|
<p>To avoid confusing clutter, several advanced menu items and buttons are hidden by default. When you are comfortable with the program, hit <i>help->advanced mode</i> to reveal them!</p>
|
|
<h3>searching with wildcards</h3>
|
|
<p>The autocomplete tag dropdown supports wildcard searching with '*'.</p>
|
|
<p><img src="wildcard_gelion.png"/></p>
|
|
<p>The '*' will match any number of characters. Every normal autocomplete search has a secret '*' on the end that you don't see, which is how full words get matched from you only typing in a few letters.</p>
|
|
<p>This is useful when you can only remember part of a word, or can't spell part of it. You can put the '*' anywhere, but you should experiment to get used to the exact way these searches work. Some results can be surprising!</p>
|
|
<p><img src="wildcard_vage.png"/></p>
|
|
<p>You can select the special predicate inserted at the top of your autocomplete results (the highlighted '*gelion' and '*va*ge*' above). <b>It will return all files that match that wildcard,</b> i.e. every file for every other tag in the dropdown list.</p>
|
|
<p>This is particularly useful if you have a number of files with commonly structured over-informationed tags, like this:</p>
|
|
<p><img src="wildcard_cool_pic.png"/></p>
|
|
<p>In this case, selecting the 'title:cool pic*' predicate will return all three images in the same search, where you can conveniently give them some more-easily searched tags like 'series:cool pic' and 'page:1', 'page:2', 'page:3'.</p>
|
|
<h3>exclude deleted files</h3>
|
|
<p>In the client's options is a checkbox to exclude deleted files. It recurs pretty much anywhere you can import, under 'import file options'. If you select this, any file you ever deleted will be excluded from all future remote searches and import operations. This can stop you from importing/downloading and filtering out the same bad files several times over. The default is off. You may wish to have it set one way most of the time, but switch it the other just for one specific import or search.</p>
|
|
<h3>inputting non-english lanuages</h3>
|
|
<p>If you typically use an IME to input Japanese or another non-english language, you may have encountered problems entering into the autocomplete tag entry control in that you need Up/Down/Enter to navigate the IME, but the autocomplete steals those key presses away to navigate the list of results. To fix this, press Insert to temporarily disable the autocomplete's key event capture. The autocomplete text box will change colour to let you know it has released its normal key capture. Use your IME to get the text you want, then hit Insert again to restore the autocomplete to normal behaviour.</p>
|
|
<h3>tag censorship</h3>
|
|
<p>If you do not like a particular tag or namespace, you can easily hide it with <i>services->manage tag censorship</i>:</p>
|
|
<p><img src="tag_censorship.png" /></p>
|
|
<p>You can exclude single tags, like as shown above, or entire namespaces (enter the colon, like 'species:'), or all namespaced tags (use ':'), or all unnamespaced tags (''). 'all known tags' will be applied to everything, as well as any repository-specific rules you set.</p>
|
|
<p>A blacklist excludes whatever is listed; a whitelist excludes whatever is <i>not</i> listed.</p>
|
|
<p>This censorship is local to your client. No one else will experience your changes or know what you have censored.</p>
|
|
<h3>importing and adding tags at the same time</h3>
|
|
<p><i>Add tags before importing</i> on <i>file->import files</i> lets you give tags to the files you import <i>en masse</i>, and intelligently, using regexes that parse filename:</p>
|
|
<p><img src="gunnerkrigg_import.png"/></p>
|
|
<p>This should be somewhat self-explanatory to anyone familiar with regexes. I hate them, personally, but I recognise they are powerful and exactly the right tool to use in this case. <a href="http://www.aivosto.com/vbtips/regex.html">This</a> is a good introduction.</p>
|
|
<p>Once you are done, you'll get something neat like this:</p>
|
|
<p><img src="gunnerkrigg_page.png"/></p>
|
|
<p>Which you can more easily manage by collecting:</p>
|
|
<p><img src="gunnerkrigg_chapter.png"/></p>
|
|
<p>Collections have a small icon in the bottom left corner. Selecting them actually selects many files (see the status bar), and performing an action on them (like archiving, uploading) will do so to every file in the collection. Viewing collections fullscreen pages through their contents just like an uncollected search.</p>
|
|
<p>Here is a particularly zoomed out view, after importing volume 2:</p>
|
|
<p><img src="gunnerkrigg_volume.png"/></p>
|
|
<p>Importing with tags is great for long-running series with well-formatted filenames, and will save you literally hours' finicky tagging.</p>
|
|
<h3>tag migration</h3>
|
|
<p class="warning">At <i>some</i> point I will write some better help for this system, which is powerful. Be careful with it!</p>
|
|
<p>Sometimes, you may wish to move thousands or millions of tags from one place to another. These actions are now collected in one place: <i>services->tag migration</i>.</p>
|
|
<p><img src="tag_migration.png" /></p>
|
|
<p>It proceeds from left to right, reading data from the source and applying it to the destination with the certain action. There are multiple filters available to select which sorts of tag mappings or siblings or parents will be selected from the source. The source and destination can be the same, for instance if you wanted to delete all 'clothing:' tags from a service, you would pull all those tags and then apply the 'delete' action on the same service.</p>
|
|
<p>You can import from and export to Hydrus Tag Archives (HTAs), which are external, portable .db files. In this way, you can move millions of tags between two hydrus clients, or share with a friend, or import from an HTA put together from a website scrape.</p>
|
|
<p>Tag Migration is a powerful system. Be very careful with it. Do small experiments before starting large jobs, and if you intend to migrate millions of tags, make a backup of your db beforehand, just in case it goes wrong.</p>
|
|
<p>This system was once much more simple, but it still had HTA support. If you wish to play around with some HTAs, there are some old user-created ones <a href="https://www.mediafire.com/folder/yoy1dx6or0tnr/tag_archives">here</a>.</p>
|
|
<h3>custom shortcuts</h3>
|
|
<p>Once you are comfortable with manually setting tags and ratings, you may be interested in setting some shortcuts to do it quicker. Try hitting <i>file->shortcuts</i> or clicking the keyboard icon on any media viewer window's top hover window.</p>
|
|
<p>There are two kinds of shortcuts in the program--<i>reserved</i>, which have fixed names, are undeletable, and are always active in certain contexts (related to their name), and <i>custom</i>, which you create and name and edit and are only active in a media viewer when you want them to. You can redefine some simple shortcut commands, but most importantly, you can create shortcuts for adding/removing a tag or setting/unsetting a rating.</p>
|
|
<p>Use the same 'keyboard' icon to set the current and default custom shortcuts. </p>
|
|
<h3>finding duplicates</h3>
|
|
<p><i>system:similar_to</i> lets you run the duplicates processing page's searches manually. You can either insert the hash and hamming distance manually, or you can launch these searches automatically from the thumbnail <i>right-click->find similar files</i> menu. For example:</p>
|
|
<p><img src="similar_gununu.png" /></p>
|
|
<h3>PIL errors</h3>
|
|
<p>At some point, you will probably encounter a PIL error when importing a file. PIL is the Python Image Library, the code I use to manipulate image files. Some files are kooky, and just won't load with it. I can't fix these errors, since PIL is not mine. Just gotta deal with it.</p>
|
|
<p>If the PIL error'ing file is one you particularly care about, I suggest you import it into photoshop or similar and save it again. Photoshop should be clever enough to parse the file's weirdness, and then it'll hopefully save again to a simpler format that PIL, and hence the client, will be able to understand.</p>
|
|
<h3>busted up gifs</h3>
|
|
<p>Animated gifs are a real pain in the neck. The standard permits odd palettes and colourspaces, and PIL has a hard time parsing it all. I try my best to compensate, but some still break for reasons I can't fathom. I have fixed most of this on Windows by moving to OpenCV for gif rendering, but it still affects Linux and macOS.</p>
|
|
<p>So, some gifs will have a coloured first frame but grey frames thereafter; or they will have odd washy noise all over; or they will just be black. The file isn't broken, the client is just looking at it wrong.</p>
|
|
<h3>setting a password</h3>
|
|
<p>the client offers a very simple password system, enough to keep out noobs. You can set it at <i>database->set a password</i>. It will thereafter ask for the password every time you start the program, and will not open without it. However none of the database is encrypted, and someone with enough enthusiasm or a tool and access to your computer can still very easily see what files you have. The password is mainly to stop idle snoops checking your images if you are away from your machine.</p>
|
|
</div>
|
|
</body>
|
|
</html>
|