On Wednesday, March 23, 2011 22:21:33 Malte Gell wrote:
Am Wed, 23 Mar 2011 11:37:16 +0100
schrieb Sebastian Kügler
: Let me guess: Your problem is not that the startup order is wrong, but that korganizer doesn't understand that it's offline, and doesn't get noticed when it's online, hence won't refresh the data from your webservice. That's a one or two line change in korganizer, best is to file a bugreport against it.
That is correct. Korganizer fetches data from my Google calendar and when the system is offline it produces an error message. I think Korganizer can be set to fetch calendars every X minutes which would be a workaround.
That's also not the right way to go about it. KDE's Solid framework can notify you once the network comes up, you connect your apps' synching and updating mechanism to that signal, and you get *INSTANT* updates once your network comes up. I've actually done this for quassel some time ago, and it works nicely: I remove the network connection, quassel goes into disconnected mode immediately. As soon as the network comes up again, quassel reconnects without any sort of timeout. My experience is, that a timeout is not very useful for applications anyway, since the first thing I'd do after the network comes up is hit the refresh button anyway, so the updating has to happen immediately, if it should be useful. Anyway, please file a WISHLIST bug against korganizer that it should update on network connect.
Malte btw: being able to set the start order of apps would be a good thing though
Why? You just pointed out that your usecase is a completely different issue... Besides, apps might be started in parallel (which certainly improves startup performance on multicore systems with fast disks), so there isn't really an order to begin with. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org