IE9 is going to be a major release that puts Microsoft's browser on track to follow existing web standards; what's more important, it looks like Microsoft has abandoned the 'I'm the standards' position that made IE win the first browser war against Netscape, and was making it lose the second one.
Trying to maintain that position any longer would have made the world progressively shift to other browsers, as in fact is happening in the past few years.
Coming back to the topic, another supposed IE9 user interface has leaked, as you can see from this image. Other supposed user interface screenshots that circulated earlier this year showed an oldstyle user interface, but this image seems to confirm other statements published recently in the blogs that anticipated how the user interface should look like. If this screenshot is real, it seems that at Microsoft they have followed the minimalistic design of Chrome that I really love, taking it a step further: they seem to leave more room to the content by putting all the browser's user interface in one single line (the tabs), using less space for inactive tabs (just the icon?). Another thing I hope to see in the new user interface is Chrome's 'status bar': in Chrome you see the status information while the page is being loaded, or a link destination as you hover over the link, then the status bar goes away to leave room to the content. In IE8 you still have to choose whether you want to see the status bar (and lose its space) or you do not want it (and lose the information).using System;
using System.Windows.Forms;
using System.Threading;
static class Program {
[STAThread]
static void Main() {
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new TestForm());
}
}
public class TestForm : Form {
private Button btn;
public TestForm() {
// Just add a simple button with a Click handler
btn = new Button();
btn.Text = "Click me";
btn.Click += new EventHandler(btn_Click);
this.Controls.Add(btn);
}
void btn_Click(object sender, EventArgs e) {
// We are creating a WorkItem to be run
// on a thread from the thread pool
WaitCallback wc = new WaitCallback(this.DoTheWork);
ThreadPool.QueueUserWorkItem(wc);
}
void DoTheWork(object sender) {
// This code is run in a background thread
try {
// We are using Invoke so the call
// to ThrowWithNiceStackTrace() runs in the main thread
this.Invoke(new MethodInvoker(
this.ThrowWithNiceStackTrace));
}
catch (Exception ex) {
Type ext = ex.GetType();
string stackTrace = ex.StackTrace;
}
}
private void ThrowWithNiceStackTrace() {
// This code is run in the main thread;
// calling Control methods is legal
this.btn.Text = "Clicked";
try {
this.ThrowWithLongStackTrace();
}
catch (Exception ex) {
throw new ApplicationException(
"Exception caught in invoked method", ex);
}
}
private void ThrowWithLongStackTrace() {
this.ThrowDivByZero();
}
private void ThrowDivByZero() {
int i = 1 / string.Empty.Length;
}
}
using System;
using System.Windows.Forms;
using System.Threading;
static class Program {
[STAThread]
static void Main() {
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new TestForm());
}
}
public class TestForm : Form {
private Button btn;
public TestForm() {
// Just add a simple button with a Click handler
btn = new Button();
btn.Text = "Click me";
btn.Click += new EventHandler(btn_Click);
this.Controls.Add(btn);
}
void btn_Click(object sender, EventArgs e) {
// We are creating a WorkItem to be run
// on a thread from the thread pool
WaitCallback wc = new WaitCallback(this.DoTheWork);
ThreadPool.QueueUserWorkItem(wc);
}
void DoTheWork(object sender) {
// This code is run in a background thread
try {
// We are using Invoke so the call
// to ThrowWithNiceStackTrace() runs in the main thread
this.Invoke(new MethodInvoker(
this.ThrowWithNiceStackTrace));
}
catch (Exception ex) {
Type ext = ex.GetType();
string stackTrace = ex.StackTrace;
}
}
private void ThrowWithNiceStackTrace() {
// This code is run in the main thread;
// calling Control methods is legal
this.btn.Text = "Clicked";
try {
this.ThrowWithLongStackTrace();
}
catch (Exception ex) {
throw new InvokeException(
"Exception caught in invoked method", ex);
}
}
private void ThrowWithLongStackTrace() {
this.ThrowDivByZero();
}
private void ThrowDivByZero() {
int i = 1 / string.Empty.Length;
}
}
public class InvokeException : Exception {
public InvokeException(string message, Exception innerException)
: base(message, innerException) { }
public override Exception GetBaseException() {
// Yes, we are lying: the doc says we should return
// 'The first exception thrown in a chain of exceptions'
return this;
}
}
| Note |
|---|
In addition to the InvokeRequired property, there are four methods on a control that are thread safe: |
using System;
using System.Windows.Forms;
using System.Threading;
static class Program {
[STAThread]
static void Main() {
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new TestForm());
}
}
public class TestForm : Form {
private Button btn;
public TestForm() {
// Just add a simple button with a Click handler
btn = new Button();
btn.Text = "Click me";
btn.Click += new EventHandler(btn_Click);
this.Controls.Add(btn);
}
void btn_Click(object sender, EventArgs e) {
// We are creating a WorkItem to be run
// on a thread from the thread pool
WaitCallback wc = new WaitCallback(this.DoTheWork);
ThreadPool.QueueUserWorkItem(wc);
}
void DoTheWork(object sender) {
// This code is run in a background thread
try {
// We are using Invoke so the call
// to ThrowWithNiceStackTrace() runs in the main thread
this.Invoke(new MethodInvoker(
this.ThrowWithNiceStackTrace));
}
catch (Exception ex) {
string stackTrace = ex.StackTrace;
}
}
private void ThrowWithNiceStackTrace() {
// This code is run in the main thread;
// calling Control methods is legal
this.btn.Text = "Clicked";
this.ThrowWithLongStackTrace();
}
private void ThrowWithLongStackTrace() {
this.ThrowDivByZero();
}
private void ThrowDivByZero() {
int i = 1 / string.Empty.Length;
}
}