Hello,
It is time for a new status report. Over the past week, I've managed to make the
notifications somewhat easier to use by module writers, by modifying the new and
free functions to handle all the fields of the notification struct.
This, along with some other minor changes also solved the wa
Hi,
On Fri, 2012-07-27 at 09:45 +0300, Tanu Kaskinen wrote:
> Fully agree with this.
Great!
> Is this a widely used convention in the Vala world? To me the "default"
> parameters that however can't be used as real default parameters seem
> strange and confusing. The programmer should read the fu
Hi folks,
> Tanu Kaskinen writes:
>
> Hi Tanu,
>
>> On Fri, 2012-07-20 at 17:32 -0300, Flavio Ceolin wrote:
>>> Tanu Kaskinen writes:
>>> > There were problems with the code. I don't remember what exactly was
>>> > broken, though. But at least I didn't like the concurrency handling: I
>>> > real
Hi Tanuk,
On Sat, Jul 28, 2012 at 4:12 PM, Tanu Kaskinen wrote:
> On Thu, 2012-07-26 at 12:20 +0200, Mikel Astiz wrote:
>> Currently (and IMO incorrectly) module-bluetooth-device and
>> module-bluetooth-discover include some policies to handle the initial
>> state and the transitions. This needs
At 2012-07-19T10:56:09+0200, David Henningsson wrote:
> What I meant was that I can successfully run your latency test with
> 10 ms here - when I go down to 5 I start to get xruns. In that
> context, getting problems around 50 - 100 ms of latency is quite a
> lot.
Oh, right. Of the three bug repo
