Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReloadDates #36

Closed
krisanthony opened this issue Jun 1, 2016 · 5 comments
Closed

ReloadDates #36

krisanthony opened this issue Jun 1, 2016 · 5 comments
Assignees
Labels

Comments

@krisanthony
Copy link

I'm not sure if this is working correctly. I'm trying to scroll to a date, and select it (single selection) not by pressing on the date itself but by gesture. I have other logic in the didSelectDate implementation that prevents me from being able to trigger the delegate call.

So I have

calendar.scrollToDate(date)
calendar.selectDates([date], triggerSelectionDelegate: false)
calendar.reloadDates([selectedDate])

where selectedDate is the previously selected date, however it is not reloaded, and remains selected. Any ideas?

@patchthecode patchthecode self-assigned this Jun 1, 2016
@patchthecode
Copy link
Owner

Checking this out now.

@patchthecode
Copy link
Owner

I am not understanding what you are trying to accomplish.

Just so i understand this.
You want to:

  1. Scroll to a date
  2. Select the date with code
  3. Reload the selected date

And my question is, why?
If your objective is to select a date and scroll to it, then just do

  1. calendar.scrollToDate(date)
  2. calendar.selectDates([date], triggerSelectionDelegate: false)

Maybe if you describe an overview of what you are trying to do, then I can help you more.

@krisanthony
Copy link
Author

I made that more confusing than it needed to be. Basically. I am wanting to scroll to and select a date different than the one already selected. However, with single selection enabled, the previously selected date does not deselect if you have 'triggerSelectedDelegate: false'

@patchthecode
Copy link
Owner

This should be working correctly.
Tell you what, I will not look into this because I have a new version being released over the weekend.
I do not see the issue you mentioned occurring in it, so it's possible that the issue is resolved in the new version. Will release it in a couple hours.

@patchthecode
Copy link
Owner

New version released. Reopen this issue if it is still occurring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants