Meilleure que l'histoire actuelle.
This release fixes quite a few bugs, and should reduce memory usage.
This release fixes the most commonly reported bugs and crashes.
Important note: If MaxTo does not start after this update, please download and install .NET Framework 4.7.2. You can also uninstall MaxTo and re-install this version from our website.
This is purely a bug fix release that attempts to fix the most common crashes experienced by end users.
The release has focused mainly on fixing crashing bugs.
movecommand now supports moving a window to a different monitor, while keeping dimensions. See issue #313.
Mostly more bug fixes.
Even more bug fixes.
Lots of bug fixes thanks to all the issues you've found.
null. See issue #282.
The second beta of MaxTo 2.0.0 is here. We've concentrated on fixing crashing bugs, but we've also enabled some new functionality. "Start on logon" is back, as is working window snapping.
The first beta release of MaxTo 2.0.0.
Let's just be honest here: this is a beta release. That's right, we've fixed a lot of bugs, and probably introduced a lot of new ones. Don't expect anything to work well in the early alpha releases.
We've basically rewritten everything from scratch, so expect some crashes.
We've separated the user interface from the underlying functionality in MaxTo, and re-implemented it completely.
This means that everything should feel a lot nicer and fresher; and it should look a lot better on Windows 10!
It also means that we now have full, complete mixed-DPI support! Finally!
Recipes are a powerful new feature of MaxTo, that replaces the previous keyboard shortcut functionality. A recipe is a set of commands assigned to a keyboard shortcut; which means that you can run a lot of commands using one keystroke.
Commands that are ready now include:
You can mix and match these commands as you see fit; and we have nice editors for their arguments in the user interface.
We've started writing proper documentation. Obviously it is not finished as of now, but we have published what we have.
Also, if you have suggestions, you can edit the documentation directly. We will include any approved changes on the website as it is updated.
You can now have different regions on each virtual desktop. Or you can have the same regions on all virtual desktops. It's a setting.
We can now update the compatibility shims (that ensure MaxTo is compatible with other programs) without releasing a new version of MaxTo. You can selectively disable the shims on your machine if desired.
This is a bigger deal than it seems. Previously MaxTo used the monitor number as reported by Windows. That meant that if you had two monitors, MaxTo would only know of them as monitor 1 and monitor 2. If you detached monitor 1, its regions would be applied to the second monitor, as that monitor got renamed "monitor 2", and the settings for the second monitor would be forgotten.
Now MaxTo knows the serial number of each monitor, and will remember the settings for that monitor forever.
We've introduced a new, JSON-based, settings system that automatically reloads any changes to the configuration file immediately. You can find MaxTo's settings in
%AppData%\MaxTo% (by default, you can change this to e.g. store them in your Dropbox).
Our new installer is based on Squirrel, which means we get automatic updates and delta packages "for free". So that's good.
The recipes and commands are designed to work well with a command line interface, so expect to see this to pop up shortly. You'll be able to do things like (syntax may not be final):
C:\> maxto window move -Window "Untitled - Notepad" -Position 0,0 -VirtualDesktop 3 C:\> maxto recipe "Notepad on the left" C:\> maxto preset load "4x4" -Monitor "Dell U3011 (DP)"
All the translation options are missing in this initial alpha release, but it is coming back.
Quite a few things from previous versions of MaxTo where removed, and will not be re-introduced:
We are jumping on the semantic versioning bandwagon. Basically this means that you should be able to tell if there are breaking changes in the version that you are updating to just from the version number.
Since we had previously used
<month> to identify releases, we chose to start at version 2.0 for semantic versioning purposes. Version 2.0.0 nicely reflects what we intended; namely that this is a major upgrade for MaxTo.
As you can probably see from the website, we've changed our prices. The new prices are differentiated between personal and business licenses.
These licenses work as they always have, buy it and you have a lifetime license for anyone in your household.
The price will be $29, which is a price hike from the previous $19. We still think this is quite cheap for a tool such as MaxTo, that you can use for the rest of your life without purchasing another license.
Business licenses are new in that they require renewal every year. The price starts at $19/user/year, and we give significant discounts for purchasing more than one year at a time, as well as volume discounts.
Site licenses are of course still available.
All licenses that are purchased under the old system will continue to be valid going forward.
Note that to use version 2.0.0 or later (including the preview releases), you will need to convert your old license key for a new one.