ISSUE: Highlighting performance is terrible today?
I am using the iOS iPad Bible app (iOS 6.x) v4.0.3, and when trying to highlight today the app hangs for a long time, and often flips me back to iOS.
Anyone else seeing these kinds of performance issues? I didn't have them a few days ago!
Comments
-
Hello Ward, I haven't experienced any crashes or app hanging today, but, if it's any consolation, highlighting in the Logos iOS app is always slow for me.
0 -
Anyone else seeing these kinds of performance issues?
Sorry, no. [:S]
I am using the iOS iPad Bible app (iOS 6.x) v4.0.3, and when trying to highlight today the app hangs for a long time, and often flips me back to iOS.
- Are you using only one note document? If so, what happens with a new, blank document?
- Are you using only one highlighter? Pallet? If so, what happens when you use another one?
- Are you using only one resource? If so, what happens when you use a brand new (unhighlighted) resource?
- Have you done a full restart of the device?
0 -
Anyone else seeing these kinds of performance issues?
Sorry, no.
I am using the iOS iPad Bible app (iOS 6.x) v4.0.3, and when trying to highlight today the app hangs for a long time, and often flips me back to iOS.
- Are you using only one note document? If so, what happens with a new, blank document?
- Are you using only one highlighter? Pallet? If so, what happens when you use another one?
- Are you using only one resource? If so, what happens when you use a brand new (unhighlighted) resource?
- Have you done a full restart of the device?
go figure...went to run these tests, and things are working correctly...
I was trying to highlight in
things were very erratic and slow, but I was mostly trying to use the built-in "Highlighter Pens"--I use the default of writing back into whatever pallete document the highlighting was defined in. I was using highlighters from several documents.
While things are working now, I confirmed that I can highlight in other documents during this test.
I hadn't done a full restart of the device, but had closed all other apps and fully closed Logos a couple times. It was working about 50% to finally create a highlight--if I waited long enough for it to "think"
I was using Logos5 on Windows8.1 on the same network at the same time, and things were working normal
odd...
0 -
Ward (and Brad) —
I use the app daily to read and highlight and have no issues. There are several things I have discovered, however, and my behavior is different than the default settings.
- Highlighting slows down with 1) large note files and 2) large amounts of highlights/notes within a single resource.
- Highlight notes, by default, go into a pallet specific note file. That is the easiest behavior (since it is automatic,) but it makes no sense to me and creates havoc in performance
- instead, I create resource specific note files. If I am reading "the peacemaker," I have a note file named such and store those highlights there.
- The only note file which gives me any trouble is my devotional bible reading document. I create a new one each year and will be deleting the current one in a week or so. Currently, highlihts take about 15-20 seconds to appear, but only in that resource / note file. Other note files take 1-3 seconds for highlights to appear.
0 -
Thanks, Alabama, that is a very helpful explanation and provides some good strategies for improving the highlighting performance. Now I'll have to decide what to do about it, given all of the highlights I already have in place and would like to keep! I appreciate the tips.
0 -
Thanks, Alabama, that is a very helpful explanation and provides some good strategies for improving the highlighting performance. Now I'll have to decide what to do about it, given all of the highlights I already have in place and would like to keep! I appreciate the tips.
If memory serves, I may have created a UserVoice request for "highlighting management" within Logos: i.e., a way to automatically migrate various styles/pens from one document to another. I have so many highlights that it is effectively impossible for me to accomplish this manually. If I could have a script run from time to time, then I could automatically move highlights around to optimize performance (and minimize the library-wide impact if a highlighting file became corrupted)...and better yet, then it wouldn't matter where I had the highlights write to--I'd fix that issue retroactively.
0
