https://bugs.meego.com/show_bug.cgi?id=13511
--- Comment #6 from Jussi Kukkonen <[email protected]> 2011-11-14 14:26:05 UTC --- (In reply to comment #5) > So the change which broke the UI was that the default = "ScheduleWorld" config > was downgraded to not ConsumerReady? As far as I can tell, yes. Something also changed so the name entry now shows "Scheduleworld". It didn't do that before I think? > Whether the "default" config has the flag set is basically undefined. If it > helps the UI, then we can define it so that it must be set. >From my POV that would be make things easier, as there are quite a few special cases in the widget creation code already -- but up to you. > What other properties must be set for the "default" template? Just the list of > sources? Well, looking at how the widget actually draws itself, pretty much all data in a "default" widget gets over-written anyway -- these options are the only ones used to decide if/how the widget gets created: "ConsumerReady" "PeerIsClient" "syncURL" "peerType" If you _want_ to change the "default" config to have non-scheduleworld data in it (like some other peername, url, etc), that would work. But I have the over-write code in place already so I can just add a rule for PeerName as well so new configs aren't called "Scheduleworld" in the ui. I think the simple choice is: - you change the default to ConsumerReady = 1 (assuming this is feasible for you) - I over-write PeerName for "default" configs -------- Product: SyncEvolution Component: GTK UI MeeGo Release: unspecified Severity: normal Priority: Medium Keywords: Status: ASSIGNED Who: [email protected] Assigned To: [email protected] Target Build: 1.2 Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=13511 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
