Grab it in the usual place.

• Item Limit removed
• Another perf fix
• Browser peice updates the status bar

Here is a little story about ListView's in .Net: Almost everything runs instanteously in the reader, except for this one news feed, google news. I first "solved" the problem by having an item limit. The way this all works is that I inject html into the third pane everytime I got a SelectedIndexChanged notification. While I was debugging something unrelated I noticed that the injection code was getting called too frequently. The problem was that when I selected all the items in the list view, it would call the injection code for only one item, then for having two items, then for having three items... Meanwhile the google feed has in every item (typically 100+ will build up in radio) a picture. When the first injection happens, it starts to load the first image. Before much of anything happens, the image download is cancelled since new html code has been injected. A big DUH went off in my head, and I made it such then when I selected items programatically (ctrl-A, click on a different feed, delete) I wouldn't do any injection till the end. This worked well, and was how I released yesterday's version. What I found today was that (after removing the 50 item limit) I would get the same freeze when going from everything selected to only a single thing selected. Oh Crap! When the user clicks only one entry while everything is selected, the control walks the list of the selected items turning each off INDIVIDUALLY, meaning the first problem again just backwards, but since this is not my code's loop, I can't use the same fix. I needed an event that would fire only after all the selecting and deselecting was finished. In the end, I used KeyUp and MouseMove events to check a bool that gets set when a SelectedIndexChanged notification fires, and then inject the html if needed.
1:48:47 PM    comments ==

turning the crank. Here's a great article about the daily process the Windows Server team is going through now to drive to RTM.... [Incessant Ramblings]
This one focuses on the workings of the Win2k3 War Team, which has the final say in what does and doesn't go into to Windows. Acording to the article it took Ballmer showing up to the War Team and personally justifing the change to get the last minute name change from Windows .Net Server to Windows 2003 Server to happen.
9:29:27 AM    comments ==