Bruno Windels 3dbf5e727d process in incoming order (reverse-chronological order if backward) ...

makes code simpler, don't need fix to undo reverse ordering of
nonOverlappingEvents. reverse looking is very likely premature
optimization as well.

2019-06-03 00:18:52 +02:00

..

entries

fix fragmentId:0 being evaluated as falsy

2019-06-02 19:27:23 +02:00

persistence

process in incoming order (reverse-chronological order if backward)

2019-06-03 00:18:52 +02:00

common.js

fix fragmentId:0 being evaluated as falsy

2019-06-02 19:27:23 +02:00

Direction.js

first round of fixes after running the app again in the browser!

2019-06-02 00:49:47 +02:00

EventKey.js

first draft of persistFragmentFill

2019-05-12 20:25:41 +02:00

FragmentIdComparer.js

fix fragmentId:0 being evaluated as falsy

2019-06-02 19:27:23 +02:00

Timeline.js

fix some gap fill errors

2019-06-02 15:46:24 +02:00