Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
goToCurrentTime does not work correctly
See original GitHub issueDescribe the bug
When using goToCurrentTime only the scroll of goToHour is executed but goToDate is ignored.
To Reproduce Steps to reproduce the behavior:
- Scroll away from current time and current date
- Invoke method call for
goToCurrentTime - Now the view scrolls to the correct time, but not the correct date
When using only goToDate(Calendar.getInstance()) scrolling to the current date works. Therefore, it seems that goToHour ‘overrides’ the scroll of goToDate.
Additional context
- Android version: 10
- Samsung Tablet
- WeekView version: 5.0.1
Further idea as an improvement:
goToHour throws an exception, when the hour is outside of minHour and maxHour. I think the implementation would be more convenient, when the method just moves the hour into the range between minHour and maxHour. Like in the following java code:
Math.min(Math.max(goToHour, weekView.getMinHour()), weekView.getMaxHour())
Similar to toToDate, where the date is adjusted first.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
And thanks again for the fast fix release.
Yes,
scrollToDateTimeshould cover the use case I described in (2.)