Dear community, in order to ensure portability of simple VIs with front panels containing "copy-pasted" images (used as decoration for the GUI) onto computers with different screen resolution, I thought about setting the resolution of the computer screen to a pre-set value at the start of the VI and reset the initial screen resolution when the VI is stopped (maybe there is a smarter way to ensure coherent rendering of VI front panels with images on different screen resolution while keeping exact distances between elements and images?). After some research, I concluded that the best way to proceed is to use the windows API user32.dll. I found a simple example using user32.dll to get the screen resolution and other system's metrics: very simple. But when it comes to set screen resolution via the user32.dll, then comes the issue of parameter formatting, etc. I am not an expert at all with dll, and I could not find a recent example working for the recent version of LabVIEW and Win (only an old version that is not working, or other solution with custom-made DLLs). But I would like to use user32.dll (also a good way to learn how to use this useful resource). With a bit of googling, window's doc and chatGPT, I managed to make a simple example that does not send error, but nothing seems to be changed. Probably a very stupid mistake or a formatting error somewhere. LabVIEW 2023 on Windows 10 Enterprise on 64-bit operating system, x64-based processor VI attached. Any help is very welcome 🙂 Thanks a lot regards, Hicham

@LLindenbauer wrote: So it seems you were correct in your initial assessment of needing to call system32. Only if you can get that working. But I agree .net doesn't make it a lot easier. That first link is broken, the second uses Resolution Class (Iot.Device.Media) | Microsoft Learn, that seems to be completely out of context. QRes @ Sourceforge might still work. It does, according to How to change screen resolution with command on Windows 10 - Pureinfotech. It would do all the heavy lifting. If it works from the command line, it's easy to call the command line from LabVIEW.