Prev: MatLab builder Ja
Next: Errors and Warnings after compiling MATLAB GUI m-file
From: Walter Roberson on 9 Jul 2010 17:51
Eric Wait wrote:

> --Time is set to 0 because I am using it to hold the time since the last
> "fresh" call was made. Trying to limit the number of calls that are
> allowed to execute.

I think your logic with respect to setting it to 0 is probably mistaken. If
you had wanted to act to block the _next_ refresh, you could have used

if Time == 0
Time = clock;
return
end


But that isn't what you did. Instead you used

if Time == 0
Time = clock;
end

currenttime = clock

and then compared Time to currenttime. In that situation, though, there would
be negligible time passed between the two clock calls, so the time interval
would be pretty much 0, leading to the refresh being skipped but only
implicitly rather than the simpler explicit call -- and it would be skipped no
longer how long it had been since the last refresh. This leads me to suspect
that you did not realize this situation would exist. The cure for it would be
to use your current code but set Time = currenttime rather than Time = 0 when
you do process a refresh.
First  |  Prev  | 
Pages: 1 2
Prev: MatLab builder Ja
Next: Errors and Warnings after compiling MATLAB GUI m-file