Set Prioritzation Limits Advanced
I'm trying to make this work but so far seem to be missing something as its not working the way I understood it would.
I've have priorities set as per below. When I click on a greek word in LXX SESB I would expect Lust to open, instead BDAG opens. What am I doing wrong ?
Comments
-
Andrew, I'm pretty sure that there is an error in that book - reported elsewhere.
Try changing to the other LXX and test then
0 -
Andrew, I'm pretty sure that there is an error in that book - reported elsewhere.
Try changing to the other LXX and test then
Ok,, changed to LXX, Morphologically Tagged Edition (not the Logos Morph one) and it crashed the system when I double clicked on a greek word in order to execute the keylink.....log files attached.
0 -
Andrew, I'm pretty sure that there is an error in that book - reported elsewhere.
Try changing to the other LXX and test then
Ok,, changed to LXX, Morphologically Tagged Edition (not the Logos Morph one) and it crashed the system when I double clicked on a greek word in order to execute the keylink.....log files attached.
Ok tried this time time with LXX Logos Morph and still same result BDAG opens instead of Lust. I think I'm out of LXX versions to try at this point.
0 -
Andrew, did you also the change your prioritised resources:
Sorry, I don't have the SESB LXX - was that from the latest SESB??? - I have the first two versions - never bother with the 3rd. So, I'm not sure why the keylinking didn't work with that - probably needs to be rebuilt for 4.0
The LXX, Morphologically Tagged Edition definitely has an error that causes crashes.
0 -
Andrew, did you also the change your prioritised resources:
Change in what way, what you have below is how I set it up
Sorry, I don't have the SESB LXX - was that from the latest SESB??? - I have the first two versions - never bother with the 3rd. So, I'm not sure why the keylinking didn't work with that - probably needs to be rebuilt for 4.0
Yes this came with 3.0.... I didn't have 1.0 or 2.0
0 -
Andrew,
My apologies. I was sure that I had got this working after Bob made a reference in another thread to limiting preferences by source.
It appears that this function doesn't work for the LXX - just tried it with the Vulgate and it seems to work OK. More playing ahead.
Damian
0 -
Andrew,
My apologies. I was sure that I had got this working after Bob made a reference in another thread to limiting preferences by source.
It appears that this function doesn't work for the LXX - just tried it with the Vulgate and it seems to work OK. More playing ahead.
Damian
No problem, thanks for trying... some more work to do indeed in learning 4.0
0 -
Ok I have tried this now with NASB dictionarie and NASB95 for Greek Strongs's Number. Since it has its own version of strongs numbering this is the the most logical combination keylink in this instance for this datatype.
However it does not work like the previous example I tried...From right click menu system defaults DBL to top priority for Strong's (this seems to be only way I can find this out - this needs to be addressed).
 AM.png)
Note NASB dictionary is third on list behind DBL and TDNT.
I have set up my keylinks as follows: (only a snapshot of list is shown as this is growing way too long to show full list)
.png)
This I believe forces the NASB dictionary to be opened when a Greek or Hebrew Strongs keylink is activated within the NASB95 resource. Otherwise I would expect the default of DBL to open in all other instances of strong's number keylinks.
However when I use the Open Stron'gs Greek from the right click menu in the top screen shot it does not open NASB disctionary, instead it opens the default DBL resource despite the efforts I have gone to setting up the prorities...
Logos can you please explain how this is suppossed to work. TIA
0 -
This I believe forces the NASB dictionary to be opened when a Greek or Hebrew Strongs keylink is activated within the NASB95 resource. Otherwise I would expect the default of DBL to open in all other instances of strong's number keylinks.
i cleaned out my list and refreshed it as per http://community.logos.com/forums/p/1252/10306.aspx#10306
then I added NASB Dict for Greek Strong's from any resource before DBL Greek in the list. I didn't add an entry for Hebrew Strong's. And it showed at #1 for Strong's as expected, but it also showed as #1 for the Lemma! There are still problems when we add to a working list!!
Dave
===Windows 11 & Android 13
0 -
Andrew, I'm pretty sure that there is an error in that book - reported elsewhere.
Try changing to the other LXX and test then
1780.Logos4logs.zip" target="_blank">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/67/1780.Logos4logs.zip:550:0]
Ok,, changed to LXX, Morphologically Tagged Edition (not the Logos Morph one) and it crashed the system when I double clicked on a greek word in order to execute the keylink.....log files attached.
Hi Andrew, please post crashes with reproduction steps as per the beta testing guidelines http://community.logos.com/forums/t/728.aspx thanks.
0 -
Andrew, I'm pretty sure that there is an error in that book - reported elsewhere.
Try changing to the other LXX and test then
1780.Logos4logs.zip">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/67/1780.Logos4logs.zip:550:0]
Ok,, changed to LXX, Morphologically Tagged Edition (not the Logos Morph one) and it crashed the system when I double clicked on a greek word in order to execute the keylink.....log files attached.
Hi Andrew, please post crashes with reproduction steps as per the beta testing guidelines http://community.logos.com/forums/t/728.aspx thanks.
George there was not crash, the feature just appears to be not working as I expected it to do. What I have posted above is the steps I took to try and set these up. I was looking for cofirmation from Logos as to whether or not I had understood this feature, whether or not I had set it up correctly and whether or not it is actually working correctly in beta 1 or its a known issue that I have missed picking up on somewhere in one of the mutitude of threads. I have since reset all my priorities to explore other things with the beta but will take another look at this and post back here as to my results. In the meantime if you read this before I get to post back and can answer any of my questions in this thread that would be appreciated. (Your doing a great job, George [:D] , in case anyone has told you.)
0 -
This I believe forces the NASB dictionary to be opened when a Greek or Hebrew Strongs keylink is activated within the NASB95 resource. Otherwise I would expect the default of DBL to open in all other instances of strong's number keylinks.
i cleaned out my list and refreshed it as per http://community.logos.com/forums/p/1252/10306.aspx#10306
then I added NASB Dict for Greek Strong's from any resource before DBL Greek in the list. I didn't add an entry for Hebrew Strong's. And it showed at #1 for Strong's as expected, but it also showed as #1 for the Lemma! There are still problems when we add to a working list!!
I cleared out prioirities and tried:
.png)
As previously experienced this did not work. When working with Greek Strong's in NASB95, NASB dictionary was not used.
I then tried the following list which I think matches Dave's description. It didn't work either.
.png)
So at this point George I am still no the wiser as to what is going on here and really need confirmation from logos as to whether its my understanding/setup at issue or there is a bug, known or otherwise. There is still no crash to report. I had confidence in the reliablity of and ease of setting up keylinks in 3.0 (even with its limitations).. at this point I am far from getting closer to that feeling with 4.0 and my confidence in being able to set this up is degrading each time I try to use this new system.
0 -
Thanks for posting such detailed testing scenarios with screenshots. It's very helpful for us.
Sorry there hasn't been much response to this topic so far; there has been a lot of noise regarding the new resource priority model. It's been hard to separate bug reports from design complaints.
Both are totally valid, but I'm only qualified to fix the bugs. :-)
... and [we] really need confirmation from logos as to whether its my understanding/setup at issue or there is a bug, known or otherwise.
As alluded to in the beta 2 release notes, there are [now] known issues with "From resource" limited priorities.
In Beta 2, links within resources and double-click keylinks should respect "From resource" priority limits.
Unfortunately, there are still some incorrect behaviors regarding "From resource" priorities (primarily involving context menus) that will have to wait until beta 3 to get resolved. Please do continue to post any unexpected behaviors.
... and my confidence in being able to set this up is degrading each time I try to use this new system.
Can we reset your confidence value for the new beta? :-)
Thanks for continued feedback and testing.
0 -
Thanks for posting such detailed testing scenarios with screenshots. It's very helpful for us.
Sorry there hasn't been much response to this topic so far; there has been a lot of noise regarding the new resource priority model. It's been hard to separate bug reports from design complaints.
Both are totally valid, but I'm only qualified to fix the bugs. :-)
Can we reset your confidence value for the new beta? :-)
Thanks for continued feedback and testing.
Thanks for the feeback Jacob...confindence levels reset...(after all it is a new beta version) [H] and I'll try this out again with beta 3 and the same scenarios above and report back how it went... the screen shots. The new system is sleek if you only want to set a couple of resources as prioritkes but is really messy when you want to start customizing a lot of settings.
0 -
Thanks for posting such detailed testing scenarios with screenshots. It's very helpful for us.
Sorry there hasn't been much response to this topic so far; there has been a lot of noise regarding the new resource priority model. It's been hard to separate bug reports from design complaints.
Both are totally valid, but I'm only qualified to fix the bugs. :-)
... and [we] really need confirmation from logos as to whether its my understanding/setup at issue or there is a bug, known or otherwise.
As alluded to in the beta 2 release notes, there are [now] known issues with "From resource" limited priorities.
In Beta 2, links within resources and double-click keylinks should respect "From resource" priority limits.
Unfortunately, there are still some incorrect behaviors regarding "From resource" priorities (primarily involving context menus) that will have to wait until beta 3 to get resolved. Please do continue to post any unexpected behaviors.
... and my confidence in being able to set this up is degrading each time I try to use this new system.
Can we reset your confidence value for the new beta? :-)
Thanks for continued feedback and testing.
Jacob was going to try and look at this tonight but I'm having issues with indexer again. Details posted here and also here
For an examples of the difficulties with resource priority take a look at this post.
I will get onto this once I have some stability in my install. At the moment testing it while resouces are missing probably wouldn't be a fair test.
0 -
Jacob, I haven't forgotten about this, I really would like to get around to actually doing this but I stil trying to get things sorted out after the licensing server muck up the other day: http://community.logos.com/forums/p/1714/14628.aspx#14628
0
