Sometimes, when I hit backspace-enter, it acts like I've also hit ctrl-a

[DrReddP]

This was a persistent problem about a year ago, but after a couple of updates it went away, but now it's back.

If I have a line that is too long and needs a break, I will place the cursor at the beginning of the word that I want to start the second line, and I will quickly hit backspace then enter to delete the space, and insert a line break. The problem is, that sometimes when I do this, it acts like I've hit control-a, and it selects all of the text.

It doesn't do it every time, even if it does it on a particular line and then I go back and try to do it again on the same line, it doesn't do it, but I managed to get it on camera only once. I've tried four different keyboards so it's not that.

Video: http://imgur.com/a/TbTwzie

[darnn]

I think it's related to this, since it also happens when another line is added:
#3141
In 3.6.1 NEXT beta 11:

It's happening at the point at which the textbox switches from not having a scrollbar to having one. It sort of flashes, which I assume means it's getting replaced somehow by the scrollbar kind, and that's when all the text gets selected. Hard to do anything about if it can only be reproduced on certain machines, though, I suppose. For the record I'm back on a Windows 7 computer now.

Also, for the sake of trying to reproduce it: my max. number of lines is set to 2, and I'm using shift+enter in that gif in order to force SE to insert a line break even though it's over the limit. And, the entire text getting selected, it only happens once until you move to a different subtitle. So, like, if I put that subtitle back the way it was, two lines, and repeat what I did, it will not select the text. But if I go back one subtitle and then forward one subtitle, and do everything the same way, it will select all the text again.

[niksedk]

I have not been able to re-produce this in my Win 10 system.

Note that SE can use two different text boxes - one is the default text box, and the other is the rich text box which support colors. See Options - Settings - Appearance:

(Syntax coloring will make SE use the rich text box)

What do you use? Does it happen with both for you? @DrReddP: Are you also on Win 7?

[OmrSi]

3.6.1 if official.
3.6.1 NEXT is the beta.

[DrReddP]

The 3.6.1 zip you posted above is giving me this. The other versions never did this

[OmrSi]

The one called SubtitleEditBeta.zip is the beta.

[DrReddP]

1. Why is Windows defending against 3.6.1
2. How do I get my old font back in the edit box. "Use syntax coloring" didn't change it

[darnn]

3.6.1 is the latest full release, so first of all, you should use that one. The portable version is here:
https://github.com/SubtitleEdit/subtitleedit/releases/download/3.6.1/SE361.zip

As for getting your old font back, open the previous version you were using, open settings and check what you selected in the font tab. Then, in 3.6.1, go to settings, appearance (you should now have it on the left, like in the post above), and change the settings to those you were using previously.

As for Windows Defender, all I can say is that mine wasn't doing that in Windows 10. It's a false positive, either way.

[darnn]

I use the default one. This doesn't appear to happen for me with the rich text one. The rich text one doesn't blink in and out when the scrollbar is added, either. I seem to recall there was some specific reason I was using the default one (beyond the fact that I don't need syntax coloring), though, so I'd love it if it didn't happen there either.

[DrReddP]

Ty

…

On Tue, Jun 1, 2021, 4:52 PM darnn ***@***.***> wrote: 3.6.1 is the latest full release, so first of all, you should use that one. The portable version is here: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.6.1/SE361.zip As for getting your old font back, open the previous version you were using, open settings and check what you selected in the font tab. Then, in 3.6.1, go to settings, appearance (you should now have it on the left, like in the post above), and change the settings to those you were using previously. As for Windows Defender, all I can say is that mine wasn't doing that in Windows 10. It's a false positive, either way. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5076 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATTXE6OIEOKYQJYOHQJWMYLTQVCCDANCNFSM453LAOGQ> .