Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd+down doesn't work when "workbench.list.openMode": "doubleClick" is set #68469

Closed
Tyriar opened this issue Feb 11, 2019 · 5 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug tree-widget Tree widget issues verified Verification succeeded
Milestone

Comments

@Tyriar
Copy link
Member

Tyriar commented Feb 11, 2019

Found in #68018

@roblourens roblourens added the bug Issue identified by VS Code Team member as probable bug label Feb 12, 2019
@roblourens roblourens added this to the February 2019 milestone Feb 12, 2019
@roblourens roblourens added the tree-widget Tree widget issues label Feb 12, 2019
@Tyriar
Copy link
Member Author

Tyriar commented Feb 25, 2019

@roblourens maybe I'm doing something wrong but I removed all my settings and keybindings, searched something and now pressing cmd+down and cmd+return when focus is on a search result and it's doing nothing. Am I thinking right in that this should do the same thing as cmd+1? (since a preview editor will be opened)

This happens when both doubleClick and singleClick are set.

@Tyriar Tyriar reopened this Feb 25, 2019
@roblourens
Copy link
Member

@joaomoreno this is from 3946e32

It sounds right to not trigger onDidChangeSelection when the selection did not actually change, but we can select a selected element to make different things happen.

Similar, select an element in the file explorer then alt+click. It should open to the side (on mac) now it does nothing.

@roblourens
Copy link
Member

roblourens commented Feb 25, 2019

Maybe the same, "go to definition" on something with multiple definitions (like the onDidChangeSelection event) and the first item in the peek tree is selected but it no longer navigates to that item right away.

@isidorn
Copy link
Contributor

isidorn commented Feb 26, 2019

Feels like a duplicate of #69284
Leaving up to @joaomoreno to decide if to close as dupe.

@isidorn isidorn assigned joaomoreno and unassigned roblourens and isidorn Feb 26, 2019
@joaomoreno
Copy link
Member

It was hard to understand what is the issue here, since I didn't know what Enter should do in that case. After testing stable, I verified that Enter should open and focus the editor. I've pushed a fix for that.

This happens when both doubleClick and singleClick are set.

@Tyriar Correct. Even in stable. My fix should cover that as well.

Maybe the same, "go to definition" on something with multiple definitions (like the onDidChangeSelection event) and the first item in the peek tree is selected but it no longer navigates to that item right away.

Can't repro that any more, maybe got fixed today with my other changes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug tree-widget Tree widget issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants