Hm. Could be the operations queue got backlogged, stopping the UI from being able to load data in.
When that happens, check in the Settings tab’s Active Operations list. There should ideally be nothing in there, or only brief flashes of some work that finishes within seconds, then goes back to an empty list. If you see a lot of operations in there, or operations that show a time of a minute or more, that indicates things have got overloaded.
I’ve done some fixes to reduce the risk of that happening in the next build. I might have it ready in the next couple of days…
Heh. I think that’s only scratching the surface with the issues on that view
It was built as a very quick prototype, to get a feel for what it would look and feel like. Basically the entire UI of it (including the map) is still in the “proof of concept” stage.
At some point I’m going to have to sit down and dream up what I want the view to actually look like. Though before I get to that point I might still do some basic cleanup, like the points you identified there. As it stands now it’s actually kinda cool and interesting, so it’d be nice if it also presented the data accurately/correctly in each detail, regardless of whether it looks like final design and UI.
I’ll see if I can set aside some time to come back to it this week, and do some more cleanup on it. I won’t get to doing the proper design and UI yet, but yeah, would be nice to clean up the actual bits that are there now.
When I click on “Total Visits” and the list contains many entries, the display is slow: 30 seconds before 2000 entries appear and the scrolling of the list is not fluid but jerky. If I select an entry and click on “More”, the application returns to the “Place” page and freezes, the iphone (15 pro max) heats up and then the application crashes.
Yep, there’s some database query slowness in there. I’ve got that on my todos for this week to optimise.
Is that going into the Place Details view after tapping through to a Visit Details view from Place Details view? If so, I’m guessing the app is ending up with the visits list loaded twice, so taking up too much memory and getting terminated for memory use.
I’ll look into optimising that too. Though I think the recursive stacking of Visits List view might inevitably always hit a memory limit. But yeah, that could be handled better.
Yes, that’s exactly it. I think it’s the stacking of views that causes the crash. The crash doesn’t happen when the number of entries in the Total Visits view is low.
