minitech

When you open or close the Notes form, check or uncheck the ToolStrip button. To handle the case where the user closes the form manually, simply add this in the FormClosing event handler: [CODE]DirectCast(Me.Parent, [B][i]TypeOfParentForm[/i][/B]).[B][i]NameOfToolStripButton[/i][/B].Checked = False[/CODE]

Personally, when doing video-related things I use Monitor.Enter/Exit manually. One UI thread, one capture thread, one saving thread. I find it really helps with performance. So if you would prefer threads over BackgroundWorkers, just keep that kind of performance thing in mind.

I don't know how you might run as an administrator, but you can do a Windows 7/Vista check with this: [code=C#]if(Environment.OSVersion.Platform == PlatformID.Win32NT && Environment.OSVersion.Version.Major >= 6) { // The OS is Win7 or Vista } else { // It's something else }[/code]

No, with the code as-is you have no potential deadlock problems. Static objects are fine, as long as you have a good reason to use them in the particular class. But as for locking static objects and using synchronization on static properties, go ahead. In this case, however, you might …

And yes, using a delegate is the way to go for cross-thread control access. I believe that when an exception is thrown from another thread started using Thread.Start(), it terminates the thread, but when you are not debugging it does not give an error message to the user, just shuts …

I'm Ryan O'Hara from Parksville, 13 years old, VB.NET/C#/JavaScript programmer, nice to meet you all! :)

Your second for loop's conditional part should be [icode]iColumn <= iSize - iRow[/icode].