Currently we are trying to implement a SFSchedule timeline and month view that show some issues on larger screensizes and when rotating.
The timeline has an issue regarding the width of the timeslots. We have set the DayCount to 7 days and the TimeInterval to 1440 (1 day per timeslot), but this doesn't make it fill all available space. This is especially noticeable on larger devices or landscape mode (see screenshot in attached zip file). Is there a way to make the timeline fill the available space (evenly spaced out per timeslot) if it ends up being smaller than the screen estate?
The second issue is with the month view. Whenever we rotate the already open month view most views resize properly, but the week number labels seems to resize improperly. Is there any way this can be fixed?
timelineViewSettings.DaysCount = 7;
SFSchedule.TimeInterval = 1440;
SFSchedule.TimeIntervalHeight = -1; |
Thank you very much. `SFSchedule.TimeIntervalHeight = -1;` seemed to do the trick for iOS! (Still need to get it to work for Xamarin.Android, where it doesn't seem to work as well)
I'll await November 2 for the orientation issue
To add to the screen size issue (I'm not sure if I should open a separate thread for this one or not): Is there a way to make the scroll content inset of the SFSchedule start at the iOS safe area instead of the start of the view?
For certain views (such as UIScrollView) this happens automatically or can be solved by adjusting some kind of content inset, but such a value doesn't seem present for SFSchedule.
This causes an issue on (for example) devices with a notch, as can be seen in attached screenshots 1-1 and 1-2. The content goes under the notch.
I can adjust the entire SFSchedule view (rather than just the scroll inset) to anchor to the safe area using the following constraints:
Schedule.LeftAnchor.ConstraintEqualTo(View.SafeAreaLayoutGuide.LeftAnchor)
Schedule.RightAnchor.ConstraintEqualTo(View.SafeAreaLayoutGuide.RightAnchor)
This does solve the content going under the notch, for example (see screenshot 2-1 and 2-2). But since the view gets cut off at the start and end of the safe area this gets quite ugly in terms of scroll animation. since the content just disappears when it exits the safe area rather than scrolling neatly behind the overlays.
Thank you very much. I will keep an eye out for the weekly nuget release!
I will open a separate thread for the safe area issue (since it seems to be unrelated to the orientation issue)