> >The project window in Pro 7 does not differentiate between regular mouse
> >clicks and context clicks when detecting a double click.
> >Try this with a file in the project window.
> >1) Select a file (click).
> >2) Very quickly (within the double click time) do a context click
> >(control-click) on the same file.
> >What happens:
> >You get a context menu for the item *and* the file opens. Of course since a
> >menu is up the window comes up blank until you dismiss the menu and then it
> >You get a context menu for the item but the file does not open. The context
> >click should reset the double click detection logic.
> I can't duplicate this.
I can clarify the instructions a bit, I think. I'm still running Pro 6,
but I'm pretty sure it's still there.
1) Click on a file in the project window
2) Very quickly control-click on the same file. DON'T MOVE THE MOUSE.
3) Let go of the mouse button, still holding the control key
4) Both the window for the file and the context menu will pop up
In step 3, if you move the mouse, the context menu pops up before you
let go of the button. That seems to make the difference.
OK, I just tried it on a co-worker's Pro 7 on 10.1 and it does the same
If the window comes up in the same area that the context menu would pop,
it either doesn't show the bug, or the context menu is behind the
Palm Digital Media