search

KenjiTakahashi / pacmixer

an alsamixer alike for PulseAudio.
GNU General Public License v3.0
116 stars 7 forks source link

pacmixer crashes in settings dialog #14

Open murinicanor opened 8 years ago

murinicanor commented 8 years ago

hi,

thanks for pacmixer! i've compiled the program on debian testing and it works as expected except the settings dialog: it show no settings and crashes as soon as i use the 'l' key or the right arrow key with the message : Uncaught exception NSRangeException, reason: Index 0 is out of range 0 (in 'objectAtIndex:')

pacmixer-log.txt

if you need the debug log, i can recompile and attach that

KenjiTakahashi commented 8 years ago

Thanks for reporting the issue. The crash is, obviously, a bug, there's probably some boundary check missing, I'll have a look at it later. As for no settings, do you actually expect any settings? I don't see any settings controls being reported in the log. Keep in mind that those are not pacmixer settings, but your device settings. There might be none, depending on your audio device and its' driver. If you're not sure, you can check what pavucontrol shows in the Configuration tab.

murinicanor commented 8 years ago

hi, sorry for not getting back to you earlier:

As for no settings, do you actually expect any settings? I don't see any settings controls being reported in the log. Keep in mind that those are not pacmixer settings, but your device settings. There might be none, depending on your audio device and its' driver. If you're not sure, you can check what pavucontrol shows in the Configuration tab.

hm, i guess i did expect settings based on the fact that there is a settings tab. you're right, there are not settings in the configuration tab, except the sound profiles. maybe from an ux point of view, the settings tab should not be there, if there are no settings...

KenjiTakahashi commented 8 years ago

No problem, I have long delays myself too ;-].

Oh, I see. Perhaps it would indeed be nice to hide tabs that are empty, even if it is kinda unusual behaviour for terminal interfaces. It won't happen before I get myself to refactor the UI parts of the code, though. Which will happen, at some point, hopefully.