You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I always felt a bit unsatisfied about how the search results displayed when the node text is long. I never knew why. For some reason, I always need to navigate to the node in order to check if it really is what I'm looking for. Even making the Jumper window giant and the font size tiny isn't enough for me to "see" the results.
Now, I stopped to understand the situation, and concluded that it's because of how the truncation works.
For example, searching for BBB in this situation:
Results in:
Notice that:
-For BBB2: the truncation favors the text to the right side of the word BBB2. To me, this creates problems, because there is not enough text before the word BBB2 for me to get the context, and so understand the result (i.e., in order to understand which node actually is this). I think that, if the result was in the middle, it would be more useful.
-for BBB3: the truncation doesn't take full advantage of the space available for displaying the result (I give a lot of screen real estate to Jumper, so I want Jumper to actually use it)
An idea, that may help with the problem described here, is having a tooltip to show the content of the node when the mouse hover over the search results. The MapInsight Add-On, for example, has a tooltip that is very useful to show lengthy nodes (see it working at 12:55 in this video)
Center the highlighted text result every time it's possible => both for BBB2 & BBB3 use cases
Adding tooltip sounds nice but I raised 2 warnings:
there should be an option to enable / disable tooltip (no "breaking change" for current users)
maybe the delay before tooltip is displayed should be "customizable" ; because I assume you want the tooltip to automatically occur when result is selected (ie when moving up / down from 1 result to an other one)
I always felt a bit unsatisfied about how the search results displayed when the node text is long. I never knew why. For some reason, I always need to navigate to the node in order to check if it really is what I'm looking for. Even making the Jumper window giant and the font size tiny isn't enough for me to "see" the results.
Now, I stopped to understand the situation, and concluded that it's because of how the truncation works.
For example, searching for BBB in this situation:
Results in:
Notice that:
-For BBB2: the truncation favors the text to the right side of the word BBB2. To me, this creates problems, because there is not enough text before the word BBB2 for me to get the context, and so understand the result (i.e., in order to understand which node actually is this). I think that, if the result was in the middle, it would be more useful.
-for BBB3: the truncation doesn't take full advantage of the space available for displaying the result (I give a lot of screen real estate to Jumper, so I want Jumper to actually use it)
Thanks,
Map used in the example:
EXAMPLE BBB.zip
The text was updated successfully, but these errors were encountered: