progman | simple X11 window manager modeled after Program Manager

I think the misconception here is that upcasting actually changes the type of an object.

Any type of casting is just a pointer to the compiler to treat a variable as having a certain type, for the developers benefit. So upcasting a variable with type InternationalPurchaseOrder to a PurchaseOrder might change the way you see it and can interact with it (as you mentioned, fields being restricted), but the variable still references an InternationalPurchaseOrder

Therefore to concretely answer your question, comparing classes will use the equals method declared to their actual type, not the type you have marked it as.

As mentioned in this and this post it seems like the issue is due to a linker error which is caused by (I believe 8 function calls) that are depending on libraries implemented by the User32.dll located in C:\windows\system32 more info about this.

In this current project it seems like you are missing to include additional dependencies. You can include those by going to Project Properties -> Linker -> Input -> Additional Dependencies. Here you can choose to include the User32.dll file or choose the "Inherit from parent or project defaults" option. I believe this will solve your linker errors.

As @JonathanPotter pointed out, when hitting Windows + D or the Show Desktop button, the event WM_WINDOWPOSCHANGING gets fired, and the window gets moved to -32 000, -32 000 (its size also gets changed)

NOTE : a window without the style WS_MINIMIZEBOX seems not receiving WINDOWPOSCHANGING event when hitting Windows + D. Thus, no -32 000 coordinates detection in that case... Also noticed the same issue when using the ex style WS_EX_TOOLWINDOW (as this one gets rid of the minimize box, even if you set the style flag WS_MINIMIZEBOX). Didn't find a solution for that case, so I'm sticking to an overlapped window.

To prevent this movement, just set the flags SWP_NOMOVE and SWP_NOSIZE on the WINDOWPOS structure passed in the lParam

So as a final result, to achieve the wanted behaviour (i.e always behind every other window but always in front of the desktop), the only needed code to add to the doc's sample is the following, placed in the window procedure WindowProc's switch statement :

EDIT : the best place to force the Z order with HWND_BOTTOM thus ensuring the window is always on bottom is also in the WM_WINDOWPOSCHANGING event. Indeed, calling SetWindowPos to force it in the WM_SIZE event when dragging the window over, as I was doing previously, causes some flickering on the window when resizing it, whereas no flickering occurs when setting directly the hwndInsertAfter property of the WINDOWPOS structure in WM_WINDOWPOSCHANGING.

The problem is that in Component.onCompleted the window(the rootObject) has finished building but the engine list has not been updated. The solution is to invoke init_window an instant later using Qt.callLater():

In linux a regular user like your normal working user or the webserver assigned user needs the directory permission "search", which is --x or the bit mask 1, to access the files inside the directory. The permission -r- or the bit mask 2 will give you only the ability to read the file names inside a directory.

To solve the problem you have to change the chmod of the directory /usr/share/php to 755.

You can use InjectionConstructor to provide additional information for the constructor. Use it with ResolveParameter to specify which specific instance you want to inject. Assume you have the following classes and interface:

Since Nginx is changing the request before it reaches the PHP backend, the solution is to add the original request data in somehow to the proxied request.

A common used convention for this is to add the original data in as extra HTTP headers. See X_Forwarded_For as an example of this.

To add the original request path as a new header, add a proxy_set_header directive to Nginx.

Few things to fix/improve.
I'll start off with the actual problem, and then go over stuff you should/could improve.

So the actual problem, every time you run you timer, you set the zoom_toggle variable to be true. So yeah, not much help trying to do any toggles when the value is reset every time.
Move the definition to be at the top of the script, or due to how forgiving ahk is, you could actually entirely skip declaring the variable. That way when it's first used, it's created with the default value of nothing, which evaluates to false.

And now onto other fixes/improvements.
Location of your #directives.
Good/common practice is defining these types of #directives at the very top of your script.

Usage of WinGetPos to get screen width/height.
You could use the A_ScreenWidth and A_ScreenHeight variables to easily get your screen width and height.

Missing return that should end your auto-execute section.
When you launch the script for the very first time, there is nothing that stops the code execution from falling through all the way to your timer's callback label.
Nothing bad will result of this in your case, but for future reference, you don't want this to happen. Use a return to stop code execution and end the auto-execute section.

Redundant code
There is no need to set CoordMode every time you run the timer. Move this command to be at the top of your script.
In your send command, there is no need to wrap - inside { }. That is only done to escape characters that have special meaning in a send command, and - has none. In special cases you may even encounter unwanted behavior by doing this. More about this in the documentation.
Why are Xmax and Ymax being created? They're doing nothing for us?

Usage of Send instead of SendInput
SendInput is faster and more reliable. Should almost always be used over Send.
You can specify SendMode, Input at the top of your script to turn all Send commands into SendInput. Personally I prefer just writing out SendInput.

Legacy code
Technically nothing wrong with using legacy code, but it's definitely not recommended. Compatibility with future AHK versions is non-existent as well. Expression syntax is what should always be used nowadays.
Use the function GetKeyState() instead of the legacy command.
Use the non-legacy operators (&&, ||, etc) instead of legacy AND, OR, etc. Always use := instead of =. Legacy assignment is never used.
Usage of a label is pretty much legacy as well. Should replace with a function, but then I should ensure you understand function scopes as well. If you want, I can.

Here's your revised code: