On Tue, 13 Jan 2009 07:27:46 -0000, "Gordon"
>"--" <--@spammersmustdie.com> wrote in message
>> On Mon, 12 Jan 2009 10:17:40 -0500, "PA Bear [MS MVP]"
>> Strange that Address and Command would have been singled out to be
>> permanently locked. I don't get the logic of that decision either.
>> IE7, as it is, isn't usable for me.
>And that REALLY makes Internet Explorer UNUSABLE?????????
>Do you send a new car back because they've changed the position of switches
>and dials? No of course you don't...
How about if it took a half an hour to get it in gear?
>Jerez - why not just USE it as it is, like MILLIONS of others.
Now now. You snipped my comments about why it is unusable:
My previous comment, replaced:
.....I was speaking of adding an item to Favorites,
of course. As far as I know, neither the Favorites Center or the
Favorites dropdown have a mode where all the folders are
auto-expanded, do they? I have to wonder why Add to Favorites would
be the only function to do that.
Do you know of a registry tweak to stop that? (I doubt that it
exists, since I see know evidence that they used a Tree control for
the Add menu. I'm assuming that I will have to uninstall IE7)
To put this into perspective: A couple of our development machines
have 1500 folders in Favorites. They're sorted references to various
programming sites, code snippets, etc. IE7 takes about 20 seconds just
crunching before even thinking about opening the menu. Then I'm forced
to scroll through page after page of folder names looking for the
If you think that is usable, I invite you to try a test. Using TweakUI
(from Microsoft's site), you can set your Favorites folder to any
location that you want. (Or you could just rename your current
favorites, etc). Find a tree with 1000 subfolders, set Favorites to
it temporarily, and see if you still think that's well-written, usable
If you don't have that large a folder tree, and if you can compile C#
code, I can write a program to create the tree for you.
IE6's Add-to-Favorites function was perfectly usable, and evidently
even included intelligent 'deferred' handlers for opening TreeControl
branches (otherwise, it would still take 20 seconds to create the
control, whether all nodes were displayed or not).
Since this would not have been a frontline security issue, I don't
understand why Microsoft broke their code. That should have been
reviewed by knowledgable users who understand more stressful