Timing an Image in Forms

[sg123]

How do I make the image pause for 2 seconds and then hide in the for? The code I used was as follows:-

If Image6.Visible = True Then
PauseTime = 2 ' = 2 seconds
Start = Timer
Do While Timer < Start + PauseTime
Exit_Pause:
Exit Function
End If
 

Thanks a lot in advance.

hide it in the form*?

Even the following code is not working:-

If Image6.Visible = True Then
pause = 1
Image6.Visible = False
 
End If

[zmbd]

Please do not bump your threads; this is against the site policy. Please keep in mind that moderators, experts, and others are un-paid volunteers that attempt to provide some help and guidance in-between our obligations to work and family. Please be patient – especially on holidays and busy posting days.

Please keep in mind: Bytes is not a code writing nor homework service. Please read the FAQ and posting guidlines before reposting your question.

By, simply stating that your code "doesn't work," posting a generic/jargon filled error along with code that appears to have had very little if any troubleshooting performed, and expecting someone to help doesn't usually result in much of an answer and may result in your thread being deleted. Instead, please tell us what you were expecting to happen, what actually happened, for each error: the EXACT title, error number, and descriptions that occurred and at what line in your posted code the error occurred. These are the minimum requirements for posting a question of this nature.

Very first thing, at the VERY top of all of your code modules make sure these lines are present:

Option Compare Database
Option Explicit

Then do a debug compile in the VBA-Editor.
Fix your errors.
Repeat the debug and fix until you have no errors.

Next... what is "timer" on line 3 of code block 1?
I can only assume that you are attempting a call to the timer-function... in which case I suggest that you select that word in your VBA-Editor and press [F1]

Your second code block is, and I don't know how to state this kindly, garbage.

[NeoPa]

It's not clear exactly what you want as you left all your typos in your post and what's there doesn't make a whole lot of sense. What you want can be handled using the Timer. Of that I'm reasonably certain. Setting the value of the picture contol's .Visible property to True and False alternately is also part of the solution. Exactly what, when and where depends largely on the details which are not, so far, found in the question.

[sg123]

Hi NeoPa
I want the image to appear when I click the appropriate command button, stay on-screen for 5 seconds and then disappear. Thanks for your advice.

[NeoPa]

Thank you. That is much clearer.

What you need to do is :

1. Design the form with a Form_Timer() procedure in the module and a value for .TimerInterval of 5000.
2. Set the .Visible property of the image to True in the Form_Open() procedure.
3. In the Form_Timer() procedure set the .Visible property of the image to False then set Me.TimerInterval to 0.

That should do what you require. When you've got it working, look at what you've done and see if you can understand how and why it works ;-)

[ADezii]

If the only criteria is what you stated in Post #4, namely:

I want the image to appear when I click the appropriate command button, stay on-screen for 5 seconds and then disappear,

then there is a much simpler solution bypassing the Form's Timer() Event which I feel is not appropriate in this case.

1. Set the Visible Property of the Image Control (Image6) to No either in Form Design View or prior to the Form displaying any of its Controls.
2. Copy-N-Paste the following Code into the Click() Event of a Command Button.
   

   Dim PauseTime, Start
    
   PauseTime = 5
    
   Start = Timer
    
   With Me![Image6]
     .Visible = True
    
     Do While Timer < Start + PauseTime
      DoEvents
     Loop
    
     .Visible = False
   End With
    

[NeoPa]

ADezii, You seem to be under the impression that looping through code for 5 seconds is a better solution than using the Timer approach. I cannot conceive of why that might be, but I'm open to hearing your reasoning on that.

My understanding would be that using a Timer based approach is infinitely better as it enables one to avoid the clumsiness of code looping. On the other hand, if you must loop through code, then including a DoEvents statement is certainly the way to go about it.

PS. When dealing with Timer() you need to allow for the fact that 23:59:57 will never result in a value that is 5 seconds on. It is more reliable to deal with the return value of Now(), which deals in values of days. Minutes are in increments of 1 / (24 * 60).

[ADezii]

The Logic behind a Form's Timer() Event is to allow periodic/scheduled execution of a Macro or piece of Code automatically at set intervals. This is something that would involve a timed Database Event. I do not see a 1-Time display of a Graphic Image for a period of 5 seconds as falling into this category. I honestly feel that the use of the Timer() Event, in this specific scenario, is counter intuitive.

[NeoPa]

ADezii:
The Logic behind a Form's Timer() Event is to allow periodic/scheduled execution of a Macro or piece of Code automatically at set intervals.

I don't believe that's correct. A timer event is there for any time related or scheduled job. This can be a one-off just as much as a repeating job.

The idea of code tying up the processor (albeit less completely with the DoEvents calls), just doesn't make sense to me when compared with the opportunity to let the system call you as and when the time period has expired. This is very similar to the situation where the choice was between polling a status and allowing an interrupt to trigger the code that needs to run. The interrupt approach was always preferred due to the lack of negative side-effects. I cannot see that the same issues are not involved here.

The timer call is based on a chip that maintains the time and works outside of the sequence of instructions processed by the main processor. Thus, the main flow of the processor is only involved exactly when necessary. Continually polling the state of the time, on the other hand, ties the processor up very heavily to do a similar job. I find it very hard to understand why the latter would ever be preferred to the former.

[sg123]

Thanks to both of you....my problem is solved :)