Thats all well and good, but this part seems a bit .. uninformative, or at the very least, easily misunderstood by the harried developer:

>For processes which have not called this function, Windows does not guarantee a higher resolution than the default system resolution.

There should at least be mention that changing this resolution can effect other processes.

Is this a bug? Its hard to see it as a feature.

▲

ninkendo 2 hours ago | parent [-]

> There should at least be mention that changing this resolution can affect other processes.

That sorta is what it’s saying. If you don’t set it yourself, you won’t get any better than the “default system resolution”. But if the default system resolution changes (say, by entering a sort of “performance mode” when playing games or watching videos), then it would imply it will affect all processes that are using the default, right?

	▲	Someone an hour ago \| parent [-]
		Sorta, on Windows < 10. From the same Microsoft page: “Prior to Windows 10, version 2004, this function affects a global Windows setting. For all processes Windows uses the lowest value (that is, highest resolution) requested by any process. Starting with Windows 10, version 2004, this function no longer affects global timer resolution.”