timer

[RobcPettit]

Hi Im using
System.Timers.Timer myTimer = new System.Timers.Timer();
myTimer.Elapsed += new ElapsedEventHandler(onTimer);
myTimer.Interval = 1000;
myTimer.Start();
and getting error onTimer does not exist in the current context. Any
Ideas
Regards Robert

[Galcho[MCSD.NET]]

I suppose this is im method body.
try to declare myTimer in class not in method body

hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

[Marc Gravell]

Well, where /is/ onTimer?

Marc

[Galcho[MCSD.NET]]

try this

class Myclass: Form //probably
{
System.Timers.Timer myTimer;

private void button1_Click(object sender, EventArgs e)
{
myTimer = new System.Timers.Timer();
myTimer.Elapsed += new
ElapsedEventHandler(MyTimer_Elapsed);
timer1.Tick+=new EventHandler(timer1_Tick);
myTimer.Interval = 1000;

}
void MyTimer_Elapsed(object sender, System.Timers.ElapsedEventArgs e)
{
throw new Exception("The method or operation is not
implemented.");
}
}

hope this helps
Galin Iliev[MCSD.NET]
www.galcho.com

[Marc Gravell]

3 big problems with this suggestion:

1) System.Timers.Timer calls back on a different thread (requiring
additional handling)
2) You should dispose the Timer (either forms or system)
3) Because if you don't do 2 it keeps firing forever ;-p

Following illustrates this using 2 timers - one System.Timers and one
System.Windows.Forms; watch the debug output and see the threads being used;
also note that if you get rid of the Dispose override then it keeps firing
even after the end of the form - which can lead to the event trying to
access a disposed form.

Marc

using System;

static class Program {
public class MyForm : System.Windows.Forms.Form {
private System.ComponentModel.IContainer components = null;
private System.Timers.Timer timer1;
private System.Windows.Forms.Timer timer2;
public MyForm() {
components = new System.ComponentModel.Container();
timer1 = new System.Timers.Timer(1000);
timer2 = new System.Windows.Forms.Timer(components);
timer2.Interval = 1000;
components.Add(timer1); // add timer1
timer1.Elapsed += Tick;
timer2.Tick += Tick;
timer1.Start();
timer2.Start();
}
protected override void Dispose(bool disposing) {
if (disposing && (components != null)) {
components.Dispose();
}
base.Dispose(disposing);
}
private void Tick(object sender, EventArgs args) {
System.Threading.Thread thread =
System.Threading.Thread.CurrentThread;
System.Diagnostics.Debug.WriteLine(sender.GetType( ).FullName,
thread.ManagedThreadId.ToString() + "[" + (thread.IsThreadPoolThread ?
"(pool)" : thread.Name) + "]");
}

}
static void Main() {
System.Threading.Thread.CurrentThread.Name = "UI";
using (MyForm form = new MyForm()) {
form.ShowDialog();
}
System.Windows.Forms.MessageBox.Show("Done");
}

}

[RobcPettit]

Thanks for all your replys. I have to admit this has gone beyond my
level of understanding. Ive not long started using c#. What Im trying
to do is every 30sec or so, is update a textbox with what number record
I on. From what ive read on the timer, it started of easy, but I cant
work out wether I need to create a class, then add to project, or use
within my program. Thanks again.
Regards Robert

[Galcho[MCSD.NET]]

you're right

Thank you

Regards,
Galin Iliev[MCSD.NET]
www.galcho.com

[Kevin Spencer]

This is going to sound sarcastic, but I certainly don't mean it any way but
to be genuinely helpful. Bookmark the following in your browser:

http://msdn.microsoft.com/library/en...asp?frame=true

That is the URL of the online Microsoft .Net SDK, and it contains everything
you need to know. The reason I'm giving you such a general reference is due
to your statements that you've just started out using c#, and of course, the
nature of your question. Everyone starts out at the beginning, and mastery
of .Net programming is a long and difficult task.

It's one thing to understand the syntax of a programming language. It's
another thing altogether to understand the vast mountain of tools and
technologies that the .Net platform makes avaialable to you as a developer.
I've been a developer for more than a dozen years, and I still probably
spend a total of an hour a day with my head buried in the .Net SDK and other
resources.

..Net programming is a lot more than writing code. It is the employment of
Object-oriented, event-driven programming and design principles with a
starter kit of tens of thousands of ready-built classes to work with. I am
only familiar with about half of them at this point, and I've been using
them for about 5 or 6 years now. It's intimidating! But the SDK also
contains a large number of articles, tutorials, and sample code to help you
get through it. Start small, start from the beginning, and you might want to
start with some of the "Starter Kits" in the SDK. Otherwise, you'll drive
yourself crazy and likely become discouraged and give up. That would not be
a good thing. .Net programming is very rewarding in the long run! But even
for those of us who love it, it's always a "love-hate" relationship.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

The man who questions opinions is wise.
The man who quarrels with facts is a fool.

<Ro********@yahoo.co.uk> wrote in message
news:11*********************@g10g2000cwb.googlegro ups.com...

Thanks for all your replys. I have to admit this has gone beyond my
level of understanding. Ive not long started using c#. What Im trying
to do is every 30sec or so, is update a textbox with what number record
I on. From what ive read on the timer, it started of easy, but I cant
work out wether I need to create a class, then add to project, or use
within my program. Thanks again.
Regards Robert

[Steve]

On Tue, 23 May 2006 12:37:51 -0400, "Kevin Spencer"
<ke***@DIESPAMMERSDIEtakempis.com> wrote:

This is going to sound sarcastic, but I certainly don't mean it any way but
to be genuinely helpful. Bookmark the following in your browser:

http://msdn.microsoft.com/library/en...asp?frame=true

That is the URL of the online Microsoft .Net SDK, and it contains everything
you need to know. The reason I'm giving you such a general reference is due
to your statements that you've just started out using c#, and of course, the
nature of your question. Everyone starts out at the beginning, and mastery
of .Net programming is a long and difficult task.

It's one thing to understand the syntax of a programming language. It's
another thing altogether to understand the vast mountain of tools and
technologies that the .Net platform makes avaialable to you as a developer.
I've been a developer for more than a dozen years, and I still probably
spend a total of an hour a day with my head buried in the .Net SDK and other
resources.

.Net programming is a lot more than writing code. It is the employment of
Object-oriented, event-driven programming and design principles with a
starter kit of tens of thousands of ready-built classes to work with. I am
only familiar with about half of them at this point, and I've been using
them for about 5 or 6 years now. It's intimidating! But the SDK also
contains a large number of articles, tutorials, and sample code to help you
get through it. Start small, start from the beginning, and you might want to
start with some of the "Starter Kits" in the SDK. Otherwise, you'll drive
yourself crazy and likely become discouraged and give up. That would not be
a good thing. .Net programming is very rewarding in the long run! But even
for those of us who love it, it's always a "love-hate" relationship.

Very sound advice :)

Steve

http://www.pretty-vacant.co.uk