BUG: Setting preferred Bible fails

Don Awalt

Here is what I did -

1. My default Bible is RSVCE. I did look up to set preferred bible to LEB. All works fine.

2. Later, I went back to click the circle next to RSVCE, which is not second. It doesn't take, keeps LEB selected.

3. I try clicking more, and typing RSVCE, and clicking on that - it stays on LEB

4, I try clicking the Bible that is #3 in my list in the Home page panel, and that fails to.

Can only change preferred Bible once it seems.

Find more posts tagged with

Comments

Don Awalt

Restarting Logos does not fix the problem - I can't change my preferred Bible now.

Don Awalt

https://community.logos.com/discussion/comment/499526#Comment_499526

It seems that if I restart Logos, I can change the preferred Bible ONCE, to something I have never selected before. But I can never go back to a Bible I have previously selected.

Rich DeRuiter

https://community.logos.com/discussion/comment/499527#Comment_499527

It seems that if I restart Logos, I can change the preferred Bible ONCE, to something I have never selected before. But I can never go back to a Bible I have previously selected.

I'm not sure I follow how you are setting your default Bible. Are you doing that through the home page or some other way? If some other way, provide specific steps. How are you looking up? How do you then set the Bible as your preferred, etc.

You may also want to check your prioritization list and make sure that your preferred Bible is the top Bible on that list as well.

Keep Smiling 4 Jesus :)

Can only change preferred Bible once it seems.

Wonder if can use Library Prioritize ? Preferred Bible is the highest prioritized.

Wiki has => http://wiki.logos.com/Prioritizing

Keep Smiling [:)]

Don Awalt

https://community.logos.com/discussion/comment/499548#Comment_499548

I can use Prioritize Bible of course, but that misses the point and was not the topic of the bug report - the Home Page capability is not working. I am doing it here, see picture, it has radio buttons to select a preferred bible, and a search capability to find a new Bible to prioritize. The intent is to set preferred Bible here, no?

Jack Caviness

https://community.logos.com/discussion/comment/499549#Comment_499549

the Home Page capability is not working. I am doing it here

Made several changes between 3 Bibles without incident. Was able to change ESV to NKJV and back several times. 5.1 RC-2 Mac OS 10.8.4

Rich DeRuiter

https://community.logos.com/discussion/comment/499549#Comment_499549

I can use Prioritize Bible of course, but that misses the point and was not the topic of the bug report - the Home Page capability is not working. I am doing it here, see picture, it has radio buttons to select a preferred bible, and a search capability to find a new Bible to prioritize. The intent is to set preferred Bible here, no?

Yes it is.

Steps I'm following:

Select Bible from list
Press ENTER to set the new Bible as the preferred Preferred Bible

Results:

List is updated on the home page.
New Bible is prioritized in the Library.

Is that what you're seeing?

If not, explain what you are seeing.

Also you are putting this on the beta channel. Confirm you on 5.1RC2 (5.1.0.0938).

Don Awalt

https://community.logos.com/discussion/comment/499596#Comment_499596

Yes I am on 5.1 RC-2. I am doing what you outlined. Here is what I have found with more experimentation, but I don't have a pattern yet; first, I noticed that if you are trying to change to different BIbles (as I was in this testing), it creates havoc in your priority list. Now I Have about 6 Bibles with advanced prioritization set in my list BEFORE my generic priority Bibles, not sure if that matters. Anyway, it sticks new Bibles in random places near the beginning of the Priority list. What I have found though is, when I do what you say, it works with some Bibles, not with others. Some might be Bibles I had in my priority list as a general (not advance) priority, some not.

Like I said, I can't narrow it down to something repeatable. But at least with my install, if you try adding enough different Bibles through the Home Page you will find it does not work. I just happened to stumble upon it the first time I tried to use it, hence the bug report.

Rich DeRuiter

https://community.logos.com/discussion/comment/499608#Comment_499608

Now I Have about 6 Bibles with advanced prioritization set in my list BEFORE my generic priority Bibles, not sure if that matters.

That could be part of the problem, but I would have no way of knowing exactly what you mean by "advanced prioritization" and "generic priority." By default your Preferred Bible should be the first Bible to appear in the Prioritization list (regardless of whatever "advanced" or "generic" priority means to you).

Something else that doesn't seem to work (AFAIK), is to set a Personal Book as a Preferred Bible. Maybe that's changed, but if you're using a Bible compiled as a PB that could produce unintended consequences.

There may be something else going on here, though. I was cycling through some lexicons and after a while it would no longer work. The Parallel Resource list turned blank and there was nothing I could do that seemed to fix it. When I closed and reopened the lexicon everything appeared and worked as normal again (even cycling through the same word). This was not repeatable, and so I didn't report. However, if there is an issue of internal program data loss with RC2, it may do what you are finding, and what I experienced. I would have no idea how to confirm or disprove that possibility.

Rosie Perera

I've seen this bug before too. It was reported before, but Logos was never able to find steps to reproduce it so they closed the report. But it sounds like it's still lurking in there somewhere:

http://community.logos.com/forums/t/59001.aspx

Don Awalt

https://community.logos.com/discussion/comment/499619#Comment_499619

That could be part of the problem, but I would have no way of knowing exactly what you mean by "advanced prioritization" and "generic priority."

This is advanced prioritization:

These advanced prioritizations need to be first, before the generic. Otherwise the generic priorities will be used first, and these will never be used.

Generic priority is a word I made up, it's just NOT advanced prioritization entries in your priorities list.

Also - I use no PBs as Bibles.

Rich DeRuiter

https://community.logos.com/discussion/comment/499658#Comment_499658

These advanced prioritizations need to be first, before the generic. Otherwise the generic priorities will be used first, and these will never be used.

Generic priority is a word I made up, it's just NOT advanced prioritization entries in your priorities list.

Okay, I get it. That's not a feature I use, and didn't really play around with since it first came out.

I'm a little out of my league here, but I'm wondering what would happen if you prioritize a Bible above these that has priority limitations set on it. I don't really know, I'm just wondering.

The only other thing I'd suggest, if you haven't tried it already (and if no one has a better idea), is to shut down Logos (and everything else), clear your temp files, reboot your computer and see if that resolves it. If not, I'm at a loss.

fgh

https://community.logos.com/discussion/comment/499658#Comment_499658

These advanced prioritizations need to be first, before the generic. Otherwise the generic priorities will be used first, and these will never be used.

Which is exactly why you shouldn't change your preferred Bible from the home page. Doing so will put it above the advanced prioritizations. (And doing it more than once will mess up the order between your Bibles as well, if you care about that.)

(This, of course, doesn't change the fact that you seem to have encountered a bug.)

Don Awalt

https://community.logos.com/discussion/comment/499722#Comment_499722

You are right. And since it does not work reliably based on the Prioritization list, and it just doesn't work at all sometimes, I have turned it off from displaying on the Home page so I am not tempted to use it. This should really get fixed, it really is a broken feature.