Closed daattali closed 2 years ago
This was happening because of the fit=TRUE
parameter of timevis()
. If you would have set fit=FALSE
or if you would have added %>% setOptions(start=..., end=...)
then it would have worked.
I fixed it by setting fit=FALSE
if start or end are provided. FYI this wasn't a regression, this never worked previously either.
Thanks for investigating!
I'm not sure what went wrong regarding my initial test (all items were shown).
Now it's working correctly. However, setting fit=TRUE
or fit=FALSE
doesn't make a difference neither for the CRAN version nor for the latest dev version. start
and end
are always respected.
Right, as I said the only way to fix this was to manually override the fix parameter to be FALSE whenever a start or end are provided. You can't respect both fit=TRUE and a start/end.
As reported by @ismirsehregal in https://github.com/daattali/timevis/issues/50#issuecomment-918999349