Hi all,
so, I guess using sound in the right places is not a bad idea. Of
course, having 60 random beeps across the codebase means we're mostly
silent already (well, my experience of workingin LibO backs this up) –
in other words: removing the remaining beeps won't hurt so much any
more. What I'd
Hi Thomas,
Thomas Arnhold wrote (21-02-12 13:20)
What do you think, is it save to remove it?! Or would you think this
would be a gain in usability?
Is it possible for you to polish my crystal bowl a bit, e.g. where do we
have those beeps.
Just from what pops up in my mind, I think those
Hi Thomas,
On Tue, 2012-02-21 at 13:20 +0100, Thomas Arnhold wrote:
I recently discovered that there's a more or less complete usage of
acoustic beeps in Libo. This is done by System::Beep(). I did a grok for
Beep and got 59 results all over the code. I don't think that is much.
Is this a
On Tue, 2012-02-21 at 14:08 +0100, Cor Nouws wrote:
Is it possible for you to polish my crystal bowl a bit, e.g. where do we
have those beeps.
git grep -5 Sound::Beep
and have a think about the context's ;-)
Just from what pops up in my mind, I think those happen when a
Yep this is the VCL sound api...
On 02/21/2012 03:25 PM, Michael Meeks wrote:
Hi Thomas,
On Tue, 2012-02-21 at 13:20 +0100, Thomas Arnhold wrote:
I recently discovered that there's a more or less complete usage of
acoustic beeps in Libo. This is done by System::Beep(). I did a grok for
Beep
