On Sun, Jul 19, 2015 at 12:42 AM, Michael Meeks
michael.me...@collabora.com wrote:
Hi Pranav,
On Fri, 2015-07-17 at 23:50 +0530, Pranav Kant wrote:
I followed the approach you mentioned.
Heh =)
But the user experience is poor this way. As I am typing things on the
keyboard the
Hi Pranav,
On Fri, 2015-07-17 at 23:50 +0530, Pranav Kant wrote:
I followed the approach you mentioned.
Heh =)
But the user experience is poor this way. As I am typing things on the
keyboard the immediate effect is that it places dummy tiles for
fraction of seconds in place of
I followed the approach you mentioned.
But the user experience is poor this way. As I am typing things on the
keyboard the immediate effect is that it places dummy tiles for
fraction of seconds in place of invalidated tiles. The callback gets
called when the actual tile gets rendered, and it
Maybe I should consider updating the overlay only after I get the actual tile ?
On Fri, Jul 17, 2015 at 11:50 PM, Pranav Kant pranav...@gmail.com wrote:
I followed the approach you mentioned.
But the user experience is poor this way. As I am typing things on the
keyboard the immediate effect
This week I made most of LOK methods, except one or two, asynchronous.
These methods are now being called in separate thread, and are not
blocking the UI at all. You can check the code at my feature branch :
feature/gsoc-tiled-rendering.
One important function that I am still not able to call in
Hi Pranav,
On Wed, 2015-07-15 at 23:48 +0530, Pranav Kant wrote:
One important function that I am still not able to call in separate
thread is drawing the tiles on the screen. The gtk passes the cairo
contexts whenever 'draw' signal is emitted. The drawing works fine if
I use this cairo
