SuperSize version: 0.1.0

Expected behaviour: Non-maximisable windows should not be able to be supersized.

Actual behaviour: Said windows (like the SuperSize configuration dialog) get supersized anyway, breaking layout with no way to restore them.

Key-value stores are easier to serialise and deserialise, without the need to convert to/from JSON.

At the moment, the plugin API is "anything goes" since the program loads any DLL with potentially malicious code. There are a few ways we can mitigate this risk.

• Keep a list of known plugins and prompt the user for new plugin installations
  • Will ask user if the file just simply appears in the plugin folder, without using the "Install" button
  • Keep track of plugin hashes to check tampering

This is not 100% secure, but it's a step in the right direction without the need for certificates or public key crypto.

I've recently noticed Windows Forms are horrible at scaling to HiDPI displays. It would be better to use another UI Toolkit, such as WPF or WinUI, which tend to scale much better, as well as offer more services for integration with Windows 10 and 11.

For example on how this should look, see the Microsoft PowerToys and ModernFlyouts configuration utilities.

SuperSize actually maximises windows it should ideally not. Check if the window is maximisable before changing its size.

Example below:

The config window should not be maximisable, but SuperSize does it anyway.

I feel like the plugin API is a bit too limited and can easily cause lockups if the logic takes too long to execute. As well as the plugin definition isn't as simple and "safe" as I'd like it to be.

• Make sizing logic asynchrnonous, especially for scripts taking a bit longer to run, such as for IronPython setup and execution.
• Make logic selections a read-only collection. This will prevent other plugins from causing havoc.

CoreLogic (the built-in sizing logic) was made as a separate plugin (included in the SuperSize installer) to test the plugin functionality. This makes testing for developer and the portable version more difficult.

The Python plugin now takes the role of the "demo plugin" from here on out, so we can re-merge it back into the main codebase.