-
Notifications
You must be signed in to change notification settings - Fork 122
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
initDateDidChange() and scrolling layout malfunction in 2018-11-29 update. #40
Comments
Hi, Actually this fix is quite important to keep the width of each grid the same. I will look through this issue in the following weekend, and let you know soon. Thanks |
Wonderful, thank you. |
Hello. I've looked through your problem, but I am sorry that I cannot find any solutions yet.
Hopefully these opinions can help you to solve your issues. Thanks, |
Hello again! Sorry for taking so long, I've had much to do besides programming. Thanks very much for your notes, I have looked through them and here comes a little update. A few of the problems seems to have disappeared with the newer versions by the way. I've not a native English speaker myself so the explanations may be a bit weird, hehe. However I have looked further into this and narrowed down the problem. The code that creates the issue lies in JZBaseWeekView.swift. Current issue update (using the same code to setup as above):
I'll continue to see if I can find out why the initDate isn't set properly, when scrolling left. |
Hi. I tested this on the current example project and everything works fine, but probably I misunderstand your meaning. However, I think before you go further, maybe you can try the example project and set a break point to the If you find the example project still exists this problem, which means I do it wrong way. Let me know. Thanks |
Of course i'll try that, you are probably right. I strongly believe I might be doing something wrong here too. Since the bug would be noticed very quickly if it was from the library itself, the reason i posted was just that the update seems to have caused for me. I shall try out the example project and as well more closely examine the changes from my cached version of the library. |
Hello again! I have narrowed down the issue. Or at least I've found what caused it for me. I went through all commits til I found the one without the issue and I after that I compared the code in JZBaseWeekView.swift and noticed that if I use the latest version of the library but then comment out the flowLayout.rowHeaderWidth property change everything works as expected. I have yet to find the culprit... I have tested to change back from my custom views one by one, but that isn't causing. Well I'm gonna investigate further. But I believe it must have something to do with my implementation. To demonstrate the change:
Thanks for your help and interest in the issue! |
Are you changing the rowHeaderWidth in another place? I think you might change this width in somewhere else, then it causes your issues. |
Hi mate, I think the latest v0.7.0 should resolve your issue. If you are still interested, could you have a try and let me know? I completely redesign the pagination effect in this release. You find the release comments here |
Introduction
Hello, i've been using this library since end of august this year and loving every moment of it. However after updating the library 15 days ago (when 16cf27b ) was merged, i got the following problems which forced me to reverse to the version i had before (whatever version that running 23 nov 2018).
Context
JZLongPressWeekView
that I use as well as the setup method for the calendar in my view controller. I get the same issue even if i change back to using the supplementary views that come with the library!Actual issue
initDateDidChange(_ weekView: JZBaseWeekView, initDate: Date)
does not get called when i scroll to change page.Code
JZLongPressWeekView subclass:
Setup in view controller: where
weekCalendar : WeekCalendarViewModel
called inviewDidLoad()
and I perform aforceReload()
with new events inviewWillAppear()
.initDidChange():
Am I alone with this issue and need to debug further? Or did something change in the library that might have introduced this bug? Have I provided enough information?
Thanks for your time!
The text was updated successfully, but these errors were encountered: