Thanks for your feedback, however we knew that this one would pop up (it’s obvious) 😉 The reason behind the change of the UI was that were facing a lot of different use cases lately: from users with only a few resources to users with a huge number of calendars and address books. Big lists were not performing well and sometimes it was impossible to scroll through a big list and selections were very laggy. Therefore we needed a more performant way with the newly introduced RecyclerView (together with the also newly introduced Room database this is very useful) which can only be used in a separate tab for full performance (it needs to handle scrolling and can’t be nested within another scrollable container). Also imagine someone having a large number of address books (it already happens with 6 or more address books). People needed to scroll down very long or some people didn’t even know that there was a second section for CalDAV calendars and WebCal (they didn’t see it and didn’t know it was there). The titles did not change anyway - it was named CalDAV and CardDAV in earlier versions. We will maybe also use the additional space for more information in a second line under the title of a resource. I hope that clarifies some of our decisions!
DAVx5 exits after renaming an account
-
Just a short note:
Recently I had several times the situation that I had to rename an account in DAVx5. This worked fine so far, but immediately after the rename, each time DAVx5 exited. This is no major showstopper, as the renaming had been completed and the change is still there after restart… but might benefit from some review?As far as I remember this happened with the 3.1.1-gplay, when I had to import an account which had same name as an already present one. Sorry for this being somewhat imprecise, but I did not want to mess up my working config just to reproduce cleanly.
-
Cannot reproduce this. Are you sure that this happens for 3.1.1? In the latest versions, a few rare occasions of such a problem have been fixed.
If it happens for you, please provide exact steps to reproduce.
-
@rfc2822 No, I am not totally sure the upgrade to 3.1.1 was already installed when I observed this, might have happened on a phone where an upgrade got stuck. When you cannot reproduce it, and did some changes in that direction lately, I’d consider my observation invalid now and not worth investigating further.
