Closed GoogleCodeExporter closed 9 years ago
Both 2.x and 3.x make sounds. Both also try to respect the system setting for
whether to make sounds or not.
However, there might be a bug where 2.x tries to use an old location for the
sound effect and thus will not work. Also, Mavericks broke the ability to check
the system setting for making sounds, so sounds can not be disabled there.
Original comment by paracel...@gmail.com
on 2 Nov 2013 at 7:15
So, I clearly don't understand something here... What program is making the
sound? Is it Xee? Is it Finder? Is it the OS?
When you say that Xee 2.x might have a bug that looks in the wrong place for a
sound, causing it to not make a sound, that implies that the sound is created
by Xee, not by Finder, and not by the OS. That means Xee could choose not to
make the sound... right?
I did some further examination of this... In my System Preferences / Sound, I
found a setting, "Play user interface sound effects." I disabled that setting,
and now when I delete files in Finder, no sound is made. However, Xee 3.x
still makes the sound!
It seems to me that this bug should not be marked Invalid, because your program
is the one choosing to make the sound, and choosing which sound to make
(presumably by looking up certain preferences).
I think Xee3 should offer the user a preference as to whether to make a sound
when deleting a file. Or, failing that, at least respect the user's preference
regarding user interface sounds.
I know this might seem like a trivial matter, but I was actually trying to
listen to a Podcast on my system while cleaning up some image files. And for
some reason the Podcast was recorded with low volume, so I had to turn up my
system volume in order to hear it, and so all the delete-file sounds were very
loud and distracting while I was trying to listen to the voices on the Podcast.
So please do not mark this bug as Invalid, but do give it some thought, if you
could. Thank you.
Original comment by zipfoxt...@gmail.com
on 3 Nov 2013 at 12:49
As I said, Xee respects the system setting, but Mavericks has broken the code
used to check the system setting.
I'd rather wait to see if Apple un-breaks this first, and if not, I might have
to add a custom option in Xee. But I'd prefer to keep it simple by following
the system settung.
Original comment by paracel...@gmail.com
on 3 Nov 2013 at 12:57
Ok, thanks for clarifying that. I understand the issue now. :)
Original comment by zipfoxt...@gmail.com
on 3 Nov 2013 at 1:02
Original issue reported on code.google.com by
zipfoxt...@gmail.com
on 2 Nov 2013 at 7:12