On Thu, 2011-10-27 at 01:24 -0400, Kevin Hunter wrote:
> After a long build, I'm there. As I'm not mired in that part of LibO
> internals, for what visible changes should I be looking?
Cool :-) glad you've got a build. Just a tip: stick with that build for
a while, and/or have two build
On 10/25/2011 04:32 PM, Noel Grandin wrote:
Getting there :) almost have a complete build on my machine :)
After a long build, I'm there. As I'm not mired in that part of LibO
internals, for what visible changes should I be looking?
Heh, or put differently, what Ctrl+F should I use on
http
Getting there :) almost have a complete build on my machine :)
On Tuesday, October 25, 2011, Michael Meeks wrote:
> Hi Noel,
>
> On Tue, 2011-10-25 at 18:51 +0200, Noel Grandin wrote:
>> Duration timers are best implemented using the system's monotonic
>> clock.In Java, this is System.nanoTime(),
Duration timers are best implemented using the system's monotonic
clock.In Java, this is System.nanoTime(),under linux, this is
clock_gettime(CLOCK_MONOTONIC),under windows, it is GetTickCount()
On Tue, Oct 25, 2011 at 17:40, Michael Meeks wrote:
>
> On Tue, 2011-10-25 at 13:54 +0100, Michael Meek
On Tue, 2011-10-25 at 13:54 +0100, Michael Meeks wrote:
> There is one minor annoyance I discovered of a warning under gtk2:
> g_main_context_prepare(): main loop already active in another thread
I pushed a fix for this by implementing a custom timer GSource that we
can query
Hi guys,
I just pushed feature/gtk3 to master. What does that mean ?
well, a few things. While there are no known major bugs, and a fair
bit of testing has been done - there are a large number of backends
that this affects. This mainly affects unix where it touches the gtk,
gtk3, gen, svp,
