feat: Implement Advanced Log Filtering and UI/UX Improvements #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a powerful and scalable filtering system to the application, allowing users to efficiently navigate large datasets. Key UI/UX enhancements have also been implemented to improve data visibility and interaction, including a more discernible traffic polyline on the map, a more informative trip ID column in the log table.
Key Features & Changes:
Advanced Log Filtering System:
LogTable,Map,TimeSlider) and navigation controls (Next/Previousbuttons) now respect the active filters, ensuring a consistent and intuitive experience across the entire application.Enhanced Traffic Polyline Visibility:
TrafficPolylinecomponent now renders a "casing", a wider, semi-transparent black line underneath the main colored traffic line. This border effect improves the visibility of the planned route against complex map tiles.LogTable Header Update:
Map Click Accuracy Fix:
locationinstead ofrawlocationfor its proximity search, which is means it can also match trip events. Useful when the user is filtering to just trip events.