This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 257399

Summary: Opening class in Usages tab opens it next to the Usages tab
Product: ide Reporter: Exilor
Component: CodeAssignee: issues@ide <issues>
Status: RESOLVED INCOMPLETE    
Severity: normal    
Priority: P3    
Version: 8.1   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: IDE log

Description Exilor 2016-01-04 18:51:59 UTC
Product Version = NetBeans IDE 8.1 (Build 201510222201)
Operating System = Linux version 3.16.0-57-generic running on amd64
Java; VM; Vendor = 1.8.0_66
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.66-b17

Reproducibility: Happens every time

STEPS:
  * Find usage of a class (for example)
  * Usages pane opens in the bottom with all previous tabs up top
  * Click on a class in the usage pane that isn't currently open
  * 
ACTUAL:
 The class will open as a tab next to the usage tab (at the bottom) 

EXPECTED:
The class should open in the main tab view (as it always was) next to all the other open tabs (at the top
Comment 1 Exilor 2016-01-04 18:52:02 UTC
Created attachment 157992 [details]
IDE log
Comment 2 Jiri Prox 2016-01-14 07:52:27 UTC
Can you please attach screenshot of the windows layout?

Did you re-arrange the windows?

You can also try calling Reset Windows from the Window main menu and see if it helps.

Thanks
Comment 3 hefest 2016-10-27 09:56:06 UTC
I can confirm Exilor's report. I did not rearrange the window layout. Installed 8.2, imported settings from 8.1, opened an existing Maven project, opened a Java class, selected a method, looked for it's usages, the list of matches appeared in a view below (as expected), but then when clicking on a line in the list of matches, the class containing the match opens in a tab next to the "Usages" tab, instead of a tab in the main code view above.
Comment 4 hefest 2017-02-27 14:11:30 UTC
What does "resolved/incomplete" mean? Is a fix scheduled to be available for NB 8.2? Is it going to have to wait for 8.3/9.0?

Can anyone suggest a workaround? I get the feeling something's misconfigured in the platform virtual filesystem: would be nice if one could manually patch it up it until a proper fix is released...in the meantime, not sure how to make use of 8.2. :\