First, thanks for congratulations !
The GUI looks pretty broken
It's true I systematically use C::B in maximised mode; I'll try to find how to add scroll bars (does not seem too difficult) but more space will be wasted whereas they appear because of the few available space...
There no miracle but 50'' screen
I guess it's enough activating and switching to the panel when clicking on that menu entry.
Yes, I'll add another menu entry in the Search menu with the same event ID as in the view menu.
Is this what you mean ?
Why not opening a "big" (usual) editor instead (I guess you have reasons for that)?
Yes, I have
In fact, when I read code, I often search for items but leaving my current position to switch to another place in the same file bores me a lot : where was I in this wonderful 20000 lines file I got back :evil:
Another thing, I often need to browse method calls to see how it works and the use context. But I want to keep the editor I am working on in the same state. In this case, I either change Messages notebook size or I play (a lot) with F2 to switch Messages notebook visibility : far more efficient !
Note that single click on a result line previews the code whereas
double click opens a "big" (usual) editorIf you enable the "dir items" things get worse for me. I usually keep the message panel quite small and then it looks like the other screenshot attached. I'm not sure how to handle this any better...
I was aware of this problem, that's why there is the 'Hid dir items' button. Data are managed but you spare one line of controls space. You do not need to display dirs items to perform search in directories.
Dje