Updating net compact framework
When I tried this in the emulator it actually is predictable.
I’ll definitely notice the high DPI features on that machine. If you are a control provider (commercial or free) and want to chat, please reach out at [email protected] WPF is inherently High DPI aware and compatible because it is based on vector graphics. Higher resolution doesn’t necessarily mean high DPI. Please do reach out to your control providers to tell them which Windows Forms (and WPF) controls you want updated to support High DPI. NET Framework 4.6.2, based on improvements in the Windows 10 Anniversary Update.If you answered unpredictability then proceed to “Don’t be a moron, Mike already tried that” Don’t be a moron, Mike already tried that In my own defence I didn’t realize at the time the event was firing from a thread outside the main UI thread (I’m not sure if that is much of an excuse) Anyways, you like unpredictability eh?I’m guessing when you are updating your UI from a worker thread you are doing something like this: What is happening here is a worker thread is created when this CE application first starts.
I would prefer this over declaring the counter at the class level but it doesn’t appear to be an option for the compact framework.