Let us check what is causing this issue.įirst check if you have enough memory or storage space to install the updates. I could do wrong here, this looks like Preview bug affecting 32-bit programs to me.I understand that you are unable to upgrade to build 10061. Just to be on the sure side, I declared my program to support Windows 10 by using an embedded manifest and using the corresponding / line with the Windows 10 GUID - this did not help either.Īs querying and adding those two system metric values is rather trivial (no need to include code in this question, I think), I don't have the slightest idea what Unfortunately this does not solve my problem, as that system metric returns 0. Yet 0, at least for 32-bit programs like mine.)Īssuming that Microsoft finally switched off that compatibility measure on Windows 10 I query and add SM_CXPADDEDBORDER now as well. (SM_CXSIZEFRAME alone only continued to work on Vista and beyond thanks to a little compatibility hack by Microsoft, with SM_CXSIZEFRAME still returning the full border size and SM_CXPADDEDBORDER returning Then I learned that already since Windows Vista one is expected to add the value of SM_CXPADDEDBORDER This returned 4 pixels instead of the expected 8 pixels that I got on all previous windows versions up to Windows 8.1. I calculate the size of a window border with the help of the GetSystemMetrics function, using the constants SM_CXSIZEFRAME and SM_CXPADDEDBORDER. I program/maintain a 32-bit desktop (WIN32 API) application and try it now on Windows 10 Preview build 10041. Programming problems as opposed to user problems: Maybe this forum is the wrong place to ask something about Windows 10 Preview, but I did not find a dedicated place to report
0 kommentar(er)
