Interesting Problem Now "Fixed" - May Be of Interest to Development Team

BillS

When I had to move from Kindle (android) tablet to L5 for speed reasons, my highlights note file transferred smoothly! Kudos to the development team.

I'm reporting this "problem" to Logos as being of possible interest to the development team, since I think I "tripped" over something that you may not have meant to occur.

When I created the Kindle HD note file, I misspelled the name... on Kindle, a highlight note file is much less exposed to me than it is in L5 where I'm constantly adjusting which note files to include via visual filters.

My "mistake": I corrected the spelling of the name in L5 (where it's POSSIBLE to change the name of a note; couldn't find any way to do so in Kindle).

Impact: the connection between Kindle note & Logos note was broken, & no further highlights showed up on Kindle, though I'd check once in awhile to see if the new note file name had downloaded. Nope. In fact, there appeared to be NO syncing of note files afterward.

Today's "Fix": In L5, Documents (tab), Share Documents (function), I created a backup copy of the note file I was working in (in case there was still some unseen tie to the file with the name spelled correctly). Back on Kindle, I deleted the file with the misspelled name. At first, nothing changed, & its highlights were STILL PRESENT in the Bible app. I attempted to "edit" one of those phantom notes. Bible crashed. When I opened it again, it had downloaded all the new highlight note files, & now all seems to be working correctly.

I'm not soliciting advice at this point, but I thought the development team might be interested in what happened, since changing the name in L5 might not have been something you intended a user to be able to do.

(Didn't mean to do "boundary testing" on purpose!)

Blessings, & thanks for all you folks do for us!

Kevin Byford (Faithlife)

I'm not soliciting advice at this point, but I thought the development team might be interested in what happened, since changing the name in L5 might not have been something you intended a user to be able to do.

Thanks Bill,

Something is definitely wrong here but we're not sure exactly where.  We're taking a look.