Desync'd Mouse positioning

[Akitaris]

Describe the bug
The selection of the mouse cursor and where the position of where it actually is, is offset by a massive value.

To Reproduce
Steps to reproduce the behavior:
Constant Issue, on Startup

Expected behavior
Selection sync'd properly with the mouse cursor.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [Windows 10]
• Version [1909]
• DDDEditorGMS2 | Version 01.01.2020

Additional context
I'm going to assume its relevant to the screen resolution. I run in 1360x768.

Potentially add a launcher that allows you to select resolution? Or potentially a .cfg option.

[Akitaris]

Unfortunately it did not capture my mouse cursor, but it is right above the "Create New" button.

[DragoniteSpam]

I run in 1360x768.

Ooh, this was going to be something I was going to have to deal with sooner or later. This is related to #12 which I've been avoiding for a while, but if I want other people to be able to use it (1366x768 is still a pretty common laptop resolution) I should probably sit down and work it out.

[Akitaris]

I run on a desktop, just my monitors native is 720p, its an old flatscreen monitor haha. And hey man I really appreciate all that you do.

…

On Thu, Apr 30, 2020, 7:06 PM Michael Peng ***@***.***> wrote: I run in 1360x768. Ooh, this was going to be something I was going to have to deal with sooner or later. This is related to #12 <#12> which I've been avoiding for a while, but if I want other people to be able to use it (1366x768 is still a pretty common laptop resolution) I should probably sit down and work it out. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APNAI226JJQI5DL6KNS7FC3RPIHAVANCNFSM4MWXKLQQ> .

[DragoniteSpam]

Updated it so that if the window is a different size than what it wants to be the mouse clicks will at least be detected in the correct place. The UI doesn't look especially good when it's scaled and I'm not going to count it as the "correct" solution yet, but hopefully it's at least usable now.