Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: Button clickable area off
#1
Updated to MoOde 9.2.4, with the new kernel version that supports my Allo Piano 2.1 dac again.

Smaal problem detected with this version of MoOde.
In the section "Audio Options"   "Chip options" the edit button is only clickable direct right of the actual button.
I noticed this on an other button too. Camilla DSP  to open the pipeline editor you have to click on the left side of the button.
BTW when opening the pipeline editor only the text "Pipeline editor"appears and the links to other section on top.
Tested this with Firefox, Brave and Edge.
Maybe related to this topic ==> https://moodeaudio.org/forum/showthread.php?tid=7408
Reply
#2
Pipeline editor opens ok using chrome, firefox, safari on a Mac.

The chip options button issue is a bug :-0
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
Run the command below to install the patched file and let me know if it fixes the issue.

Code:
sudo wget -q https://raw.githubusercontent.com/moode-player/moode/refs/heads/develop/www/snd-config.php -O /var/www/snd-config.php
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#4
Well, would you look at that! Here was me assuming that the chip options I used to set were simply no longer available in the drivers in moOde 9 and there they were hiding behind the invisible button Smile

I've tried the fix, but still have to click to the right even after a reboot.
----------------
Robert
Reply
#5
(02-10-2025, 07:48 PM)Tim Curtis Wrote: Run the command below to install the patched file and let me know if it fixes the issue.

Code:
sudo wget -q https://raw.githubusercontent.com/moode-player/moode/refs/heads/develop/www/snd-config.php -O /var/www/snd-config.php

This patch is fixing the issue at my end.

regards
Wim
Reply
#6
Hmm, tried on three players now. Hasn't worked on any of them. Also, when I open the chip options page by clicking to the right, I just a get a page that says "Chip Options" but doesn't have anything to set.
----------------
Robert
Reply
#7
Try the usual suspects, browser cache etc
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#8
Seems the button is getting the disabled attribute set.

snd-config.php seems to be taking longer than I remember to load, but then I just set and forget from an iso install.

Paul
Reply
#9
(02-11-2025, 11:12 AM)Tim Curtis Wrote: Try the usual suspects, browser cache etc

Yeah, tried all that even a fresh browser...

Must be something on my end, I'll keep faffing.
----------------
Robert
Reply
#10
(02-11-2025, 03:10 PM)the_bertrum Wrote:
(02-11-2025, 11:12 AM)Tim Curtis Wrote: Try the usual suspects, browser cache etc

Yeah, tried all that even a fresh browser...

Must be something on my end, I'll keep faffing.

Verify that you actually have the fix, in case something went sideways with the wget.

Code:
pi@moode9:~ $ cat /var/www/snd-config.php | grep "cfgAudioDev"
$cfgAudioDev = sqlQuery("SELECT chipoptions, driver, drvoptions FROM cfg_audiodev WHERE name='" . $_SESSION['i2sdevice'] . "'", $dbh)[0];
       $_chip_btn_disable = (!empty($cfgAudioDev['chipoptions']) && $_SESSION['i2soverlay'] == 'None' && $i2sReboot === false) ? '' : 'disabled';
       $_chip_link_disable = (!empty($cfgAudioDev['chipoptions']) && $_SESSION['i2soverlay'] == 'None' && $i2sReboot === false) ? '' : 'onclick="return false;"';
if (!empty($cfgAudioDev['drvoptions']) && $_SESSION['i2soverlay'] == 'None' && $i2sReboot === false) {
       $_select['drvoptions'] .= "<option value=\"Enabled\" " . ((strpos($cfgAudioDev['driver'], $cfgAudioDev['drvoptions']) !== false) ? "selected" : "") . ">" . $cfgAudioDev['drvoptions'] . " Enabled</option>\n";
       $_select['drvoptions'] .= "<option value=\"Disabled\" " . ((strpos($cfgAudioDev['driver'], $cfgAudioDev['drvoptions']) === false) ? "selected" : "") . ">" . $cfgAudioDev['drvoptions'] . " Disabled</option>\n";
pi@moode9:~ $
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply


Forum Jump: