To others: the definitive differential in the file opening experience is
based upon the application's shell association type. Legacy handlers are
limited to 15 selections by default for performance reasons. Applications
using modern shell association methods will not have this limitation.
"Feldspar" <lordwalsingham@xxxxxx> wrote in message
news:74942163-DC36-4511-B50C-BB4A11C2E2F4@xxxxxx
Quote:
> Once again, try reading my post before replying.
I apologize for any misinterpretation in my attempts to clarify what is
fairly evidently a Windows design. You're noticing a behavior, I was
pointing out Why It Works That Way, which I had hoped would be illuminative.
We're clearly not in disagreement over what happens here, right? The only
question here was why, which I had hoped to provide some relevant insight
upon. I apologize for failing in that regard.
Quote:
> It's nothing to do with performance and I wish you'd just drop that,
> you're just flat wrong, why can't you admit it?
I apologize: I did not mean to offend you in any fashion. I had thought
that because I'm on the shell team, know the people responsible for this,
and know the change in question, that my insight might be illuminative. I
realize opinions will always vary, and I do respect and value yours.
Quote:
> Also, your answer doesn't at all address the problem of opening any more
> than just one (1) file at a time with Open With... As soon as I select
> even
> two files, the Open With... option disappears. Even two 1k text files. Are
> you really trying to tell me that they disabled that deliberately because
> of
> performance, and that they thought about that scenario and decided that
> opening 2 x 1k files at once would be devastating? Get real mate, you're
> so
> far wrong it's embarrassing.
No, that's part of WYSIWII. What You Select Is What Is Invoked. The Open
With menu item only supports one selection, so it would be incorrect to make
it available.
I apologize if any of this seems indecisive: you may have a difference of
opinion, but this is definitively the way it works and why it works that
way.
Quote:
> Basically, this is a bug, there's no two ways about it.
OK: I had previously respected your difference of opinion by pointing out
that this behavior is by design for legacy style associations, and that if
you disagree with the current implementation, your best resource would be
actual Product Support where you could attempt to garner support for an
update of some sort. I think we've run the gamut from determining the
behavior, explaining the behavior, and a possible resolution to the
behavior, so I think we're likely done here.
I apologize for being inconsiderate and rude: it wasn't my intention. I've
worked with a variety of external companies to help advise them on file
association issues, and I apologize that in my developer eagerness to help
move you forward I was terse and forgot my manners.
It's interesting that it truncates the dialog at 15 units. I wonder if that
is a configurable unit? Too bad there are no Vista PowerToys. I wonder
what things one might find if one ran a registry monitor. =\
It is too bad that there are no Vista PowerToys. I enjoy that kind of thing
and enjoy tinkering with my system.
-Zach
--
Speaking for myself only.
See
http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.