Organ Details

[Bumblebee001]

I noticed that the software is not saving all the details entered in the text boxes.

[larspalo]

What details?

You're sure you're remembering to tab out of any numerical field?

[Bumblebee001]

I was entering my own data about the organ and upon saving, half the information I wrote disappeared on loading the odf (in GOodf) again.

[larspalo]

I was entering my own data about the organ

In the text box for "Organ comments:" or which one? All of them?

[Bumblebee001]

Organ Builder
Organ build date
Recording details

[larspalo]

Without further information, I'd guess that you're trying to enter strings that contain a semicolon (;).

The character for a semicolon would indicate a comment. It would be automatically stripped from a key=value pair when an .organ file is opened in GoOdf as GO won't display such a string anyway.

[larspalo]

I'm going to fix the semicolon issue by disallowing any entry of a semicolon in the textfields.

[Bumblebee001]

Yes. I separated the info with semicolons: Eg: Build date: Rothwell UK (1870); Bugeja Malta (2011) Normal *text* and *syntax* and *punctuation* should *not* be restricted in text boxes in any way…. in my humble opinion. For as long as you impose such restrictions users will continue to be experience issues and will either report or simply abandon providing the information that would have otherwise been relevant. I see your point re the use of semicolon in an odf. At least a small note above the text box should clarify: *Avoid use of “ ; “ in this text box. * Regards Mark

…

On Sun, 09 Mar 2025 at 15:50, larspalo ***@***.***> wrote: I'm going to fix the semicolon issue by disallowing any entry of a semicolon in the textfields. — Reply to this email directly, view it on GitHub <#113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVM7NS7COTHKDPUFEAJDTT2TRILFAVCNFSM6AAAAABYTSGZRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYHA4TMMRSG4> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: larspalo]*larspalo* left a comment (GrandOrgue/GoOdf#113) <#113 (comment)> I'm going to fix the semicolon issue by disallowing any entry of a semicolon in the textfields. — Reply to this email directly, view it on GitHub <#113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVM7NS7COTHKDPUFEAJDTT2TRILFAVCNFSM6AAAAABYTSGZRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYHA4TMMRSG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Bumblebee001]

Use of semi-colons was indeed the issue I experienced. Confirmed. I used commas instead.

[larspalo]

I consider this issue fixed with the 0.15.1 release.