[resolved] BUG:'Link set' doesn't work

I'm really struggling to understand how Logos works... Or, in my case, why it doesn't.

I have a number of books open in various panes in the Logos window. Some of the panes have multiple tabs--one pane has Bibles, another commentaries, while a third has lexicons. ALL (yes, bold italic underline all caps!) the books are set to Link set: A. However, when I move in to a different reference in one book (e.g., a Bible, say from Gn. 27:1 to 27:9) the other books don't follow along. If I type a different reference in the reference box at the top of a tab, that doesn't work either.

What's the trick to get books to scroll together? And beyond that, how do you get Logos to scroll with other software that it should scroll with (e.g., Bible Society's ParaTExt)? I've been fighting this for months and, to be honest, it makes me not even want to open Logos...

Any help most appreciated. A somewhat frustrated,

Paul

Find more posts tagged with

Comments

Graham Criddle

Hi Paul

I have a number of books open in various panes in the Logos window. Some of the panes have multiple tabs--one pane has Bibles, another commentaries, while a third has lexicons

Please upload a screenshot - using the paperclip icon - showing your layout.

I have just tested this and it works fine so would like to understand whether it is a resource-specific issue.

Paul Unger

https://community.logos.com/discussion/comment/732584#Comment_732584

Here you go, Graham:

Thanks for taking the time to look at this,

Paul

Graham Criddle

https://community.logos.com/discussion/comment/732605#Comment_732605

Thanks Paul

With that layout I would expect those resources which have a Bible index to scroll together but the others won't

So I would expect NASB, NLT, USB and the NICOT volume to scroll - but the TWOT and NBD won't. (I don't know about "Exegetical Helps" - I don't have that resource and don't know how it is indexed)

Is that consistent with what you are seeing?

Graham

Paul Unger

https://community.logos.com/discussion/comment/732607#Comment_732607

Correct--I don't expect the lexicons to scroll with the other resources. But I do expect those arranged by 'verse' to ("Exegetical Helps" is and should follow along). Unfortunately, they don't...

I have started and stopped Logos a few times today. Each time it has 'updated resources' and 'indexed resources'. Each time I have waited for these tasks to complete before starting to work. And each time I 'move' in a resource (clicking or scrolling) or type a reference in the box, nothing else follows along. I have to move things manually (as you can see in the picture, one resource is at Gn. 27:1 and another is at Gn. 27:7). This is my normal.

To be fair, I should say that scrolling has worked in the past, but it has been very hit-&-miss. More 'miss' than 'hit,' I'm afraid... And as I said earlier, I'm trying to get it to scroll with my translation software (ParaTExt), but that's a complete 'miss'. :-(

If there was something I knew I was doing wrong, or could do to 'kickstart' linked scrolling, I'd give it a try. One thing I did try today was to set all resources to "Link set: None" and then all back to "Link set: A." It didn't help.

The only other thing I can think of is that I have Logos installed on two Android phones. I don't know how Logos manages my resources across platforms, but I do wonder if that affects scrolling (e.g., I just opened a Bible on my Win7 computer and it was at a reference that I'm pretty sure I had last looked up on one of my phones).

Paul

MJ. Smith

https://community.logos.com/discussion/comment/732620#Comment_732620

Using NLT and USB handbook I can replicate the problem. If I enter a reference in the reference box they scroll together; if I change focus to change the reference book content, they do not.

Paul Unger

https://community.logos.com/discussion/comment/732623#Comment_732623

There's some comfort in having this confirmed by someone else. Small comfort, but some. ;-) Thanks for sharing your experience, MJ Smith.

Reuben Helmuth

https://community.logos.com/discussion/comment/732627#Comment_732627

There's some comfort in having this confirmed by someone else. Small comfort, but some. ;-) Thanks for sharing your experience, MJ Smith.

I hope it comforts you more that it can work, as it does for me (see screencast). Perhaps other (Windows) users could specifically test with NLT and UBS Handbooks...

As far as linking ParaTExt, that is done in ParaTExt and not in Logos, I'd need to check what the menu item is...

Graham Criddle

https://community.logos.com/discussion/comment/732623#Comment_732623

Using NLT and USB handbook I can replicate the problem. If I enter a reference in the reference box they scroll together; if I change focus to change the reference book content, they do not.

MJ, what do you mean by "changing focus" here?

MJ. Smith

https://community.logos.com/discussion/comment/732737#Comment_732737

Using NLT and USB handbook I can replicate the problem. If I enter a reference in the reference box they scroll together; if I change focus to change the reference book content, they do not.

MJ, what do you mean by "changing focus" here?

Scrolling or clicking in the text that results in the contents of the reference box changing.

Reuben Helmuth

https://community.logos.com/discussion/comment/732623#Comment_732623

Using NLT and USB handbook I can replicate the problem

Oh, sorry, I was testing the UBS Handbook. I'll have to see if I can find the other one! [;)]

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/732749#Comment_732749

clicking in the text that results in the contents of the reference box changing

This is not considered "navigation", so it doesn't cause linked resources to follow.

MJ. Smith

https://community.logos.com/discussion/comment/732753#Comment_732753

clicking in the text that results in the contents of the reference box changing

This is not considered "navigation", so it doesn't cause linked resources to follow.

That's odd - it makes Lange's and NRSV scroll together. You must misunderstand what I'm doing.

Ah, or do you mean that clicking alone in the same page isn't navigation ... it may be the start of selection

Paul Unger

https://community.logos.com/discussion/comment/732720#Comment_732720

As far as linking ParaTExt, that is done in ParaTExt and not in Logos, I'd need to check what the menu item is...

The menu item in ParaTExt is Tools > Scroll Scripture with any compatible applications. I have this checked.

Paul Unger

https://community.logos.com/discussion/comment/732753#Comment_732753

Hi Bradley,

Maybe you could clarify what is considered navigation? And point me to a reference? I searched Help, but couldn't find anything definitive; and at this point, something definitive would be very helpful...

Thanks,

Paul

Paul Unger

https://community.logos.com/discussion/comment/732720#Comment_732720

Thanks for the screencast, Reuben. While I will agree that the scrolling is close, it is not bang on... For example, there's a brief pause in your scrolling at 0:04, when NLT--the 'leading' resource--is at Gn. 13:1 (in the reference bar), and at that point all the other resources are still at Gn. 12:19. That's two verses off. Even that would be an improvement over my experience, though--my other resources don't move at all...

Dave Hooton

https://community.logos.com/discussion/comment/732828#Comment_732828

Maybe you could clarify what is considered navigation? And point me to a reference? I searched Help, but couldn't find anything definitive

FL isn't renowned for documentation but past threads have made it clear that the software doesn't regard clicking in the text as "navigation" because that could be accidental or it could be the start point for selecting text. Therefore navigation is effected by scrolling the text or manually changing the reference.

You may notice, after scrolling to Jn 4:48 then clicking in Jn 5:10 and selecting text, that the reference remains at Jn 5:10 whilst scrolling that book, but the reference in the text at the top of the page shows that both books are scrolling together!

Paul Unger

https://community.logos.com/discussion/comment/734770#Comment_734770

Maybe you could clarify what is considered navigation? And point me to a reference? I searched Help, but couldn't find anything definitive

FL isn't renowned for documentation but past threads have made it clear that the software doesn't regard clicking in the text as "navigation" because that could be accidental or it could be the start point for selecting text. Therefore navigation is effected by scrolling the text or manually changing the reference.

Thanks for the reply, Dave. Sadly, I'm learning the deficiency of FL's documentation... And I don't spend much time here looking for answers--searching the forum hasn't really scratched me where I have itched (I guess I use different search terms from 'past threads'...)

The trouble with scrolling is that there are many times when scrolling gets 1/2 a verse beyond the top of the window, but the commentary that is 'linked' (and has more text to display than the verse it is commenting on) won't advance until I scroll to the next verse, and then everything is out of whack... I'd like to look at the verse and its commentary at the same time. A 'click' would be much more definitive than scrolling. Even to have the option to 'click to a reference' would be great for those who don't tend to click by accident. The other option--typing the reference in the reference box every time--would be painful.

BUT EVEN BETTER THAN ANYTHING would be if Logos would just scroll its 'link sets' in relation to my other Bible software! Then I could click to a reference in that program and not worry about Logos's quirks. Unfortunately, it still doesn't follow along... Advice still welcome on that!

Reuben Helmuth

https://community.logos.com/discussion/comment/732830#Comment_732830

Even that would be an improvement over my experience, though--my other resources don't move at all...

Paul, is this still true? If so, there's definitely something wrong... If it's feasible from where you're at, I'd recommend calling tech support and having them connect to your computer remotely to diagnose/fix the issue.

Paul Unger

https://community.logos.com/discussion/comment/735327#Comment_735327

Paul, is this still true? If so, there's definitely something wrong... If it's feasible from where you're at, I'd recommend calling tech support and having them connect to your computer remotely to diagnose/fix the issue.

It's mostly still true, Reuben. When I began this thread (3 June) the resources in Logos would not follow a Bible being scrolled at all (despite all being set to Link Set A), nor would my translation software program (UBS/SIL's ParaTExt). In the time since then there have been a few major updates to Logos that have been downloaded and scrolling within Logos works--kind of...

