Get rid of double cache, filesystem checking for every tile fetch, swap out http interception for a fluttermap tileprovider that calls map_data, fix node rendering limit

This commit is contained in:
stopflock
2025-11-28 21:48:17 -06:00
parent 153377e9e6
commit df0377b41f
19 changed files with 228 additions and 45 deletions

View File

@@ -1,14 +1,18 @@
{
"1.5.2": {
"content": [
"• MAJOR: Fixed severe tile loading performance issue - eliminated expensive filesystem searches on every tile request",
"• IMPROVED: Smart cache routing - only checks offline cache when actually needed, dramatically improving browsing speed",
"• IMPROVED: Simplified tile loading architecture - replaced HTTP interception with clean TileProvider implementation",
"• IMPROVED: Cross-platform tile performance optimizations - better retry timing, request deduplication, queue management",
"• IMPROVED: Network status indicator now focuses only on surveillance data loading, not tile loading (tiles show their own progress)",
"• IMPROVED: Node limit behavior - buttons now show helpful messages instead of being disabled, encouraging users to zoom in for safe editing",
"• IMPROVED: Indicator positioning - network status and node limit indicators automatically move down when search bar is visible",
"• IMPROVED: Reduced complexity in cache management and state tracking",
"• FIXED: Max nodes setting now correctly limits rendering only (not data fetching) to prevent UI lag",
"• FIXED: New node limit indicator shows when not all devices are displayed due to rendering limit",
"• FIXED: Tile cache properly clears when switching between tile providers/types - no more mixed tiles",
"• FIXED: Network status indicator no longer shows false timeouts during surveillance data splitting operations",
"• FIXED: Eliminated potential conflicts between multiple cache layers"
"• FIXED: Network status indicator no longer shows false timeouts during surveillance data splitting operations"
]
},
"1.5.1": {