You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Alarm import does not retain original sorted order (by 'creation date'). When exporting/importing the same list to several devices, each may display a different order.
To Reproduce
Add several alarms if the list is empty.
Sort by 'creation date'. Observe the order of the list.
Export alarms to file.
Clear the alarm list.
Import alarms (from recent export).
Sort by 'creation date'. Observe that the order of the list is now reversed.
Repeat steps 2-5, except sort by 'alarm time' before exporting.
After importing, sort by 'creation date'. Observe that the 'creation date' order is now a reverse of the previous 'alarm time' order.
Expected behavior
The alarm list should retain its 'creation date' order when exporting and importing.
Additional context
The bug originates during export - the list is exported in whatever order it is currently displayed.
Version Info:
Tested with 0.14.6.
The text was updated successfully, but these errors were encountered:
@Timo-Fi I found this bug thanks to your comments in #602. I don't think its directly related to that issue (but like a lot of things tangential). There are actually several confounding issues with that alarm list.
It sounds like there is still another bug out there though. One that causes recently added items (whether imported or otherwise) to fail if scheduled for the near future (~10 minutes).
Describe the bug
Alarm import does not retain original sorted order (by 'creation date'). When exporting/importing the same list to several devices, each may display a different order.
To Reproduce
Expected behavior
The alarm list should retain its 'creation date' order when exporting and importing.
Additional context
The bug originates during export - the list is exported in whatever order it is currently displayed.
Version Info:
Tested with
0.14.6
.The text was updated successfully, but these errors were encountered: