Prioritizing Frustration

Page 1 of 1 (13 items)
This post has 12 Replies | 2 Followers

Posts 40
Travis Arnold | Forum Activity | Posted: Sat, Nov 28 2009 7:38 PM

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

Problem: From an interlinear, I wanted to click the Strong's number and open up "Enhanced Strong's Lexicon" (ESL). So I prioritized ESL above any other lexical resource. BUT... when I am in ESL, each entry has the corresponding TWOT number and GK number. I want to be able to click on the TWOT number and have it open TWOT. (Makes sense!) And I want to be able to click on the GK number and have it show me some other resource that I tell it to show me. But instead, clicking on the TWOT number gives me ESL because that's what I have set as the number one priority (and I want it to remain the number one priority). I can understand no longer being able to assign any resource I like to GK numbers. BUT shouldn't TWOT numbers always just open up to TWOT?? All I want is for Strong's numbers to always open ESL, TWOT number to always open TWOT and GK numbers to always open DBL. Can anyone help?

Posts 25600
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Nov 28 2009 8:26 PM

Hi Travis, this can be very frustrating even understanding the Advanced Options that will manage the data type a resource will respond to.

In your Prioritize list right click a resource and choose Set Prioritization.....(Advanced).

Click the little arrow on the first box "of this type"

ESL --> set to Greek Strong's

Then Prioritize another copy of Strong's, put it where you want in the list and:-

ESL --> set to Hebrew Strong's

This way it won't take GK, TWOT numbers away from their respective lexicons!

 

OHH! You've also got to stop DBL Hebrew taking TWOT nos.

DBL Hebrew --> set to Hebrew

 

So this should work if you Prioritize as follows:

ESL --> Greek Strong's

ESL --> Hebrew Strong's

DBL Hebrew --> Hebrew

TWOT

Dave
===

Windows 10 & Android 8

Posts 40
Travis Arnold | Forum Activity | Replied: Sat, Nov 28 2009 8:36 PM

That worked great, Dave... Thanks!

Posts 25600
Forum MVP
Dave Hooton | Forum Activity | Replied: Sat, Nov 28 2009 8:41 PM

Travis Arnold:

That worked great, Dave... Thanks!

Great!  But check out what I added as well!

Dave
===

Windows 10 & Android 8

Posts 40
Travis Arnold | Forum Activity | Replied: Sat, Nov 28 2009 8:52 PM

Oh.. OK. It worked fine anyway (with GK going to DBL automatically). But I will set it up like that anyhow. The "advanced prioritization limits" function is starting to make sense to me. Thanks!

Posts 40
Travis Arnold | Forum Activity | Replied: Sat, Nov 28 2009 10:31 PM

K... now, when in the OT, the Strong's numbers link to ESL. BUT IN THE NT, Strong's numbers link to WSNTDICT, even though I have set ESL as the priority for BOTH Hebrew Strongs and Greek strongs. I don't even have WSNTDICT prioritized at all. So then I set WSNDICT as a priority, making sure it was below ESL on the list... but still, WSNDICT takes the priority for Greek Strong's numbers. Do you know how I can fix this?

Posts 25600
Forum MVP
Dave Hooton | Forum Activity | Replied: Sun, Nov 29 2009 2:20 AM

What is WSNDICT? What does its Resource Information (the circled i when open) say under Indexes.

Try to Prioritize it for something other than Strong's, say Greek lang, making sure it was listed below all other Greek lexicons. If that fails we have a problem!

Dave
===

Windows 10 & Android 8

Posts 40
Travis Arnold | Forum Activity | Replied: Sun, Nov 29 2009 3:03 PM

WSNDICT is "The Complete Word Study Dictionary, New Testament". Under indexes, it says, "Greek Strong's Number" & "Greek headwords." I set it as the priority for "Greek" and made sure it was positioned under ESL (which is still set as the priority for both Hebrew & Greek Strong's numbers). But Greek Strong's numbers still open up to WSNDICT and not ESL no matter what I do. So I have ESL as priority for Hebrew and Greek Strong's numbers; DBL is set up for Hebrew and Greek GK numbers; TWOT is set up as priority for TWOT numbers...... All of these priorities function correctly, except for Greek Strong's numbers. Greek Strong's numbers have a mind of their own. The only way I can get both Hebrew & Greek Strong's numbers to go to ESL is to remove from the priority list any other lexical resource (TWOT, DBL, etc.) and make sure ESL is the only one prioritized (only 1 copy of ESL with no "apply only to" designations) and that WSNDICT is prioritized underneath it. But then I lose my ability to have TWOT numbers show TWOT and GK numbers show some other resource. I like the idea of how prioritization SHOULD work, but it just doesn't seem to work the way it was designed to. (I'm considering deleting WSNDICT from my library altogether to see if that helps.)

 

 

Posts 25600
Forum MVP
Dave Hooton | Forum Activity | Replied: Sun, Nov 29 2009 4:00 PM

Travis Arnold:
(I'm considering deleting WSNDICT from my library altogether to see if that helps.)

You need to Hide it for that to be effective (L4 will automatically restore anything that is missing/deleted). Open Program Settings and click the arrow on Hidden Resources at the bottom. Drag the title there and restart L4 to complete the process.

I still consider this to be a BUG in Prioritisation, but performing the above should confirm it.

I wouldn't prioritise for GK numbers as any keylinking is done with Greek or Hebrew Headwords. Also, it is unnecessary to restrict TWOT as it wasn't stealing keylinks from anything!

Try this:

ESL --> Greek Strong's

ESL --> Hebrew Strong's

DBL Greek --> Greek

DBL Hebrew --> Hebrew

TWOT

WSNDICT

Dave
===

Windows 10 & Android 8

Posts 40
Travis Arnold | Forum Activity | Replied: Sun, Nov 29 2009 4:42 PM

Dave Hooton:

You need to Hide it for that to be effective (L4 will automatically restore anything that is missing/deleted). Open Program Settings and click the arrow on Hidden Resources at the bottom. Drag the title there and restart L4 to complete the process.

I still consider this to be a BUG in Prioritisation, but performing the above should confirm it.

I wouldn't prioritise for GK numbers as any keylinking is done with Greek or Hebrew Headwords. Also, it is unnecessary to restrict TWOT as it wasn't stealing keylinks from anything!

Try this:

ESL --> Greek Strong's

ESL --> Hebrew Strong's

DBL Greek --> Greek

DBL Hebrew --> Hebrew

TWOT

WSNDICT

Hiding WSBDICT worked. The heavens opened up, a light shined down and a choir of angels sang. I did, however, have to restrict TWOT to TWOT numbers because it ended up stealing my Hebrew Strong's keylinks. But everything works! The only downside is that I DID like WSNDICT--I just didn't want it linking to my Strong's numbers. It would be nice to occasionally access WSNDICT, but for now the linking issue is more important to me... So until this "bug" is fixed, I'll just have to keep WSNDICT hidden.

Thanks again for your help!

Posts 418
Mary-Ellen | Forum Activity | Replied: Mon, Nov 30 2009 5:44 AM

First time through I thought this was a joke!  Everyone knows the forum is the place to go for "answers to tough questions"!  Wink

This feature gives me a lot to think about and tinker with.  I don't find the "advanced prioritize" feature documented?

 

Dell XPS 8930/Intel Core i7-8700@3.20GHz/32GB RAM/Win10 Pro

Trekstor Primebook/Celeron/4GB RAM/Win10 Home

iPad Air/Pixel/Faithlife Connect

Posts 25600
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Nov 30 2009 3:39 PM

Mary-EllenVian:

First time through I thought this was a joke!  Everyone knows the forum is the place to go for "answers to tough questions"!  Wink

This is the first time I saw it as a joke -  LOL!

And, yes, the documentation is sadly lacking.

Dave
===

Windows 10 & Android 8

Posts 526
Bobby Terhune | Forum Activity | Replied: Mon, Nov 30 2009 4:05 PM

By the way, Bob P mentioned that they are rebuilding the old ESL, so I don't know how that will affect things for the future. All new packages now ship with the complete strongs concordance instead of the ESL, Only those folks who had L3 and are upgrading will have to deal with L4 and the ESL. It will be interesting to see how the rebuilt resource will play with the tagging in the other lexicons.

Page 1 of 1 (13 items) | RSS