How do I highlight all the Bible headings
I would like to change the color of the Bible headings in the text of each bible so they stand out and add a little color to my reading. Is there a way to globally change the color of these headings?
Comments
-
A Visual Filter will do the job, as Bibles seem to have a search field called "Heading text". But the wildcard search is inefficient and will really slow down Logos 4 or have side effects (Windows Explorer crashed whilst running it on one bible).
Dave
===Windows 11 & Android 13
0 -
Hi Tim
It is theoretically possible - but I don't think it is practical at the moment.
If you do a Basic Search and constrain the Search Fields to "Heading Text" on a Bible you will only get hits against these headings.
You can then apply a Visual Filter to the search results and they will be highlighted.
The problem is that to get all of the headings you would need to do a wildcard search which would be prohibitively slow to do and to construct a filter from.
So, until / unless we get much faster wildcard searching I don't see a practical way to do this.
Graham
Edit: Sorry, Dave posted while I was composing my reply!
0 -
Dave, Graham ... I wonder why the wildcard search is so slow? On my software, I have various types of search algorithms, but even the one which is simply a hard text search on a net book of the Bible isn't that bad. I suppose if I were search all my Bibles that might be a little slow though certainly not threaten memory allocation. Only way it seems it could be that slow is how the data is stored (knowing Bob is a search guru).
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
I was able to do a wildcard search for headings in all my english bibles. It took 20-30 min if I interpret the info correctly (I was out while the computer did the work). I then created a filter as seen in the screenshot. My computer shows Logos using 50% of the processor doing something? I'm assuming building the filter. Have I done everything correctly from what you can see? If so then I guess I just have to wait and see if it actually does build the filter (built it about 5 minutes ago). Currently it does not show up when I click on the filter button in a bible.
0 -
Tim Engwer said:
I was able to do a wildcard search for headings in all my english bibles. It took 20-30 min if I interpret the info correctly (I was out while the computer did the work). I then created a filter as seen in the screenshot. My computer shows Logos using 50% of the processor doing something? I'm assuming building the filter. Have I done everything correctly from what you can see? If so then I guess I just have to wait and see if it actually does build the filter (built it about 5 minutes ago). Currently it does not show up when I click on the filter button in a bible.
Forgot the screenshot:
0 -
Hi Tim
That looks about right.
However, I think the issue you are going to find is that the VF will need to be regenerated every time you start Logos - it needs to do the search again - so it will incur a significant delay (you will see how long the delay is when the VF comes available) whenever you restart.
I think this is how it works - if not, I am sure someone will correct me!
Graham
0 -
-
Hi Tim
Tim Engwer said:It worked! But since I chose a foreground color for the highlight shouldn't it have just highlighted the text? I did just want the text itself to change color
Well done!
So is the issue that the "Chapter line" is highlighted as well or is there another problem?
Graham
0 -
Yes there is a delay as I restarted and it is processing right now. It was pretty cool though. I could change the style, color, etc. and created a custom heading style and could change it on the fly with no delay. But when you restart you have to wait to use the VF as you said. I am still waiting so we'll see if it works on restart. I'll let you know. But this opens the possiblity of custom styling parts of your books globally if the Logos team is able to make this a little more practical in terms of speed. Although on my computer with an i7 processor it only took about 20 minutes with one IE crash.
0 -
The time it would be sped up if you run it on 1 Bible rather than all of the English Bibles.
0 -
I wanted just the text itself and not the area around the text colored. I have restarted and as you surmised waiting for the VF to be rebuilt and then I will do some more experimenting.
0 -
Hi Tim
Tim Engwer said:I wanted just the text itself and not the area around the text colored
I think you still have the search pane open - this is what is causing the background colour.
Try closing that.
It was confusing in that the colour generated by the search window was the same as you used for the foreground colour!
Graham
0 -
Tim Engwer said:
I wanted just the text itself and not the area around the text colored. I have restarted and as you surmised waiting for the VF to be rebuilt and then I will do some more experimenting.
The area around the text may show highlighting because of the search. Close the search and it should disappear.
Edit: Graham thought faster than me. So I will just say Merry Christmas so my post isn't wasted.
"For the kingdom of God does not consist in words but in power"
Wiki Table of Contents0 -
Tim Engwer said:
But this opens the possiblity of custom styling parts of your books globally if the Logos team is able to make this a little more practical in terms of speed
True - but this does work it the moment if what you are interested in can be done with a non-wildcard search. So if, for example, you wanted to do something against all verbs then you are fine.
Graham
0 -
Denise Barnhart said:
Dave, Graham ... I wonder why the wildcard search is so slow?
Logos had problems with pure wildcard searches in Logos 3 and I'm very surprised they did not improve its performance in L4 e.g. looking for * in Highlighting or search fields. A special case could easily be made for those searches.
Note that a search like a* is fairly fast, so we have derived workarounds based on that. If morph data is present there are workarounds based on parts of speech e.g. @V, @N, @J etc.
Dave
===Windows 11 & Android 13
0 -
Graham Criddle said:Tim Engwer said:
But this opens the possiblity of custom styling parts of your books globally if the Logos team is able to make this a little more practical in terms of speed
True - but this does work it the moment if what you are interested in can be done with a non-wildcard search. So if, for example, you wanted to do something against all verbs then you are fine.
Graham
Yes. I just got back and let the computer do its thing (not sure how long it took but it was less than an hour) and the filter is working perfectly. I can change the color and characteristics instanly once the VF is loaded! So as you say I can make other global changes if desired! If the time lag is a factor of a search needing to be done by the VF in the background each time I load it then I'm wondering if there is a way to for the Logos team to code it so that L4 stores the information from the search so that the Visual Filter can be brought up almost instantly no matter how complex. How about it Logos? Would this be possible??
BTW I removed the filter and then reapplied it and it is rebuilding the VF again so there is a lag when you first start the program as well as when you remove and reapply a complex VF. I would think that storing the info from the search would solve the lag problem and make all VFs much quicker.
0 -
Philana Crouch said:
The time it would be sped up if you run it on 1 Bible rather than all of the English Bibles.
This is a good idea and I will try creating a filter for just my top bibles individually and see how this does for time. When I first started this experiment I tried just doing a search in the NIV for headings and it only took a few minutes.
0 -
I thought so, partially because some of the headings can be pretty long, when you add that to all English Bibles it could take awhile. I wonder are headings indexed, could that affect the speed?
0 -
Tim Engwer said:
I would think that storing the info from the search would solve the lag problem and make all VFs much quicker.
but what happens when new resources are added? This would require the search to be redone and I am sure there are other things that would require this.
Graham
0 -
Philana Crouch said:
I wonder are headings indexed, could that affect the speed?
All resource text is indexed, including text that is tagged as a Search Field (e.g. Heading Text). By definition, a search for Heading Text is restricted to text in that field and all other text is ignored e.g. a Bible Search only looks for results in Bible Text and ignores pericope headings, footnotes, etc (you get the same results with a Basic Search on Bible Text).
Dave
===Windows 11 & Android 13
0 -
Graham Criddle said:Tim Engwer said:
I would think that storing the info from the search would solve the lag problem and make all VFs much quicker.
but what happens when new resources are added? This would require the search to be redone and I am sure there are other things that would require this.
Graham
I hadn't thought of that but I suppose the search would only need to be done when the resources change and L4 could probably be made to do the new search only when new resources have been added that are related to the Visual Filter. I created a filter for 6 of my bibles individually and it takes about 7-10 minutes to load the filter so it works. Now I can style them individually. I am experimenting with the bible text next to have different colors for different bibles. This is what I have for the headings in NLT:
0 -
Thanks, Dave (wildcard searches).
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Hi Tim
Looks like you are doing really useful things with this - glad it is giving you what you wanted.
Tim Engwer said:I hadn't thought of that but I suppose the search would only need to be done when the resources change and L4 could probably be made to do the new search only when new resources have been added that are related to the Visual Filter.
The more I think about this the more I don't see it happening - but we would need Logos to comment definitively.
For example, if the Visual Filter were constructed on a search using collections then it would need to update itself every time a collection was changed as well.
It could just get very complex!!
Graham
0 -
Well I've experimented with the visual filters to change the appearence of the text and headings in certain resources and it seems that when I create more than 2 or 3 of these VFs and they have fully loaded, when I start to use L4 it soon gets overwhelmed and crashes. The resource texts look great with these filters but, alas, it seems L4 is not able to keep up with the filter. I was able to cut the load time in half by using the search filter "a*,b*,c*,d*,e*,f*,g*,h*,i*,j*,k*,l*,m*,n*,o*,p*,q*,r*,s*,t*,u*,v*,w*,x*,y*,z*" but this didn't keep L4 from crashing.
I am enclosing the crash log. If I interpret it correctly it seems that L4 runs out of memory each time it crashes per the line "Error detail: OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown." I have 6GB of ram but I believe L4 can only use 2GB of this. So I don't suppose adding more ram would enable L4 to handle these more intensive VFs would it?
Now that I've had a brief taste of color and style variety using this filter, using L4 without it seems bland. It would be great if the team would add the ability to change the fonts and styles for the text of individual resources as well as background color but despite this inability L4 is still a great program!
0 -
Tim Engwer said:
I am enclosing the crash log. If I interpret it correctly it seems that L4 runs out of memory each time it crashes per the line "Error detail: OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown." I have 6GB of ram but I believe L4 can only use 2GB of this. So I don't suppose adding more ram would enable L4 to handle these more intensive VFs would it?
Correct. Put simply, L4 can't allocate any more memory or (computer) resources needed for temporary storage of search results.
Dave
===Windows 11 & Android 13
0
