Text Selection
I am having a huge issue with text selection through mouse dragging. If I drag across a paragraph break it grabs the ENTIRE next paragraph. It is extremely frustrating! Am I doing something wrong here, or is this a bug that needs to be fixed?
Comments
-
It's a feature called 'smart text selection' and can be turned off under Tools/Settings.
Have joy in the Lord!
0 -
This is the "Smart Text Selection" feature
You can enable / disable it permanently in Program Settings - or temporarily using the Alt key on Windows (Opt on Mac)
0 -
Well, I think it's dumb text selection. Haha, just kidding, I can see where it could be useful. THANK YOU!
0 -
Oh that BEAUTIFUL alt key! You have brought great joy back to my text selecting! Thanks!
0 -
Thanks for the helpful tip about the Alt key. I can certainly see the value of the Smart Text Selection but there are times when the selection I want does not agree with the selection Logos wants.
Ben
0 -
Ben Anderson said:
Thanks for the helpful tip about the Alt key.
[Y] The auto-selection is often kindof wierd!
0 -
I'm experiencing a hotkey issue that is driving me mad.
I am trying to select the verse number "heading" for paragraphs in the ESVSB and make that text large. My highlighting hotkey for that is "L"
However, the autotext selection logic doesn't understand why I'd want to do this, so I have to override it with the Alt key.
My problem is that after making my selection (and releasing Alt), when I press "L" to make that text large, Logos6 instead thinks I want ALT+L, which opens the Library ... about 95% of the time. I've tried various combinations of key and mouse clicks, but can't seem to get around this without disabling text selection in Settings.
Any ideas?
0 -
Unfortunately, I think the only way you're going to be able to accomplish this particular workflow is by disabling Smart Selection in Settings. The only other thing I can think of is to apply your highlighting style by clicking on the style in the Highlighting Tool after selecting the verse number "heading" using Alt.
0 -
Chris Culy (Faithlife) said:
Unfortunately, I think the only way you're going to be able to accomplish this particular workflow is by disabling Smart Selection in Settings. ...
When highlighting other things, there are equally bad key combinations... I am going to have to disable Smart Selection because of this. If Logos / Faithlife fixes this bug [when using Alt to over-ride Smart Selection and using user-defined hotkeys for highlighters, the Alt key remains hot and the user-hotkey instead invokes other commands in Logos ] in the future, I'd appreciate a reply here so that I can turn it back on.
0 -
I'm sorry about this. After trying it out myself, I believe there is a bug here. If you keep holding Alt after you finish making your selection, the behavior you are reporting is "as expected" (since you are pressing Alt+L together), but pressing Alt and then finishing your selection and releasing Alt before pressing L is a different issue and is a bug that should be fixed.
Thank you for reporting this. I will investigate an appropriate fix.
0 -
I have a fix for this internally. We will update this thread when the fix ships in a public build. Thank you.
0 -
Wait, pressing ALT temporarily suspends this? Ok, smart text is being turned back on tonight!
0 -
Chris Culy (Faithlife) said:
I'm sorry about this. Thank you for reporting this. I will investigate an appropriate fix.
[Y] A big part of why I love Logos (or Faithlife)
0 -
Ward Walker said:Chris Culy (Faithlife) said:
I'm sorry about this. Thank you for reporting this. I will investigate an appropriate fix.
A big part of why I love Logos (or Faithlife)Agreed!
Somehow I missed this thread before and look forward to using the alt key in the future.
Using adventure and community to challenge young people to continually say "yes" to God
0 -
Chris Culy (Faithlife) said:
I have a fix for this internally. We will update this thread when the fix ships in a public build. Thank you.
This has been fixed in 6.0a SR-1.
0 -
Angela Murashov said:Chris Culy (Faithlife) said:
I have a fix for this internally. We will update this thread when the fix ships in a public build. Thank you.
This has been fixed in 6.0a SR-1.
[:D]
0
