This page contains a bit about the implementation details of Sizer 4.0. It is intended for those who want to know a bit more about what goes on under the hood.
Sizer 4.0 works slightly differently from previous versions of the program. Sizer installs hooks into all running applications and uses them to detect when a window is resized or when a user interacts with the border. In previous versions of Sizer, special handling was performed inside the target application itself (rather than in the Sizer executable). This approach is both efficient and highly flexible. The problem is that hook code is at the mercy of the target application. Incompatibilities occur when the target application uses undocumented Windows API or does not follow standard Windows programming guidelines (which is far more common than one might think). Therefore Sizer 4.0 follows a slightly different approach. The hook portion only ever listens and then forwards important events to the main Sizer executable. Sizer 4.0 severely restricts the processing it performs in the target application and hence minimizes the risk of incompatibilities. The downside is that Sizer no longer is able to do things that were possible in previous versions. This includes:
Sizer includes an option to Compensate for Desktop Window Manager frame effects but what does that mean?
It controls how Sizer figures out how big a window should be. There are two main ways of doing this:
This option therefore controls which approach is used. It basically says do you want to you the actual window rectangle (option disabled) or do you want to use what is visible (option enabled). Things to Note:.