If I scroll a Bible slowly, the linked commentaries follow along. If I scroll quickly (using the wheel on my mouse to check something in a reference in the passage some distance away), all bets are off. So right now my Bibles (two of them on separate tabs in one 'pane' of the Logos window), and commentaries (three of them on separate tabs in another 'pane' of the Logos window), and 'Text Comparison' (five more Bibles in another 'pane') are at Gn. 29:33. A quick scroll finds my Bibles (including 'Text Comparison' Bibles) at Gn. 29:22 but my commentaries at Gn. 29:32--the commentaries just can't keep up... If I scroll my Bibles slowly now, the commentaries jump to join the Bibles at Gn. 29:23. The quick scroll doesn't have to be more than ten verses away, as in this example--it can be just two--but if it's quick, the commentaries get lost...

As for Logos interacting with ParaTExt, there are no signs of life there... ParaTExt is equipped to "Scroll Scripture with any compatible resources" (which I have selected) and to "Access Logos Resources". Neither of these work. When I click "Access Logos Resources," an Access to Logos Resources window opens (as expected), however, clicking Launch (to open a selected resource) tells me that it was, "Unable to launch Logos." If I go to the All Resources tab and select a Logos resource in the left pane I get the message, "The Logos COM API is not registered with Windows. Paratext is unable to access any Logos resources."

The temptation to quit using Logos is mounting... There are other alternatives.

Reuben Helmuth

https://community.logos.com/discussion/comment/735372#Comment_735372

The temptation to quit using Logos is mounting... There are other alternatives.

I'm really sorry! I do know that others consider there to be alternatives, but IMHO these really aren't true alternatives. Since you have ParaTExt, you very likely already have TW 5 as well, but TW is also available in Logos format (which you may be aware of) so for the price of the TW license you'll get access to +$7,000 worth of materials, seamlessly integrated with your other Logos resources! To me this is simply a no-brainer deal!! If you call Logos (800-875-6467) and get technical support (probably you'll be routed through customer service), you'll find that they're extremely helpful. There's been only one occasion in which I was involved that they couldn't fix (it was a windows registry problem that required Microsoft intervention).

Bradley, could you have Mike or one of the other tech support team reach out to Paul?

Paul Unger

https://community.logos.com/discussion/comment/735378#Comment_735378

TW is also available in Logos format (which you may be aware of) so for the price of the TW license you'll get access to +$7,000 worth of materials, seamlessly integrated with your other Logos resources!

It's the TW package that I'm using (and a return to TW Folio that I would consider the alternative). "Seamless integration" would be really cool! There's someone at SIL looking for a solution (there are a few of us facing the same problem...) We'll see what they can come up with.

Reuben Helmuth

https://community.logos.com/discussion/comment/735380#Comment_735380

It's the TW package that I'm using (and a return to TW Folio that I would consider the alternative). "Seamless integration" would be really cool! There's someone at SIL looking for a solution (there are a few of us facing the same problem...) We'll see what they can come up with.

As far as ParaTExt & Logos not talking to each other...I wouldn't be surprised if it's an issue with ParaTExt still trying to talk to L5 instead of L6 (assuming you're running L6). FWIW I have the TW Logos edition and my only complaint is that the resources weren't developed to the same standards as normal Logos editions (e.g. more missing links, etc.).

Paul Unger

https://community.logos.com/discussion/comment/735455#Comment_735455

As far as ParaTExt & Logos not talking to each other...I wouldn't be surprised if it's an issue with ParaTExt still trying to talk to L5 instead of L6 (assuming you're running L6). FWIW I have the TW Logos edition and my only complaint is that the resources weren't developed to the same standards as normal Logos editions (e.g. more missing links, etc.).

Actually, it looks like an L4 dll that wasn't being registered properly...I started with L6, so that may have something to do with it. Someone at SIL has written a script that calls RegSvr32.exe to register the Logos Smart Tags dll, L4SmrtTg.dll. He said, "The problem seems to involve the Logos COM API being registered improperly." Anyway, I ran his script and I'm happy to say: IT WORKS!

[Is there a way to mark threads as 'Solved'?]

Dave Hooton

https://community.logos.com/discussion/comment/735488#Comment_735488

Actually, it looks like an L4 dll that wasn't being registered properly..

See this thread for the history.

Reuben Helmuth

https://community.logos.com/discussion/comment/735488#Comment_735488

I ran his script and I'm happy to say: IT WORKS!

SUPER!

Someone at SIL has written a script that calls RegSvr32.exe to register the Logos Smart Tags dll, L4SmrtTg.dll.

Would you mind sharing the script so that other with the same problem can use it?

Thanks!

Dave Hooton

https://community.logos.com/discussion/comment/735565#Comment_735565

Would you mind sharing the script so that other with the same problem can use it?

Reuben

Faithlife have provided a PowerShell script for this.