When I click in the reference text box, nothing is highlighted and I have to delete everything before I can type in the new reference.I don't see this on Windows - are you running on Windows or Mac?
[resolved] Bug: Reference text box 6.2.0.0027
Lankford Oxendine
Member Posts: 242 ✭✭
When I click in the reference text box, nothing is highlighted and I have to delete everything before I can type in the new reference. This was a bug when Logos 6 was first released, fixed in 6.0b SR-1 and now has returned in 6.2.0.0027.
0
Comments
-
Lankford Oxendine said:
When I click in the reference text box, nothing is highlighted and I have to delete everything before I can type in the new reference.
I don't see this on Windows - are you running on Windows or Mac?
0 -
Sorry, should have posted that I'm running Mac.
0 -
Lankford Oxendine said:
Sorry, should have posted that I'm running Mac.
Any other Mac users who can check this?
0 -
Graham Criddle said:
Any other Mac users who can check this?
I didn't understand the problem at first, but I can now confirm. For clarification: When clicking in the reference text box (i.e. where you would see the reference, headword, page number, etc.), the text isnt selected, so the user must manually delete the text. What is expected is that by clicking in the box, all of the text would be selected, allowing the user to replace the text by simply typing.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Thanks for the clarification!
0 -
Thanks Alabama
alabama24 said:What is expected is that by clicking in the box, all of the text would be selected, allowing the user to replace the text by simply typing.
And on Windows it works exactly as you describe it
0 -
It looks like we're aware of this. Thank you for reporting it!
0 -
Thanks for the update. I'm not trying to be snarky but I really hope this doesn't take over 2 months to fix like last time. I know this is a minor issue but it really does cut into my workflow.
0 -
Lankford Oxendine said:
Thanks for the update. I'm not trying to be snarky but I really hope this doesn't take over 2 months to fix like last time. I know this is a minor issue but it really does cut into my workflow.
With a 6 week development and release cycle, it clearly depends upon where one is in the cycle how long the repair will take. I have great hope that a disciplined 6 week cycle will decrease the number of bugs in the software. But that depends upon truly being disciplined - freezing changes at the point one is schedule to freeze changes and not cheating with "little" changes. I know it is frustrating as a user to wait ... but it in long run it benefits all of us.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Tommy Ball said:
It looks like we're aware of this. Thank you for reporting it!
This should be fixed in 6.3.
0
