Solution b is not an option since as Mikkel stated it will break the API and ABI
I think we are stuck with adding the GetDataSourceForid method. It wont harm 
any1 and will satisfy the case we have

You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

  DataSourceRegistry should have GetDataSourceForId method

Status in Zeitgeist Framework:

Bug description:
  DataSourceRegistry should have a way to get a DataSource from it's id
  especially because the DataSourceEnabled signal only sends an id
  rather than a DataSource in the signal.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to