Various issues reported in igorexchange.com #62
Description
From https://www.wavemetrics.com/comment/25778#comment-25778:
- It is possible to accidentally double-click the very top row of the list box, which returns a row of -1 and triggers an abort message. It may be better (less annoying) to just ignore such calls.
- If a function has no comment, then the tool tip just shows an empty box, which is confusing. Better show no tool tip in this case.
- constants show the standard list-box help text instead, which is also confusing.
- It would be better to have the contents of structures in multiple rows, especially if the structure contains many elements, which easily goes beyond any reasonable window size.
- The parser for structures seems to have some issues, which you can see, e.g., in the info for the WMResizeInfo structure of the code browser (two superfluous commas appear at the end).
- The 'jump to first letter via keyboard' function seems to work only occasionally. Often enough nothing happens (focus is somewhere else?)
It would also be nice to have the following conveniences:
- Sort and filter by type
- Find lines which uses the selected object within the code (e.g., via keyboard shortcut forward/backward search)
- Optionally offer a non-floating panel
- Offer options to select between different types of function-comments to display. For example, I have often comments on the same line as the function declaration (i.e., to the right of the code). Others might use the first lines below the function name.
- Offer option to filter certain characters from function comments before / after text, such as #, + *. If the comment is empty after filtering these characters, show no tooltip. This would also enable compatibility with Igor's own code marker comments.