10-26-2025, 12:01 AM
(This post was last modified: 10-26-2025, 12:02 AM by Unseen Machine.)
(10-25-2025, 11:41 PM)SMcNeill Wrote: I think this would be a crazy idea, as _DeskTopWidth isn't set in stone like CONST is. Maybe on *your* system, it never changes, but on my setup I tend to have:So for you, when _DESKTOPWIDTH is called then...it depends on the screen your rendering on! Imagine you launched program on your small screen and then Alt Entered, moved it across to you tv/other panel and the screen you've moved it to has a different res...the initial width, height, aspect ratio etc would suddenly change! AND I agree it's a mess as this is not a problem i haven't encountered!
laptop at 2048 x 1200 resolution
TV at 4096 x 2400 resolution
second monitor at 1920 x 1024 resolution
So I can start a program on the laptop screen, then grab it with the mouse and drag it left/right to the next screen and... my original desktop width isn't my current desktop width. Since such a command is usually involved with scaling, by making it CONST, I've now doomed my program to never scale. It's too small to read on my tv and interact with. Too large to fit my second monitor.
It really just ruined the entire point of the command. Much better to:
Dim Shared As Long ScreenW
ScreenW = _DesktopWidth
Then, you can periodically check to see if that width has changed and respond to it properly inside the program.
BUT my reasoning....IF Aspect ratio or pixel size is calibrated against a "i made it to work on this res" but you can support this...then(again for me its probably relevant only...) a custom Aspect Ratio and/or scale values may be useful...and apparently referencing CONST is twice as fast as referencing variables....and you know me FPS is KING!
Thanks
Unseen
@bplus : "DEFO" is short for definitely!

