I didn't see anything like this in the reported bugs, but perhaps I didn't search for the right thing.
I like the debugger watch windows that pop up in the editor...especially the ones for complex objects. However, they often don't go away and right now I have one that is sticking around even after the debugger session is ended.
Changing tabs, maximizing tabs, ... nothing will get it to leave except restarting netbeans.
This is a show stopper bug as far as I am concerned.
It seems to happen when I advance the debugger when the temporary watch window is up. Once this happens, basically nothing will bring it down.
Clicking into the Editor area in the tab where the extended tooltip was originally opened closes that tooltip. Clicking into a different editor tab does not close it.
I confirmed that clicking the editor in the correct location closes the window.
I would, however, contend that this is insufficient. It is common for the debugger to enter other files when stepping through things. Once the editor switches context the window is essentially locked in place.
I believe others will experience this problem as well and, like me, have to resort to restarting netbeans to get rid of it (until they are told how to).
When I wanted to close it, the first think I tried was clicking in the editor and then I tried to use ESCAPE. These seemed like the most natural things to try and so I would recommend these as possible solutions.
I am not sure why it was designed to stay up unless the editor was clicked at a certain location, but I am guessing this was on purpose. If those reasons are still valid, then maybe this part of the design should stay. However, I think ESCAPE should close the window always.
I'm looking into this.
I'm leaving this as P2 (no showstopper for 6.9) and nominating it as a 6.9.1_CANDIDATE. Also CCing QE to make sure that this is ok to leave for 6.9.1.
I am sure there are lots of pressures on the people deciding the release schedule, but I think this is big deal and waiting for a patch release is not appropriate.
Two out of the first 3 times I used the feature I had to restart my IDE to continue my work. The stalwarts are going to just be annoyed, but a new user evaluating the NB debugger would probably quit right there.
(In reply to comment #5)
> Two out of the first 3 times I used the feature I had to restart my IDE to
> continue my work.
Does closing all editors help? It should I would say.
Closing the tab that originally launched the window closes it. Now that I know what caused the problem I know how to resolve it. Others will not know this trick, although they may guess better that I.
The first day I used 6.9, this happened to me twice. The quickest solution I could think of at the time (with the highest likelihood of success) was to just restart. Later, I reproduced again and then reported it.
So, the questions are:
* How likely is this going to be hit
* When it does, how frustrating will it be (can a simple workaround be guessed)
* What will fixing this due to the other factors that the team is considering.
Tough choices, I know...
Integrated into 'main-golden', will be available in build *201006050001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Vita Stejskal <email@example.com>
Log: #187107: close a tooltip when its editor is closed
V. NetBeans IDE 6.9 (Build 201006041701)
Transplanted to release691 as 9a0fa9ad5e28
Verified in NetBeans IDE 6.9.1 Dev (Build 201007062301).