News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Forum members' graphics/monitor setup

Started by sinsi, January 24, 2025, 04:45:25 PM

Previous topic - Next topic

sinsi

What is your setup? I'm asking because I have a 4K* monitor, if I size my program's window to make it fit the resolution it is usually too big for HD (1920x1080) but one for HD is tiny. Just wondering whether it's worthwile to adjust things on startup (sizes, fonts etc.).

My setup is
  graphics               NVIDIA GeForce RTX 3070 Ti
  primary monitor  3840x2160, 100% DPI (I cheat, desktop icons are bigger via ctrl+mousewheel)
  second monitor   1200x1920, 100% DPI (portrait, to view documents)

*4K: memory=4096, disk=4000, monitor=3840  :rolleyes:

TimoVJL

#1
It might lead to problems with dialog designers ?

Two 24 " Samsung curved FullHD monitors.

24" LED Monitor C24F390FHA with Curved Display
May the source be with you

zedd151

You never know what any particular users screen resolution might be. Are they on a laptop?, are they using ancient hardware?

I generally assume a user has monitor( or laptop screen) no larger than the legacy 1024 px. width x 768 px. height... that is if I expect others to use my programs.

Dynamically resizing to fit larger dimensions is possible of course, but to do it properly is both time consuming and produces a lot of extra code. You could do it in WM_PAINT I assume (never really tried it), but stretching to fit larger dimensions seems a less than optimal approach.

My desktop monitor is currently 1600x900 recommended size. The laptop is 1920x1080. Anything larger I consider a television, or home theater. (To be viewed at a distance) But that's just my personal opinion.  :tongue:

¯\_(ツ)_/¯

jj2007


daydreamer

1920x1080 with my newest Intel hd graphics card,15 inch laptop optional I use 40 inch 1920x1080 resolution as external monitor
You could use screen mode winapi to change screen resolution if user agrees, thinking if you made slow gdi game drawing using 4k hires it becomes too slow stretchblt up sizing to 4k
Consider change character size to different sizes by user,too tiny text might be harder to read on 4k monitor compared to lower resolution

I already got trouble earlier with make game for 1366x768 widescreen laptop monitor and other members tried game had 1024x768 monitors had trouble, that's also something think about


my none asm creations
https://masm32.com/board/index.php?topic=6937.msg74303#msg74303
I am an Invoker
"An Invoker is a mage who specializes in the manipulation of raw and elemental energies."
Like SIMD coding

fearless

Monitor 1 (Main)
LG 27GL850
Resolution 2560x1440 pixels
Frequency 144 Hz

Monitor 2 (Side)
LG 24EN43
Resolution 1920x1080 pixels
Frequency 60 Hz

Greenhorn

High DPI Desktop Application Development on Windows

The drawback is that most of the High DPI API is for Windows 10 and higher.
Kole Feut un Nordenwind gift en krusen Büdel un en lütten Pint.

NoCforMe

1600 x 1200 here.

Maybe if we get enough data points here we can determine what a "typical" or "average" screen resolution is, at least as a kind of starting point.
Assembly language programming should be fun. That's why I do it.

NoCforMe

Also, I have this special setting set in Control Panel (dunno what it's actually called) that sets my preference for the sizes of things, which may effect screen resolution settings for programs:


Assembly language programming should be fun. That's why I do it.

stoo23

On this HP AIO: 1920 x 1080 here as well  :smiley:

ognil

1. Video Adapter > UHD 4096/2160 
EVGA GeForce GTX 970 4GB GDDR5 SSC ACX Coo
1190Mhz Clock, 7010Mhz Memory PCI Express 3.0, DVI, HDMI, 3x Display Port

2. 4096 x 2160 -> Samsung UN55JU6700FXZC - 55" Curved UHD 4K Smart LED TV

My old PC
"Not keeping emotions under control is another type of mental distortion."

NoCforMe

This discussion raises a couple interesting questions.
No. 1, how do you get the resolution programmatically? (Win32 here)
Answer: easily, but you might get conflicting results, depending on what method you use.
Small li'l utility (command line "console" app) attached below. It uses two methods:
  • EnumDisplaySettings()
  • GetSystemMetrics()

> getdisplayres

Values from EnumDisplaySettings():
        Display resolution: 1600 X 1200

Values from GetSystemMetrics():
        Display resolution: 1209 X 907

I think, but am not sure, that the discrepancy may be due to that Control Panel setting I showed above.

There's yet a third way, GetDeviceCaps() which is 'spozed to give the same results as GetSystemMetrics() which I haven't tried yet.

The next interesting question is OK, wise guy: so now you know the user's display resolution. What are you going to do about it?

That, of course, is a rather more open-ended and wide-ranging discussion.

Anyhow.
Assembly language programming should be fun. That's why I do it.

zedd151

Values from EnumDisplaySettings():
        Display resolution: 1600 X 900

Values from GetSystemMetrics():
        Display resolution: 1600 X 900

:biggrin:
Why the discrepancy in yours NoCforMe, between the two?

I looked at the image in your previous post, found the answer.  :tongue:
¯\_(ツ)_/¯

NoCforMe

Well, is that the answer?
I can't think what else it would be.
Aaaaaargh.
Assembly language programming should be fun. That's why I do it.

TimoVJL

May the source be with you