8.4 beta 2: Bug with new prioritisation command

Page 1 of 1 (3 items)
This post has 2 Replies | 0 Followers

Posts 13343
Forum MVP
Mark Barnes | Forum Activity | Posted: Sat, Mar 23 2019 1:22 PM

There's a bug with the new prioritisation command which occurs when advanced prioritisation is used. To reproduce:

  1. Create an advanced prioritisation rule that applies from just one resource.
  2. Below this create a normal prioritisation for the same Bible.
  3. Make sure these rules are not at the top of the prioritisation list.
  4. 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:
    1. The wrong rule gets moved (it should be the rule that applies to all resources)
    2. 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.
Posts 21847
Forum MVP
Graham Criddle | Forum Activity | Replied: Sat, Mar 23 2019 3:10 PM

Mark

Is this the same problem as flagged by Dave and confirmed by Philana at https://community.logos.com/forums/t/180274.aspx ?

Graham

Posts 13343
Forum MVP
Mark Barnes | Forum Activity | Replied: Tue, Mar 26 2019 2:38 AM

Yes, it's the same issue. Thanks.

Page 1 of 1 (3 items) | RSS