Per https://sourceforge.net/p/opensong/discussion/373379/thread/7a6e7732d7/?limit=25#45a7,
this problem needs to be fixed in the next version.
I see that the code has been updated on 2022_10_02 - however the available windows exe is dated 2021_06_01
Can you make a newer windows install file available (am hoping that this problem is fixed in the newer revision !)
P.S: When I download the latest exe file, the revision number i get is v3.4.8(1457)
Anonymous
Following up on this ... there are a lot of commits to the repository since build 1457. Is there any way to download a build of 1533 (or any of the other interim changes)?
Without buying a license for Xojo, I can't build it myself ...
Thanks,
Eddie
Fully agree to that. I would be so thankful of the latest builds to be compiled and available for download. We use Opensong every week and encounter the issues every time, though they are obviously fixed in new revisions.
Is a compiled version for Windows containing this fix available yet? If so, where from exactly, please?
If not, what's the latest version compiled for Windows which doesn't have this bug?
Last edit: Terry S 2024-03-30
Sorry, there's still none.
This bug has been introduced by an update to the development framework, not by any change in our code. Therefore I would have to test through the 3.x versions to find, if any does not yet have the issue.
Opensong 3.0.x versions are Mac only.
All 3.4.x versions are beta versions with various issues. So, I am hesitant to do the work just to guide you "from the frying pan into the fire".
I know for sure that the last regular release 2.2.7 does not have the issue.
I investigated the Windows operating system side of this.
In Windows 10 and 11, there is a setting you can change to get rid of the issue. It is a system wide, user specific setting, so it affects all programs run by the user, but not other users. Search for spelling, typing, or autocorrect on an English Windows. Be creative or try a web search engine for other language versions. Then turn off "Highlight misspelled words" (On a German Windows search for Schreibfehler, then turn off Rechtschreibfehler hervorheben).
I personally still use a Win 8.1 system. There I did not find a setting in the UI. I tried to replicate, what gets changed in the registry and it worked. I don't know about side effects yet.
Create the following entry in the registry:
Path
HKEY_CURRENT_USER\Software\Microsoft\TabletTip\1.7
Value Name
EnableSpellchecking
Type
DWORD
Data
0
(on a command line (all in one line)
reg add "HKEY_CURRENT_USER\Software\Microsoft\TabletTip\1.7" /v EnableSpellchecking /t REG_DWORD /d 0
)Set the value to 1 or remove the entry in order to re-enable the spell checker.
Last edit: SvA 2024-03-30
Danke for your efforts, SvA, and sorry for the long delay in responding. I just logged in and saw your response today.
But what has disabling spell check got to do with being prompted to save songs which have not been changed, please?
Thanks.
Hi Terry
It is a bug or feature in the framework we use. If the spellchecker finds, what it thinks is a spelling mistake, and therefore changes the appearance of the text in the field by underlining it, we get an event that the field (content) changed. Therefor we register that change as the need to save the song in order to preserve the change.
Danke again, SvA.
Strange that TabletTip is used, Sounds like something for a tablet.
I might try adding that to the registry sometime, thank you.
Last edit: Terry S 2024-05-17
Your fix seems to work in Windows 11, SvA.
I (possibly) had to close and re-open OpenSong for it to take effect.
Danke sehr!