StrokesPlus.net
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
Roland  
#1 Posted : Tuesday, July 2, 2019 8:33:28 AM(UTC)
Roland

Rank: Member

Reputation:

Groups: Translators, Approved
Joined: 11/7/2018(UTC)
Posts: 15
Germany

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
This seems to be a new problems in todays release:

I have text expansions that replace 2-3-letter shortcuts with longer text (names, greetings, email address, etc.)
Examples:
ch -> Cheers,
br -> Best regards,

Today I found that they all don't work anymore! (with one exeption, see below)

Also: The expansion text for the shortcut "rr" is now triggered by a single "r".
Even worse: S+ treats the german umlauts (ÄÖÜaöü) like a space, so that words like "für" will be expanded ("f<expand>", the umlaut gets also replaced).


Rob  
#2 Posted : Tuesday, July 2, 2019 9:16:16 AM(UTC)
Rob

Rank: Administration

Reputation:

Groups: Translators, Members, Administrators
Joined: 1/11/2018(UTC)
Posts: 401
United States

Thanks: 5 times
Was thanked: 78 time(s) in 68 post(s)
I haven't touched anything relating to Text Expansions since the last fix.

Can you confirm by installing an older version and testing it out?

- Go here: https://www.strokesplus.net/Downloads
- Scroll down to bottom and enter 0.3.1.8 and download (obviously click No to update when S+ starts with the older version.

See if it is working properly. Then restart S+ and download the update and test again.

It's possible something else is in play, the text expansion code is pretty ugly behind the scenes, in terms of hooking the keyboard, tracking characters, etc.
So I want to be sure this is a new problem and not just an isolated situation on your system where things have gotten mucked up or something is different than before.

Also test using English and German keyboard layouts to see if there's a difference.
Roland  
#3 Posted : Friday, August 2, 2019 2:49:45 AM(UTC)
Roland

Rank: Member

Reputation:

Groups: Translators, Approved
Joined: 11/7/2018(UTC)
Posts: 15
Germany

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Sorry for the late response. I'm now back from travelling.

Text Expansion works again for me (0.3.2.9).

Unfortunately the problem with the German Umlauts described above still exists.
S+ treats the german umlauts (ÄÖÜaöü) like a space, so that words like "dürr" will be expanded like "rr" ("dü<expand>", the umlaut gets *no longer* replaced).

On the other hand, special characters like parenthesis SHOULD be treated like a space, so that I could replace "eg" with "e.g.", even if the text is "..., (eg". (ok, I added another expansion for "(eg")

In addition, S+ seems to ignore a subsequent [space] in the text to be replaced. My expansion is "eg" -> "e.g.[space]", but the [space] does not appear, while a [newline] does.

EDIT: another strange thing: the word "123456r" (any 6 letters + r) triggers the expansion for "rr"

Edited by user Friday, August 2, 2019 6:04:00 AM(UTC)  | Reason: Not specified

Rob  
#4 Posted : Friday, August 2, 2019 7:48:32 AM(UTC)
Rob

Rank: Administration

Reputation:

Groups: Translators, Members, Administrators
Joined: 1/11/2018(UTC)
Posts: 401
United States

Thanks: 5 times
Was thanked: 78 time(s) in 68 post(s)
I couldn't reproduce your rr expansion issue, but I did make a few changes to the text expansion code to hopefully address things like ü.

So try 0.3.3.0 and see what issues are still remaining.
Rob  
#5 Posted : Friday, August 2, 2019 2:33:02 PM(UTC)
Rob

Rank: Administration

Reputation:

Groups: Translators, Members, Administrators
Joined: 1/11/2018(UTC)
Posts: 401
United States

Thanks: 5 times
Was thanked: 78 time(s) in 68 post(s)
Note that now nearly all characters which produce something visible in a text box are not treated any different than a standard letter, this would be in regard to your statement about "(eg".

Someone else specifically wanted non-letters to be part of the tokens to prevent accidental expansion, which I've also had happen as well. For example, "//hello" as the token so typing "hello" wouldn't cause an expansion for a common word.

While this could cause some people to have to make an extra expansion list item, like in the case of "(eg", it is more simple in the code (and for people to understand intuitively) to just treat all characters basically the same.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.