Henri Hänninen

I've now gotten a couple more physical size detection failures, I wonder what causes them.. It goes through consistently on the first try though. Edit: Resolution detection has worked correctly...

I need to catch some intermediate step data to see if I can find if anything is different when the detection fails. Couldn't get anything yet.

When the size detection fails I'm getting dc_full values ``` 18446744073424413210 18446744071729909776 18446744072803654137 ``` and when it succeeds they're more like ``` 2063672708 721495611 ``` Is this size discrepancy a...

Thanks for taking a look. I'm having trouble debugging this further: no exceptions are raised so the only output I get of the failure is that the physical sizes and...

Thanks for taking the time to make things rigorous! Unfortunately however, I'm not getting any physical sizes or display names at all. First line print from the callback is never...

However now that I changed `LPRECT(None)` back to `None` I'm getting good values. I kept the new LPARAM(0). Edit: However, I'm now getting a randomly occuring new exception: ``` Traceback...

I ran into a new exception that I added above, and it now fails the enumeration of that specific display that it occurs on and I'm getting an incomplete list...

Now after some testing I got again a `dc_full = 18446744072350667922` and the enumeration only returned resolutions.

It seems that now with the new changes it is possible to get bad `dc` values in the callback even though the original `dc_full` was sensible. Here both callback calls...

With `type(dc)` I get for both `dc_full` and `dc` that ``` dc_full 486610913 type: dc 654382316 type: dc 18446744072971424825 type: ``` Does this help or did you want me to...