| Summary: | code search brings instant NPE when started on version 0.3.0.v20110831-1251-b552 | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Christian Campo <christian.campo> |
| Component: | Recommenders | Assignee: | Marcel Bruch <marcel.bruch> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Christian Campo
The most convenient way to use code-search is by triggering it directly from code completion inside your active editor. I couldn't recreate your error ( i triggered a query from active java editor before). Did you trigger a code-search before using the button? Anyways, Tobias will completely rework the code-search interface and views in the next weeks/months. Given that and the statement that the view is more a debug view than thought to be used by clients, I'd like to set this issue to WONT FIX and wait until Tobias comes up with a smarter UI in ~November. (In reply to comment #1) > The most convenient way to use code-search is by triggering it directly from > code completion inside your active editor. I couldn't recreate your error ( i > triggered a query from active java editor before). Did you trigger a > code-search before using the button? > > Anyways, Tobias will completely rework the code-search interface and views in > the next weeks/months. > > Given that and the statement that the view is more a debug view than thought to > be used by clients, I'd like to set this issue to WONT FIX and wait until > Tobias comes up with a smarter UI in ~November. thats ok for me…. |