On Fri, Oct 5, 2012 at 4:09 AM, Lucas De Marchi <lucas.demar...@profusion.mobi> wrote: > On Thu, Oct 4, 2012 at 11:56 AM, Enlightenment SVN > <no-re...@enlightenment.org> wrote: >> Log: >> e/connman: Check for the correct messages. >> >> Checking two times the same message does not make any sense. The only >> logical >> thing seems to be checking for the properties message here. Leaving the >> wifi >> properties message out as not every setup has wifi. At least on my desktop >> here I don't have /net/connman/technology/wifi so we should not fail >> without >> it. > > You could put wifi props there. We are just checking if the message > was actually created. > > HOWEVER, handling technologies in this function is totally misplaced. > I blame raster for adding this code :). The intention of this function > was to deal with Manager interface. Right approach would be to create > some infra similar to deal with technologies, calling > GetTechnologies() on Manager, monitoring signals etc. > > That said... as it is right now it works, so I'm not changing it. > Soon it will start using edbus, too.
You can't use edbus until e17 is released. Just to be sure you don't miss that :-) -- Cedric BAIL ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
