Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
COURSE of the MONTH
11 days, 10 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
VB.Net. Close programatically opened form automatically
Posted on 2011-09-10
Hi Experts. I have a form that is opened automatically when a button is clicked. I have set a "for next" loop in the form so that it fades after a certain time if it isnt closed by the user. My problem is that the entire program freezes while the "for next" loop runs. I suspect that each instance of the form should be on a seperate thread to avoid this. Is that correct? Any solutions would be appreciated. Thanks in advance.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3
2
- +1
7 Comments
usea backgroundworker to fade it. Show me your codein the for loop and I can wire up a backgroundworker for you.
Do not use a For Next loop. Use a timer:
Add a Timer control to the form.
Set its Interval property to the time you want (it's in milliseconds: 10000 = 10 seconds)
fade the form in the Timer's Tick event.
Forms automatically runs on their own thread, so you do not have to care about defining threads between forms.
Add a Timer control to the form.
Set its Interval property to the time you want (it's in milliseconds: 10000 = 10 seconds)
fade the form in the Timer's Tick event.
Private Sub Timer1_Tick(sender As System.Object, e As System.EventArgs) Handles Timer1.Tick
'Fade your form
Me.Close 'If you want
End Sub
Forms automatically runs on their own thread, so you do not have to care about defining threads between forms.
Application.DoEvents would work, but a loop is a very bad way of putting a delay anywhere.
The problem is that the loop won't run for the same length of time on different computers. It might be too short on fast machines, and too long on slower ones.
The timer is the best way to set a delay, because it is independent of the microprocessor speed.
The problem is that the loop won't run for the same length of time on different computers. It might be too short on fast machines, and too long on slower ones.
The timer is the best way to set a delay, because it is independent of the microprocessor speed.
Just depends on how you wrote your loop! It could be time based as well...instead of on a fixed Sleep() interval.
But yes, generally speaking, there is often a better choice than a tight loop with DoEvents() in it. ;)
But yes, generally speaking, there is often a better choice than a tight loop with DoEvents() in it. ;)
Active 1 day ago
Thanks everyone for the help.
I understand the timer to do the fading of the form. But I need the form to appear and stay for say 20 seconds then start the fade which takes about two seconds. Would I need two timers then?
I understand the timer to do the fading of the form. But I need the form to appear and stay for say 20 seconds then start the fade which takes about two seconds. Would I need two timers then?
Not necessarily.
The interval of the timer could be reset for 2 seconds after the 20 seconds delay, but both jobs would have to be handled in the same event procedure, which would involve the use of a static variable or another method to know if you are going in the event for the first or second time.
Using 2 timers is thus not only easier, but I think would also be a better design. An object should usually be tasked with only one job.
Simply enable the second timer when the first one fires.
The interval of the timer could be reset for 2 seconds after the 20 seconds delay, but both jobs would have to be handled in the same event procedure, which would involve the use of a static variable or another method to know if you are going in the event for the first or second time.
Using 2 timers is thus not only easier, but I think would also be a better design. An object should usually be tasked with only one job.
Simply enable the second timer when the first one fires.
Featured Post
Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This tutorial demonstrates one way to create an application that runs without any Forms but still has a GUI presence via an Icon in the System Tray.
The magic lies in Inheriting from the ApplicationContext Class and passing that to Application.Ru…
If you're writing a .NET application to connect to an Access .mdb database and use pre-existing queries that require parameters, you've come to the right place!
Let's say the pre-existing query(qryCust) in Access takes a Date as a parameter and l…
This tutorial will teach you the special effect of super speed similar to the fictional character Wally West aka "The Flash"
After Shake : http://www.videocopilot.net/presets/after_shake/
All lightning effects with instructions : http://www.mediaf…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses
Course of the Month11 days, 10 hours left to enroll
752 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.