"Error in parameter" with negative window handles

[pjeby]

Although /LWOD is listing negative window handles like -925692446, passing that handle into e.g. /GDFWH: does not work: it says "Error in parameter" instead. Converting the negative number to its two's complement (3369274850) doesn't work either, presumably because it overflows the int32 type being used. I'm guessing it also might just be that the code is checking for positive numbers when it'd be equally valid for them to be negative - probably just checking for != 0 instead of >0 would fix it.

[MScholtes]

Hello @pjeby,

I thought it could never come to this. How long your Windows is running?

I will check for this and think will resolve in the next release.

Greetings

Markus

[pjeby]

Thanks! Thing is, it's not a matter of sequential assignment -- most of my windows had very small handles, only a few had the negative ones, and after a while those were gone too. I'm not able to get negative handles by any specific process, they just show up sometimes, no idea why. It's probably something pseudorandom, because one of my desktops has these handles right now:

462710
854932
12846466
133258
1576062
8849888
394998
394980
2296792

And AFAICT there is no correlation between the magnitude of the handle and how new/old the window is. Most handles are 6 digits, and a few are 7 or 8... apparently some very rare ones hit 9 or 10.

Anyway, thanks for having a look-in.