FlashFXP 5.1.0 build 3834

# Fixed:
- Loading and executing a saved queue that references sites by ID (i.e Auto saved queues) that no longer exist in the Site Manager could under some conditions cause FlashFXP to get stuck in an infinite loop and lock up.
- Under a rare condition the Queue List window might cache the wrong site name and the remark column would display the wrong site name. This did not effect functionality and was only a visual issue.
- Local browser drag operations incorrectly passed a UTF-8 encoded path-name when calling a windows API when it should of used Unicode path-name, this caused some drag/drop operations to fail.
- After the desktop color depth changes sometimes FlashFXP would incorrectly render the toolbar buttons with an opaque background.
- If FlashFXP is left minimized while the local browser is displaying the content of a network drive/location and this location becomes unavailable it could cause FlashFXP to freeze for an unusually long time or lockup when restoring the window.
- Synchronized browsing issue where the remote synchronized root path was not correctly defined under some conditions.
- Scheduled tasks > If the task failed as a result of being unable to resolve the server host name this reason was not clearly indicated.
- Internal file read-only check on data files was incorrectly passing Unicode file-names to ANSI version of APIs.
- Eliminated multiple RedrawWindow() API calls after unlocking the window canvas for drawing due to erroneous DrawLockLevel evaluation.
- Indirect site to site transfers were experiencing a problem that caused the UI to appear frozen between the download and upload operations while waiting for the file to become ready.
- In some cases FlashFXP was unnecessary reloading the FlashFXP data files from disk.
- Remote editing, auto uploading on save could in some specific cases try to upload even when another operation is in progress resulting in a failed upload.
- After a download transfer failure attempting to re-transfer the file could incorrectly result in the file being skipped.
# Changed:
- Clipboard monitor now uses a more reliable monitoring method on Windows Vista and up.