Re: Form Timer issue in Access Game

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jeff Conrad (jeffc_at_ernstbrothers.com)
Date: 03/05/04


Date: Fri, 5 Mar 2004 15:31:46 -0800

Hi Kelvin,

Thanks for the help.
Forgive my stupidity, but I'm a little confused by your response.
After the second text box is revealed I don't use the Timer Event at all.
(That is still running in the background)
I basically tell Access to count to a really high number in a loop.
Was that what you are suggesting?
I even tried to define it as a private variable, but the same result.
If I don't put in the DoEvents line, the second text box is never revealed.
If I leave it in, the stopwatch counter on the form pauses just for a spilt
second.

I'm pretty sure I'm just going to have to live with it.
Thanks,
Jeff Conrad
Bend, Oregon

"Kelvin" <klu@klu.com> wrote in message
news:OBPNxnvAEHA.2768@tk2msftngp13.phx.gbl...
> Howabout instead of using a timer after the second box is revealed, using
> the OnTimer event to check if the text box is showing then increment some
> global variable. At some point, in a later OnTimer event, check the value
> of this variable then blank out the text boxes.
>
> Kelvin
>
> "Jeff Conrad" <jeffc@ernstbrothers.com> wrote in message
> news:%23thTFQvAEHA.1516@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > Using Access 97 here.
> >
> > I finished making a game in Access, but there is just one residual issue
I
> > have a question about. I can live with this problem, but I'm wondering
if
> > there is a work-around.
> >
> > As the game is in progress a "clock" on the form displays the elapsed
time
> > like a stop watch. The game is a matching game. If you select two
> un-matched
> > tiles you see the value in the text box for just a spilt second so
> hopefully
> > you remember where it is.
> >
> > In order to accomplish this I had to code the second box like so:
> >
> > ' No match so wait just a spilt second to enable
> > ' the user to see the two values
> > For Counter = 1 To 2000000
> > ' Set a small counter loop
> > If Counter = 100000 Then
> > ' Pause so we can see it
> > DoEvents
> > End If
> > Next Counter
> >
> > I had to add in the DoEvents line because no matter HOW big of a number
I
> > put in to the Counter you were never able to see the second box! Not
good.
> > Adding in the DoEvents line makes it work perfect, but there is one side
> > effect: the stopwatch timer on the form pauses for just a spilt second.
> Now
> > I *can* live with this, but is there any way to have the best of both
> > worlds: keep the stopwatch going AND be able to see the text box for
just
> a
> > bit? Probably not, huh?
> >
> > Thanks,
> > Jeff Conrad
> > Bend, Oregon
> >
> >
>
>



Relevant Pages

  • Re: Form Timer issue in Access Game
    ... Howabout instead of using a timer after the second box is revealed, ... At some point, in a later OnTimer event, check the value ... The game is a matching game. ... the stopwatch timer on the form pauses for just a spilt second. ...
    (microsoft.public.access.forms)
  • Re: mouse_event help
    ... then DoEvents and Release LeftMouse. ... I have a Timer ... It works if I am on the Desktop but in game ...
    (microsoft.public.vb.general.discussion)
  • Re: Event Handling in vb.net
    ... it appears to block the Timer event. ... If you are super paranoid about it, I would suggest you protect all events. ... Me I only protect those routines that I know I am calling DoEvents ... Handlers may call MessageBox.Show to display exceptions to the user, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Timer issue
    ... You can still put the timer logic in the Game class. ... If client get into the game before timer trigger, then good, otherwise ... | the server at this stage, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Event Handling in vb.net
    ... which will need a timer. ... the timer handler, requires two threads, right? ... Windows is using more than one thread. ... > If I call DoEvents while processing an Event, I normally set a flag in the ...
    (microsoft.public.dotnet.languages.vb)