Reef Turner

I probably won't put anymore effort into this PR. Please make modifications as you see fit, or close it.

Those values suspiciously all start with the same digits, are also larger than a 32 bit void pointer (max 4 bytes). To me this indicates memory corruption. The first thing...

I added typing to all the dll function calls. While doing this I found that the types specified for `MonitorEnumProc` were quite wrong.

> hwnd = HDC Good catch, I'll fix that. > pass None to EnumDisplayMonitors I hoped that ctypes would complain if you gave it the wrong type (now that `argtypes`...

Can you print out the type of `dc` inside the callback. I'm wondering if the callback is being given a value that needs to be converted / interpreted properly before...

> Does this help or did you want me to do something ctypes specific? It didn't give me any leads. I can't reproduce the issue that you're seeing in either...

I can't reproduce the issue with bad `dc` values. I've tried 3.7 32 bit, 3.7 64 bit, 3.8 32 bit. I added the following to the `callback` function: ``` python...

Also with: - Windows 10 - Python 3.7.3 - screeninfo version - 0.6.3 The exception being raised in `get_monitors` is ``` Procedure probably called with not enough arguments (4 bytes...

The error from screeninfo is exactly the same `screeninfo.common.ScreenInfoError: No enumerators available` Perhaps what this shows is that the granularity of the error conidtion reporting is not correct. I did...

This is the only version of screeninfo I have tried and on Python 3.7.3. I've worked around the issue in the application that was failing for me. However, looking at...