Since the existing thread was too old, https://www.b4x.com/android/forum/threads/number-of-code-lines-in-quck-search-window.105745/#content
I started a new one.
We need to know the line# in the Quick Search results in order to determine if the found lines are clustered together or not. Otherwise we have to keep clicking on the next line in the Quick Search pane until we jump to the next group of lines that reference our search string. This becomes a bit tedious if the search string appears throughout the module.
If you can't or are unable to display a separate column for the line# in the Quick Search results, then perhaps you could put the line# in the hint message (yellow flyover hint)? So it would say "Main 342" instead of just "Main". This will at least give us some idea of the next group of lines that has our search value without us having to click on every entry in Quick Search. It won't be as fast as having a 2nd column of line#'s, but it will still save us some time.
TIA
I started a new one.
We need to know the line# in the Quick Search results in order to determine if the found lines are clustered together or not. Otherwise we have to keep clicking on the next line in the Quick Search pane until we jump to the next group of lines that reference our search string. This becomes a bit tedious if the search string appears throughout the module.
If you can't or are unable to display a separate column for the line# in the Quick Search results, then perhaps you could put the line# in the hint message (yellow flyover hint)? So it would say "Main 342" instead of just "Main". This will at least give us some idea of the next group of lines that has our search value without us having to click on every entry in Quick Search. It won't be as fast as having a 2nd column of line#'s, but it will still save us some time.
TIA