G
Gene E. Bloch
[/QUOTE]I'm talking about where you right-click on an object INSIDE the program,
like a node in a tree list (say, for a folder - which has NOTHING to do
with the file system but merely how the data is organized within the
application). When you click on a tree node, it gets selected. When
you right-click on a tree node, it may not get selected. The context
menu is still showing actions for the node on which you right-clicked
but if you later do some other action, like from a toolbar, then what
you last right-clicked on may not be the selected object.
I don't remember if it was a newsreader or e-mail client where I saw
this. It would show a list of folders or some data grouping in a tree
list on the left side. I'd right-click on a tree node to select some
action from the context menu. Because I had right-clicked on that node
and because I saw the highlight change to that tree node, I figured it
was the selected node, too. Nope, so the menu/toolbar action was
against the actual selected tree node instead of the one that I had just
right-clicked on.
This is not an issue with the common browser dialog presented by Windows
that an app might call up. I'm talking about the UI for the app itself.
I remember one program where I experienced it more than once. It's aI assume that behavior was limited to a single application, and since
we don't know what it was, it'll remain a mystery. Besides the app
name, the other unknown is whether it's an app some of us are likely
to be using. We may never find out.
rarely used & obscure program called Windows Explorer.
Now that I've possibly offended you guys, please take this opportunity
to ignore the above sarcasm
And it really was Explorer...