Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Double-clicking in file tree should show selection in working set #9032

Closed
peterflynn opened this issue Sep 9, 2014 · 8 comments · Fixed by #9160
Closed

Double-clicking in file tree should show selection in working set #9032

peterflynn opened this issue Sep 9, 2014 · 8 comments · Fixed by #9160

Comments

@peterflynn
Copy link
Member

  1. Open some files in the working set
  2. Find one of those files in the project tree
  3. Double-click it in the project tree

Result: selection indicator is in the project tree

Expected: selection indicator jumps to working set (this is how 0.43 works)

Note: It works correctly if the file was not in the working set before double-clicking. The bug only happens when the file was already in the working set.

@redmunds
Copy link
Contributor

@JeffryBooher I took a look at this one, but I'm not sure how to fix it. DocumentManager.setCurrentDocument() says to "Use CommandManager.doCommand(Commands.CMD_OPEN) instead of DocumentManager.setCurrentDocument()". Interesting that "CommandManager.doCommand()" doesn't exist and "CommandManager.execute()" is actually used, although it doesn't work.

@redmunds redmunds removed their assignment Sep 16, 2014
@JeffryBooher
Copy link
Contributor

What do you mean CMD_OPEN doesn't work?

@JeffryBooher
Copy link
Contributor

@redmunds

@redmunds
Copy link
Contributor

@JeffryBooher In this scenario (when the document is already open in the working set), CMD_OPEN does not change selection from the project tree to the working set as implied by the deprecation message I quoted above.

@JeffryBooher
Copy link
Contributor

Update title in lieu of label

@JeffryBooher JeffryBooher changed the title [SplitView] Double-clicking in file tree should show selection in working set Double-clicking in file tree should show selection in working set Sep 16, 2014
@redmunds
Copy link
Contributor

FBNC back to @peterflynn

@RaymondLim
Copy link
Contributor

This may be fixed for the cases where you don't need to scroll in the sidebar. If you do have to scroll in the sidebar, then you will see issue #9161.

@redmunds
Copy link
Contributor

Confirmed. Closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.