Overflow error when saving X position of window?? - 23/08/17 07:56 PM
Hi,
I love mIRC, but one thing annoys me. I can use the Position -> Save function on the parent window as many times as I like, but Position -> Reset always puts it at the left edge of the screen, even though I saved it while its right edge was flush with the right border of the screen. The Y position is maintained, though.
If I save the position while the window is in the middle (left-right) of my screen, Reset returns it to the saved position.
This leads me to conclude that there is a cap on the X value when saving the position, and that it gets reset to zero instead of the proper saved position - I could be wrong, but it's the most obvious inference to draw.
As long as I leave the window where I put it, it stays there, and "survives" through reboots. But that is likely Windows' position restore feature, rather than mIRC's.
My screen is 2560x1440, and I'm running mIRC 7.49 on Windows 10 build 1703 x64. My mIRC window is 1050 px wide.
Hope you can fix this, or alternatively point me to the error of my ways. :-)
I love mIRC, but one thing annoys me. I can use the Position -> Save function on the parent window as many times as I like, but Position -> Reset always puts it at the left edge of the screen, even though I saved it while its right edge was flush with the right border of the screen. The Y position is maintained, though.
If I save the position while the window is in the middle (left-right) of my screen, Reset returns it to the saved position.
This leads me to conclude that there is a cap on the X value when saving the position, and that it gets reset to zero instead of the proper saved position - I could be wrong, but it's the most obvious inference to draw.
As long as I leave the window where I put it, it stays there, and "survives" through reboots. But that is likely Windows' position restore feature, rather than mIRC's.
My screen is 2560x1440, and I'm running mIRC 7.49 on Windows 10 build 1703 x64. My mIRC window is 1050 px wide.
Hope you can fix this, or alternatively point me to the error of my ways. :-)