Please help me to figure out a purpose of this code.
-
So you have a ScanTime of 250-270ms. It is generated by subtracting the current time (DateTime.Now) from the _LastScanTime which was populated by the last loop. It represents the number of milliseconds the system takes to complete the processing loop from the VM. PS It is still a very straight forward piece of code which is staggeringly simple. Try adding
Thread.Sleep(100)
after your subtraction line and see what happens.
Never underestimate the power of human stupidity RAH
Holmes>
It represents the number of milliseconds the system takes to complete the processing loop from the VM.I was waiting for this sentence.:thumbsup: For what this stands for? I mean, e.g. a label with mentioned milliseconds inside, on UI screen. Just show to UI user that app is alive? -
Pew_new wrote:
The major question is what do we really have valuable when we do a substraction as follows:
ScanTime = DateTime.Now - _lastScanTime?I cannot see anything 'valuable' in this. It merely gives you the actual elapsed time between the timer start and the first tick. Since your timer interval is set at 250 (milliseconds) it should be somewhere around that value. The question really is what this code is being used for?
Richard MacCutchan>
The question really is what this code is being used for?I would ask you this way. :) My guess is it provides an UI user some kind of "Warning". Something like "Your PC's processor is so busy that the ScanTime went out of allowed time range." Of course in case when value is out of tolerance "window". A value is out of tolerancee "window" - text of value is highlighted with red. -
Richard MacCutchan>
The question really is what this code is being used for?I would ask you this way. :) My guess is it provides an UI user some kind of "Warning". Something like "Your PC's processor is so busy that the ScanTime went out of allowed time range." Of course in case when value is out of tolerance "window". A value is out of tolerancee "window" - text of value is highlighted with red. -
So why exactly are you asking here? We have no information on the context that this code runs inside, or what the application is trying to do.
-
Some info I gave in the first post: Timer -> Timer procedure and calculation -> MVVM pattern -> UI. As said Mr.Holmes. It's very simple code.:thumbsup:
-
It may close this topic. I've got comrehensive answer from Mr.Holmes. If you're interested in. This is answer:
It represents the number of milliseconds the system takes to complete the processing loop from the VM. -
This is in a Class called
ST:public Class ST
{
private readonly System.Timers.Timer _timer;
private DateTime _lastScanTime;public ST()
{\_timer = new System.Timers.Timer(); \_timer.Interval = 250; \_timer.Start(); \_timer.Elapsed += OnTimerElapsed; } public TimeSpan ScanTime { get; private set; } private void OnTimerElapsed(object sender, ElapsedEventArgs e) { try { \_timer.Stop(); ScanTime = DateTime.Now - \_lastScanTime; OnValuesRefreshed(); } finally { \_timer.Start(); } \_lastScanTime = DateTime.Now; } private void OnValuesRefreshed() { ValuesRefreshed?.Invoke(this, new EventArgs()); }}
Then a value of
Scantimeis being transferred via MVVM pattern (ViewModel) to UI. The major question is what do we really have valuable when we do a substraction as follows:ScanTime = DateTime.Now - _lastScanTime? This point I can't figure out. Thanks in advance!There appear to be a couple of structural issues with this code. The first thing is, you haven't shown us the complete class. Secondly, you update _lastScanTime to a different DateTime.Now than when you update ScanTime - in a multi-threaded application, this could be a potentially significant difference because of your ValuesRefreshed. To be honest, I don't know why you don't make ScanTime raise INotifyPropertyChanged.PropertyChanged and avoid other events; you can bind directly to that value. Also, I would use a StopWatch instead of DateTime.Now if I were you.
This space for rent
-
No, it is just the number of milliseconds between the timer starting, and the Elapsed event being fired. This will occur after approximately 250 milliseconds as declared by the timer intialisation values.
Richard MacCutchan wrote:
This will occur after approximately 250 milliseconds as declared by the timer intialisation values.
Ah crap I completely missed that, even after rereading the dammed code.
Never underestimate the power of human stupidity RAH
-
Richard MacCutchan wrote:
This will occur after approximately 250 milliseconds as declared by the timer intialisation values.
Ah crap I completely missed that, even after rereading the dammed code.
Never underestimate the power of human stupidity RAH