Thread = new Threading.It doesn’t matter if you have Windows 10, Windows 8.1, Windows 7, or any other version. start the request process thread in the Controller class so as to not do the same request over and over until state change is detected, I do the following: lock (checkLock) Note that when I perform checks to see if I should i.e. Note that the machine does not go into any sleep or hibernate state in this period that the threads just stop, and another note is that the memory sockets is 1, not 2 (as I read that this could affect the threads losing communication with each other if they are compartmentalized to different processor groups and your application is not written to handle this). the date and time keeps updating as expected, but one controller will be stuck in request state and another in a request complete state - and no error messages logged / MessageBox. Some of the threads must have just died off or something as i.e. Now the issue here that I've noticed is that on the Win10LTSB2016 machine, the application stops performing the background operations. Third, note that in MainWindow there is a Threading.Timer (not in code - I know) that is updating the UI with the current date and time every second. Secondly I also have registered to the UnhandledException as well as the ThreadException events of the application which should log any undesired behaviour that occurred.
Now firstly, I know there seems to be some discrepancy between the millisecond delay in the code and the description of the flow - however note that there is another Thread in the Controller which toggles the shouldRequest value at this minute interval which switches up the response messages to perform the "request" when the device's state is requested. Thread = new Threading.Thread(new ThreadStart(() => Public string ProcessResponse(string response) If (!string.NullOrWhiteSpace(anotherResponse)) String anotherResponse = controllerDisplays.ProcessResponse(response) String response = controllers.ProcessRequest(request) Private void AppLifetimeLoopCallback(object state) Now for some privacy policies/reasons I cannot share the exact things that operate here and how the classes are structured, but here is a rudimentary class structure: class MainWindow Post event (a string message from obj1).Wait random period (obj1 with Threading.Timer).Post event message (from background thread to MainWindow).
Update form text (with info from event message).
Post event (a string message from obj1 when MainWindow calls obj1).Wait 1 minute (obj1 with Threading.Timer).I've designed a WinForms application and it works well on my machine (Win7), and in fact other machines, yet when I run the application on a WindLTSB machine, my background threads do not work as expected - yet some do perform as expected.
0 kommentar(er)
