Issue editing questions and notes in Bible Study Builder

Ralph Wood · 2024-11-26T01:08:51+00:00

There was an error rendering this rich post.

When trying to edit a question in Bible Study Builder I've experienced an issue where the text that I type gets inserted in a location other than where the cursor is placed - usually somewhere above where I am trying to type. This has also happened when trying to edit the notes section. The only way I could overcome the problem was to trash the question (or note) and start over.

Has anyone else experienced this annoyance?

I am on version 37.2.12 / Logos Pro

Find more posts tagged with

Performance

Bug

Desktop App

Comments

Jonathan Bradley

https://community.logos.com/discussion/243701/issue-editing-questions-and-notes-in-bible-study-builder

I can replicate the issue. When editing an inserted question, if you type after the end, after the period, it works fine. If you edit mid-sentence, it automatically starts typing at the start of the question.

Jonathan Bradley

We can't upload video clips.

Dave Hooton

https://community.logos.com/discussion/comment/1344741#Comment_1344741

Please create a separate post for this problem

Joe McCune (Faithlife)

I am unable to duplicate this issue. Please chime in if you are still experiencing this, including screenshots if possible.

Jonathan Bradley

https://community.logos.com/discussion/comment/1348625#Comment_1348625

What’s your email address? I can email you a video when I get home. I tried to upload it the other day and failed.

Ralph Wood

Was this fixed with version 38? I’m no longer experiencing this issue. Editing questions and notes are working like a charm.

Joe McCune (Faithlife)

https://community.logos.com/discussion/comment/1348655#Comment_1348655

If you are still experiencing this problem with version 38, please email the video to cs@logos.com, Attention Joe.

Joe McCune (Faithlife)

https://community.logos.com/discussion/comment/1348785#Comment_1348785

Ralph, the Bible Study Builder was significantly improved with the version 38 update, so it is certainly possible it resolved this issue.

Jonathan Bradley

It appears to have been resolved in v.38. I hadn't tried to replicate the issue since before the update. Thank you!