| Both sides previous revision Previous revision | |
| softwares:giocoso:changelog [2026/03/25 09:02] – [Giocoso Version 3.37 - Scheduled for March 31st, 2026] hjr | softwares:giocoso:changelog [2026/03/25 09:16] (current) – [Giocoso Version 3.37 - Scheduled for March 31st, 2026] hjr |
|---|
| **__Minor Enhancement__**: The software licence is now viewable within a dialog form, rather than with the **less** utility. | **__Minor Enhancement__**: The software licence is now viewable within a dialog form, rather than with the **less** utility. |
| |
| **__Significant Enhancement / Bug-fix__**: The logic for doing default searches of music to play (Option 1 on the Play Music) has been significantly revised. As explained in this blog piece, there was a bit of a logic bomb lurking in Giocoso's random selection code. By ranking per-composer recordings //before// deciding whether any recording qualified, on configured selection grounds, to be played, Giocoso was making it very hard for an eligible recording to be actually selected. The code change now makes all eligible recordings capable of selection, meaning that Giocoso will now more easily find a diverse set of qualifying recordings to play. In plain English, Giocoso's random selection was previously failing to find things to play when it could and should have because it was doing things in a logically over-restrictive way. Now, that won't be the case. | **__Significant Enhancement / Bug-fix__**: The logic for doing default searches of music to play (Option 1 on the Play Music) has been significantly revised. As explained [[blog:giocoso_random_music_selection_logic_bomb|in this blog piece]], there was a bit of a logic bomb lurking in Giocoso's random selection code. By ranking per-composer recordings //before// deciding whether any recording qualified, on configured selection grounds, to be played, Giocoso was making it very hard for an eligible recording to be actually selected. The code change now makes all eligible recordings capable of selection, meaning that Giocoso will now more easily find a diverse set of qualifying recordings to play. In plain English, Giocoso's random selection was previously failing to find things to play when it could and should have because it was doing things in a logically over-restrictive way. Now, that won't be the case. |
| ===== Giocoso Version 3.36 - March 18th, 2026 ===== | ===== Giocoso Version 3.36 - March 18th, 2026 ===== |
| **__Bug-fix__**: Giocoso is written in the United Kingdom, where we expect numbers to be written as "1.43", using a full-stop as the decimal point. Trouble is, anyone using Giocoso in Europe (for example) would expect that to be written as "1,43" with a comma as the decimal point. European operating systems presented with "1.43" will declare it to be an invalid number and mayhem results. This has recently come to light as an example of UK small-mindedness (and my inability to think globally) as a result of a user in Germany (or at least, using a German locale on a Tuxedo OS) encountering an 'invalid number' error when trying to implement Giocoso's ReplayGain functionality. This has now been corrected, by forcing Giocoso to use a locale in which full-stops are regarded as 'correct', no matter what the wider operating system may think. My thanks to Helmut for the bug report and working with me to confirm the nature of the problem and success of the fix. If users in other non-UK lands have equally exotic number representation issues, this fix should resolve it for them too. | **__Bug-fix__**: Giocoso is written in the United Kingdom, where we expect numbers to be written as "1.43", using a full-stop as the decimal point. Trouble is, anyone using Giocoso in Europe (for example) would expect that to be written as "1,43" with a comma as the decimal point. European operating systems presented with "1.43" will declare it to be an invalid number and mayhem results. This has recently come to light as an example of UK small-mindedness (and my inability to think globally) as a result of a user in Germany (or at least, using a German locale on a Tuxedo OS) encountering an 'invalid number' error when trying to implement Giocoso's ReplayGain functionality. This has now been corrected, by forcing Giocoso to use a locale in which full-stops are regarded as 'correct', no matter what the wider operating system may think. My thanks to Helmut for the bug report and working with me to confirm the nature of the problem and success of the fix. If users in other non-UK lands have equally exotic number representation issues, this fix should resolve it for them too. |