Well that looks interesting. I'll be sure to incorporate that into the script. I see you've been working on the script a bit from the added methods and aliases everywhere.
I like how it reverts the resolution back to what it should be when coming out of fullscreen. Going into fullscreen, though, looked weird--I could see the Window's Start button and highlight over items in my taskbar. Also, it seems you've changed the way the screen scrolls; no matter the resolution, it still uses the 640x480 "center-rule," if you get what I mean.
That add-on is really helpful for first-time users. I'll link to it in the first post. Thanks for your continued support
I've been wanting to get back to finishing this but other priorities, ya know?
SUPER EXCITED EDIT:
Okay, so I have been wondering for the longest time how Cremno's NoF12 (more importantly No Alt+Enter inside it) works. I was looking around the various keyboard functions until I found
RegisterHotKey. After reading it and UnregisterHotKey, I got the impression that this was what I was looking for.
So, to see how the method worked, I whipped up this little thing and put it in module Resolution#initialize at the very end:
@reghotkey = Win32API.new('user32', 'RegisterHotKey', 'LIII', 'I')
@reghotkey.call(0, 1, 0x4001, 0x0D)
To those confused, it basically says "Register new hotkey ALT+Enter to current thread". The 0x4001 is just a combination of MOD_NOREPEAT and MOD_ALT, as seen on the page I linked to. 0x0D is the virtual key code for Enter.
I go to testplay the game and, to my surprise, Alt+Enter no longer put the game into fullscreen no matter how hard I tried. Curious, I ran another game at the same time and couldn't get it to fullscreen either--at least, not until I closed the game with this snippet in it first. This outcome is exactly the same as the NoF12.dll approach.
Would anyone care to back this up and remark if I've made an amazing discovery?