BUG? Literary Typing in 8.7 context menu
In the following example, one can see that when expanding "Literary Typing" in the context menu (this is based on John 10:34 NASB) instead of the more specific categories listed in the information pane when only gets "literary typing" repeated four times.
One can see what the literary type in question is in the right pane header after one clicks on one of the "literary typing" lines:
If this is by design, it is not a good choice because (1) it is far from obvious that this is how one should find what the specific literary type is (took me a bit to figure it out) and that goes counter to the more toward ease of use and (2) it is odd that it should be so when other left panel information categories are more specific and continue to be as they were in the former context menu.
Either way, it needs a fix imo.
Comments
-
Francis said:
If this is by design, it is not a good choice because (1) it is far from obvious that this is how one should find what the specific literary type is ... and (2) it is odd that it should be so when other left panel information categories are more specific
I agree. See this bug report for the 8.8 Beta.
Dave
===Windows 11 & Android 13
0 -
-
Francis said:
In the following example, one can see that when expanding "Literary Typing" in the context menu (this is based on John 10:34 NASB) instead of the more specific categories listed in the information pane when only gets "literary typing" repeated four times.
One can see what the literary type in question is in the right pane header after one clicks on one of the "literary typing" lines:
If this is by design, it is not a good choice because (1) it is far from obvious that this is how one should find what the specific literary type is (took me a bit to figure it out) and that goes counter to the more toward ease of use and (2) it is odd that it should be so when other left panel information categories are more specific and continue to be as they were in the former context menu.
Either way, it needs a fix imo.
This has been fixed in 8.8.
0
