writing files in the Tick events when each write takes longer than the interval

[AAaron123]

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so I
can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are the
past ones simply missed?
Thanks

[rowe_newsgroups]

On Aug 1, 9:33*am, "AAaron123" <aaaron...@road runner.comwrote :

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing soI
can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?

What happens if *the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are the
past ones simply missed?

Thanks

You need to find a solution that doesn't rely on time, otherwise you
will spend the rest of the project's life debugging race conditions.

Is it possible to use a message queue to track the writes? The tick
event would write to the queue, and then the the changes could be
written out from the queue asynchronously.

Also, why not just keep the bitmap in memory and write it to a file
when the changes are done?

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

[Gillard]

what about thread?

"AAaron123" <aa*******@road runner.comwrote in message
news:e0******** ******@TK2MSFTN GP02.phx.gbl...

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so
I can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the past ones simply missed?
Thanks

[Cor Ligthert[MVP]]

Aaron,

Why not do the writing of the file assynchronous in a backgroundworke r.

The queue class will be a greath class to fullfil that.

Cor

"AAaron123" <aa*******@road runner.comschre ef in bericht
news:e0******** ******@TK2MSFTN GP02.phx.gbl...

>I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so
I can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the past ones simply missed?
Thanks

[AAaron123]

Use a thread to write and check to see if the thread is still active??

Is that what you mean?
I'd have to learn how to do that but that would be a plus!

Thanks

"Gillard" <gillard_george s@@@@@@@@@hotma il.comwrote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

what about thread?

"AAaron123" <aa*******@road runner.comwrote in message
news:e0******** ******@TK2MSFTN GP02.phx.gbl...

>I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so
I can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the past ones simply missed?
Thanks

[Gillard]

do you write new image or it is the same image??

"AAaron123" <aa*******@road runner.comwrote in message
news:#6******** ******@TK2MSFTN GP04.phx.gbl...

Use a thread to write and check to see if the thread is still active??

Is that what you mean?
I'd have to learn how to do that but that would be a plus!

Thanks

"Gillard" <gillard_george s@@@@@@@@@hotma il.comwrote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..

>what about thread?

"AAaron123" <aa*******@road runner.comwrote in message
news:e0******* *******@TK2MSFT NGP02.phx.gbl.. .

>>I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing
so I can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the past ones simply missed?
Thanks

[AAaron123]

Not sure what you mean about the queue. I'd have to save the images and the
queue would write them?
Is that what you mean.

In my post I should have said: it is much like saving the frames of a movie.

Thanks
"rowe_newsgroup s" <ro********@yah oo.comwrote in message
news:c9******** *************** ***********@26g 2000hsk.googleg roups.com...
On Aug 1, 9:33 am, "AAaron123" <aaaron...@road runner.comwrote :

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so
I
can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?

What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the
past ones simply missed?

Thanks

You need to find a solution that doesn't rely on time, otherwise you
will spend the rest of the project's life debugging race conditions.

Is it possible to use a message queue to track the writes? The tick
event would write to the queue, and then the the changes could be
written out from the queue asynchronously.

Also, why not just keep the bitmap in memory and write it to a file
when the changes are done?

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

[rowe_newsgroups]

On Aug 1, 9:55*am, "AAaron123" <aaaron...@road runner.comwrote :

Not sure what you mean about the queue. I'd have to save the images and the
queue would write them?
Is that what you mean.

In my post I should have said: it is much like saving the frames of a movie.

Thanks

"rowe_newsgroup s" <rowe_em...@yah oo.comwrote in message

news:c9******** *************** ***********@26g 2000hsk.googleg roups.com...
On Aug 1, 9:33 am, "AAaron123" <aaaron...@road runner.comwrote :

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing so
I
can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?

What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the
past ones simply missed?

Thanks

You need to find a solution that doesn't rely on time, otherwise you
will spend the rest of the project's life debugging race conditions.

Is it possible to use a message queue to track the writes? The tick
event would write to the queue, and then the the changes could be
written out from the queue asynchronously.

Also, why not just keep the bitmap in memory and write it to a file
when the changes are done?

Thanks,

Seth Rowe [MVP]http://sethrowe.blogsp ot.com/

At first take, yes you would need to save each bitmap into the queue
and then write them to files asynchronously.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

[AAaron123]

thanks
"rowe_newsgroup s" <ro********@yah oo.comwrote in message
news:50******** *************** ***********@8g2 000hse.googlegr oups.com...
On Aug 1, 9:55 am, "AAaron123" <aaaron...@road runner.comwrote :

Not sure what you mean about the queue. I'd have to save the images and
the
queue would write them?
Is that what you mean.

In my post I should have said: it is much like saving the frames of a
movie.

Thanks

"rowe_newsgroup s" <rowe_em...@yah oo.comwrote in message

news:c9******** *************** ***********@26g 2000hsk.googleg roups.com...
On Aug 1, 9:33 am, "AAaron123" <aaaron...@road runner.comwrote :

I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not work
correctly.

How can I tell in the tick event if the previous file finished writing
so
I
can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?

What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the
past ones simply missed?

Thanks

You need to find a solution that doesn't rely on time, otherwise you
will spend the rest of the project's life debugging race conditions.

Is it possible to use a message queue to track the writes? The tick
event would write to the queue, and then the the changes could be
written out from the queue asynchronously.

Also, why not just keep the bitmap in memory and write it to a file
when the changes are done?

Thanks,

Seth Rowe [MVP]http://sethrowe.blogsp ot.com/

At first take, yes you would need to save each bitmap into the queue
and then write them to files asynchronously.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

[AAaron123]

sorry, I should have said. A changing image but some may repeat. Missing
some is OK.

So should I use a thread to write and check to see if the thread is still
active and only write if it is not active?
Thanks

"Gillard" <gillard_george s@@@@@@@@@hotma il.comwrote in message
news:Od******** ******@TK2MSFTN GP02.phx.gbl...

do you write new image or it is the same image??

"AAaron123" <aa*******@road runner.comwrote in message
news:#6******** ******@TK2MSFTN GP04.phx.gbl...

>Use a thread to write and check to see if the thread is still active??

Is that what you mean?
I'd have to learn how to do that but that would be a plus!

Thanks

"Gillard" <gillard_george s@@@@@@@@@hotma il.comwrote in message
news:%2******* *********@TK2MS FTNGP04.phx.gbl ...

>>what about thread?

"AAaron123" <aa*******@road runner.comwrote in message
news:e0****** ********@TK2MSF TNGP02.phx.gbl. ..
I have a timer. At each tick, say 0.1 second, I write a file.

If it takes more than 0.1 second to write the file the app will not
work correctly.

How can I tell in the tick event if the previous file finished writing
so I can skip writing at that time?

I write using the Bitmap.Save method.

Maybe I could Open, Write, Close synchronously??

Any ideas?


What happens if the Click event takes more that 0.3 seconds to exit.

Do the click events pile up and then come right after each other or are
the past ones simply missed?
Thanks