The new command does not recognize Advanced Prioritization e.g.
Set Preferred Bible to NET does nothing, and ESV remains the preferred bible.
Set Preferred Bible to NLT promotes the Advanced Prioritization, which is OK (in this case).
The new command does not recognize Advanced Prioritization e.g. Set Preferred Bible to NET does nothing, and ESV remains the preferred bible. Set Preferred Bible to NLT promotes the Advanced Prioritization, which is OK (in this case).
Dave,
I'm not clear what you are expecting. Your screenshot shows the NET at the top of your list, is that not what you are expecting? When I run the command Set Preferred Bible to NET with Adavanced prioritization it moves to the top of my list.
What behavior do you expect?
What behavior are you observing?
If you construct a List like the one in the screenshot, you will see that ESV is the preferred bible. But I want NET (not ESV) to be used for references in the NET Bible Notes, which means the Advanced Prioritization for NET has to be above ESV! The new Set command does not recognise this subtlety, For NET to be #1 for all bible references, Set needs to move the normal entry (below CSB) to the top of the list.
NLT's advanced prioritization allows it to be used without restriction for Bible references.
I'm not clear what you are expecting. Your screenshot shows the NET at the top of your list, is that not what you are expecting? When I run the command Set Preferred Bible to NET with Adavanced prioritization it moves to the top of my list. If you construct a List like the one in the screenshot, you will see that ESV is the preferred bible. But I want NET (not ESV) to be used for references in the NET Bible Notes, which means the Advanced Prioritization for NET has to be above ESV! The new Set command does not recognise this subtlety, For NET to be #1 for all bible references, Set needs to move the normal entry (below CSB) to the top of the list. NLT's advanced prioritization allows it to be used without restriction for Bible references.
I see what you mean. I'll write up a case.
I didn't see Dave's bug report, and wrote my own - with some additional examples: 8.4 beta 2: Bug with new prioritisation command
