BUG? No Morph Information shows for the NRSV when I hover over words

When I hover over words in my NRSV bible, I don't see any morphological information pop up on the bottom of the screen.

I opened my other top bibles and the morph info does pop up (ESV, NASB, NIV, NABRE).

This seems to just be a problem with the NRSV. I do get morph info in the context menu. But nothing pops up at the bottom of the screen when I hover over words.

Find more posts tagged with

Desktop App

Comments

MJ. Smith

It works for me on Verbum 8 PC. Is your indexing finished?

John Fidel

Go to the "interlinear icon" (see screenshot below) and uncheck "Reverse Interlinear". That should bring the hover over back. I think there is a case for this and it is being fixed.

Kiyah

When I hover over words in my NRSV bible, I don't see any morphological information pop up on the bottom of the screen.

I opened my other top bibles and the morph info does pop up (ESV, NASB, NIV, NABRE).

This seems to just be a problem with the NRSV. I do get morph info in the context menu. But nothing pops up at the bottom of the screen when I hover over words.

I think I figured it out. I had "Reverse Interlinear pane" box checked, although the pane wasn't displaying. Since but I guess since the box was checked it turned off the pop up morph info.

That's confusing. I can understand if the pane was displayed, but it wasn't so the morph info still should pop up if the pane is not showing. That needs to be addressed, because now I have to take an extra step to make sure that box is unchecked so that I can see the morph info pop up.

The reverse interlinear situation has been needlessly complicated. It requires too many clicks, drop-down menus, and check-boxes to get the view you want. It was simpler before. You just had two buttons to toggle on and off.

Fewer clicks are always better that more clicks.

Kiyah

https://community.logos.com/discussion/comment/1004038#Comment_1004038

Thanks John.

I think I was in the process of typing while you were posting your response. I'm glad there is a ticket for this.