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
Please check that this issue hasn't been reported before.
I searched previous Bug Reports didn't find any similar reports.
Expected Behavior
When I move a task with the 'Move block and push neighboring blocks' handle in the Week Planner (regardless of how many days I'm showing), it should only affect that day's tasks.
Current behaviour
It actually pushes tasks/blocks from surrounding days too, whatever is in view.
Steps to reproduce
Schedule tasks on different days at different times, then view those days in Week Planner. Use the noted handle to drag one block past where a block is scheduled on a different day, and it will be pushed.
Which Operating Systems are you using?
Android
iPhone/iPad
Linux
macOS
Windows
Obsidian Version
1.7.5
Possible solution
No response
The text was updated successfully, but these errors were encountered:
The bug is here: getEndMinutes(previous) > getMinutesSinceMidnight(current.startTime)
let's say you have 2 tasks on 2 different day. task one from 7:50 - 8:10, task two is at 8:00. But since task A is on a different day, B should not get pushed. But minutes since mid night of 8:10 is greater than those of 8:00, this will cause B to be pushed.
Please check that this issue hasn't been reported before.
Expected Behavior
When I move a task with the 'Move block and push neighboring blocks' handle in the Week Planner (regardless of how many days I'm showing), it should only affect that day's tasks.
Current behaviour
It actually pushes tasks/blocks from surrounding days too, whatever is in view.
Steps to reproduce
Schedule tasks on different days at different times, then view those days in Week Planner. Use the noted handle to drag one block past where a block is scheduled on a different day, and it will be pushed.
Which Operating Systems are you using?
Obsidian Version
1.7.5
Possible solution
No response
The text was updated successfully, but these errors were encountered: