On Mo, 2011-01-17 at 16:19 +0000, Frederik Elwert wrote: > I think your suggestion makes sense. I always understood ConsumerReady > to only make sense in a template context, that’s why I currently don’t > handle it in Genesis. But using it to hide unwanted configs seems to be > a smart idea. > > My only issue with it is that it isn’t backwards compatible. So if I > implement what you suggest, configs that were created based on > non-supported templates with the current sync-ui won’t show up in > Genesis any longer. So I feel I should at least wait until the next > SyncEvolution release which explicitly sets ConsumerReady = 1, so > re-editing the config in sync-ui would make it show up in Genesis again.
Nothing in SyncEvolution will magically set that flag. Or rather, I wasn't planning to. Now that you mention it, I might as well set the flag for any migrated configuration from SyncEvolution < 1.2, because these used to be user-visible. > Attached, I have a patch that implements this behaviour for Genesis. Is > this what you had in mind? Yes, exactly. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
