Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


scanning

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
scanning [2020/03/06 02:25] – [Scanning and using your own plug-ins] shanescanning [2023/05/08 18:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Scanning and using your own plug-ins ====== ====== Scanning and using your own plug-ins ======
-Before you can use any of your own plug-ins with Unify, they must be registered in Unify's [[plugins#unify_s_plug-in_database|plug-in database]].+Before you can use any of your own plug-ins with Unify, they must be registered in Unify's [[plugins#unify_s_plug-in_database|plug-in database]]. You can register plug-ins individually, or you can have Unify scan your system for available plug-ins.
  
-**You can register plug-ins individually by drag/dropping the plug-in file icon into Unify's //plug-ins view//**, or you can choose have Unify //scan for available plug-ins//.+===== Registering individual plug-ins ===== 
 +**You don'have to run a full scan for plug-ins.**
  
-When scanning for plug-ins, Unify actually has to try to load each one. This will certainly trigger any copy-protection mechanisms it uses, and in some cases, may even cause Unify to crash. We therefore recommend the following "pro tips".+You can **register plug-ins individually** in one of two ways: 
 +  - Locate the plug-in file and drag/drop its icon into Unify's //plug-ins view// 
 +  - Click the "Operations..." button at the bottom-left, and choose "Select plug-in(s) to scan" 
 +    * A standard open-file dialog will appear 
 +    * Locate and select the plug-in you want to register, and click "Open" 
 + 
 +===== Scanning your system for plug-ins ===== 
 +You can also have Unify scan your system for available plug-ins. Note that when when scanning for plug-ins, Unify actually has to try to load each one. This will certainly trigger any copy-protection mechanisms it uses, and in some cases, may even cause Unify to crash. We therefore recommend the following "pro tips".
  
 ==== Pro tips for scanning ==== ==== Pro tips for scanning ====
Line 36: Line 44:
 Back in the Known Plug-Ins view in Unify, a progress message in green text will appear at the bottom of the main window, and the "Operations" button will change to "CANCEL SCAN" in red. Unlike the CANCEL button in the //PlugScanner// window, this one actually shuts down //PlugScanner// forcefully. Use it only if you think //PlugScanner// is completely stuck, but give it a bit of time--some plug-ins take surprisingly long to test, so you might see no apparent activity for a minute or more at times. Back in the Known Plug-Ins view in Unify, a progress message in green text will appear at the bottom of the main window, and the "Operations" button will change to "CANCEL SCAN" in red. Unlike the CANCEL button in the //PlugScanner// window, this one actually shuts down //PlugScanner// forcefully. Use it only if you think //PlugScanner// is completely stuck, but give it a bit of time--some plug-ins take surprisingly long to test, so you might see no apparent activity for a minute or more at times.
  
-**PlugScanner may CRASH during scanning.** This is actually normal (we're working on improving this). Unify will automatically re-start it, and it should continue from where it left off. If you moved the //PlugScanner// window, you'll immediately know that it was re-started, because it will seem to jump back to where it was at first.+**PlugScanner may CRASH during scanning.** Unify will automatically re-start it, and it should continue from where it left off. If you moved the //PlugScanner// window, you'll immediately know that it was re-started, because it will seem to jump back to where it was at first.
  
 In a few rare cases, **PlugScanner may get stuck on one particular plug-in**, re-starting again and again. If this happens: In a few rare cases, **PlugScanner may get stuck on one particular plug-in**, re-starting again and again. If this happens:
Line 52: Line 60:
 Once a scan eventually completes, **you may see one or more items in red text** at the bottom of the plug-in list, with an indication that they "appeared to be plug-ins" but couldn't be opened properly. Once a scan eventually completes, **you may see one or more items in red text** at the bottom of the plug-in list, with an indication that they "appeared to be plug-ins" but couldn't be opened properly.
   * In some cases, these are not plug-ins at all, but simply auxiliary files stored in the same folders. These can safely be ignored.   * In some cases, these are not plug-ins at all, but simply auxiliary files stored in the same folders. These can safely be ignored.
-  * Occasionally, you might see a file listed which you're pretty sure is a plug-in. **Try the drag/drop method to re-scan just that file**---this works in many cases.+  * Occasionally, you might see a file listed which you're pretty sure is a plug-in. **Try the individual registration method (see top of this page) to re-scan just that file**---this works in many cases.
  
scanning.1583461510.txt.gz · Last modified: 2023/05/08 18:59 (external edit)