Can't set a sound #4

Activity

1. OboTheHobo commented on Jun 7, 2018

   

   OboTheHobo

   on Jun 7, 2018

   Author

   More actions

   as well I have tried many alternatives and yes, it does work using /splay
2. RyanWolfe556 commented on Nov 9, 2018

   

   RyanWolfe556

   on Nov 9, 2018

   Last edited by RyanWolfe556

   More actions

   I am having the same issue.

   However, I have discovered a way around this, use
   /alerts set <alert> sound [<soundfile>|OFF]
   and that works just fine.

   A side note of this, if you install HexChat outside of main C:\ then you cannot find the audio files.
3. tyrope commented on Nov 20, 2018

   

   tyrope

   on Nov 20, 2018

   More actions

   Is this a HexChat limitation, or a plugin limitation? Seems silly that %appdata% isn't accessible outside a C:\ install, perhaps we need to run it with admin privileges?
4. Poikilos commented on Feb 13, 2020

   

   Poikilos

   on Feb 13, 2020

   More actions

   @tyrope The purpose of %APPDATA% is storing user-specific settings and data without admin priveleges. The problem may be spaces in the path, or assuming C: when translating from unix-like paths, if that is a problem somewhere in the code. @RyanWolfe556 By "outside of main c:" do you mean on another drive letter, or somewhere deeper? What is the install path that does not work?
5. Poikilos commented on Feb 13, 2020

   

   Poikilos

   on Feb 13, 2020

   Last edited by Poikilos

   More actions

   @dewiniaid Are you here? The issue seems to be a missing length checking for the params list. The same occurs in 2.14.3 on Fedora 31:

   Traceback (most recent call last):
      File "/home/owner/.config/hexchat/addons/alerts.py", line 2255, in command_hook
        event.call()
      File "/home/owner/.config/hexchat/addons/alerts.py", line 1323, in call
        self.fn(self)
      File "/home/owner/.config/hexchat/addons/alerts.py", line 1456, in wrapper
        args.append(event.word_eol[max_args - 1])
   

   Expected behavior:

   • If the param after /alert is a setting, say: print("Your syntax is incorrect. To set variables you must do /alerts set <alert> {setting_name} <value>.".format(setting_name=params[0])) or where params[0] is the setting that should instead be a command.