Introducing 64bit builds
A brief note on the introduction of 64bit binaries for Cyotek products.
Future versions of Cyotek products will retarget to use .NET Framework 4.8, from the current of 4.6, preventing them from being installed on older versions of Windows.
With various (in theory) safeguards in place, and concious that sometimes there is quite a delay between official releases, we've decided to have the latest CI build for supported products automatically uploaded to cyotek.com each day, allowing adventurous end users to get access to fixes sooner than normal releases.
Every so often, we'll receive a Google alert which has a link to HerdProtect or TotalVirus with a page merrily listing one of Cyotek's executable files are being a virus. I'll duly check these pages only to discover that while it might be one of our files (or a file with the same version information), it has been modified, renamed and then dumped in one of the Windows system folders attempting to masquerade as another component. This sort of thing isn't really great advertising for Cyotek, so I thought I would write this post reminding users to take caution when downloading files and to use common sense, along with outlining how you can check if the files are valid.
A brief insight into why updates to our products are taking longer than usual, and some of the steps we are taking to try and resolve this.
At some point in the last few days, COMODO have revoked the certificate we use, for reasons I'm still trying to ascertain from their support department. The net result of this is every Cyotek product released in the past 10 months is now unusable, as when you try and start any executable, it will immediately crash due to the revoked certificate.
After the last mammoth update to Gif Animator, I wanted a task that was slightly distracting rather than just fixing bugs. A couple of requests in the past have been about localization, so I had a look at the metrics we have gathered on software usage to see what different languages were being used. The vast majority of sessions for all our products (around 70%) used English, followed by a variety of other locales, the top four being French, Chinese, Spanish and Russian (around 20% for those four) with the final 10% in a long list of other languages. So, well worth taking a look at localization, and this article describes some of the progress that has been made and the issues encountered.
In my last "all products" update, I discussed how the user interface was being made more useful. In this second, shorter, update I will briefly cover upcoming changes to how application settings are stored, both their format and the location.
All our current tools use a standard series of libraries we've developed over the years, and provide vast amounts of common functionality, from settings management, windows and UI components, plug-ins, and a lot more. However, they all work around the principle of a single application window bound to a single document, with a variable amount of custom views that can be hosted in that window. This post has a sneak peak at upcoming application features, chiefly (and finally!) multiple document support, and dockable windows.