8.4 beta 2: Bug with new prioritisation command

Mark Barnes
Member Posts: 15,432 ✭✭✭
There's a bug with the new prioritisation command which occurs when advanced prioritisation is used. To reproduce:
- Create an advanced prioritisation rule that applies from just one resource.
- Below this create a normal prioritisation for the same Bible.
- Make sure these rules are not at the top of the prioritisation list.
- Use the command bar to set preferred Bible to this version.
Result:
- The advanced prioritisation rule is moved to the top of the prioritisation list.
Expected result:
- The rule that applies to all resources will be added to the top of the prioritisation list BELOW any advanced prioritisation rules that apply only to selected resources.
- In other words, there are two issues:
- The wrong rule gets moved (it should be the rule that applies to all resources)
- It gets moved to the wrong place (if the top rules apply only to some resources, it should get added below that).
Why this matters:
- Many power-users (who this command is aimed at) use advanced prioritisation to ensure that cross-references within a Bible show the passage in the same translation as the source. Like this:
- As things stand, with this prioritisation, using the new command to prioritise the NKJV will have no real impact.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
Comments
-
Mark
Is this the same problem as flagged by Dave and confirmed by Philana at https://community.logos.com/forums/t/180274.aspx ?
Graham
0 -
Yes, it's the same issue. Thanks.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0