[PATCH 1/7] Refactor device handling threads

[Anton Lundin]

On 20 January, 2015 - Thiago Macieira wrote:

> On Tuesday 20 January 2015 22:40:49 Anton Lundin wrote:
> > This refactors the device handling threads into having one common
> > ancestor class.
> 
> Why? What's the value of this? I'm assuming it's something further down the 
> line, but it wasn't evident for me...
> 
> Is it just to make things simpler?

It's part of the whole get-progress-events series, and I thought using a
common ancestor to all those classes made it easier to implement the
whole progress event thingie.

That way i can have them all behave the same way in that respect.


I also have some unfinished code for generating trace logs from
different actions for debugging purposes. I've used it my self to
diagnose some older bugs, but its kinda rough, and I haven't had the
time to clean that code up. (And it hasn't bin needed to get any debug
logs from users yet...)


Does that make more sense?


//Anton


-- 
Anton Lundin	+46702-161604