-
Notifications
You must be signed in to change notification settings - Fork 21
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
Landscape support doesn't work as expected #4
Comments
Thanks for reporting. I think this is a design problem and it’s better to just maintain a seven item per row setting. I have two ideas to approach this:
Ideas? Do you have a mock / composition that shows use of this component in landscape for more context? Thanks! On Jul 7, 2013, at 12:45 AM, Aaron Kavlie [email protected] wrote:
|
The sample app linked in the repo's README shows the problem in the simulator. See the attachment. For my purposes just a horizontal stretch would be better; perhaps it could be an option. Also, Autolayout may work well for this, rather than hard-coded cell sizes, as there are two different screen widths to deal with, and if you decide to put a view on the side of the calendar (which I may do in landscape), that would be yet another dimension that varies from the standard portrait width that this was designed for. |
btw, I plan to modify the design quite a bit, to be somewhat similar to Apple's iOS 7 calendar design (though not exactly). Boxes won't be visible. |
Is there any code resolved for this issue. I am working with the same problem with landscape mode? I have it showing 7 cells in landscape but probably did not use the best method to fix this. Also the calendar seems to jump back 2 months each time I rotate to landscape. Thanks you. Darin |
In landscape, DayFlow's day tiles continue beyond the standard layout (7 days per row) that one would expect in a calendar. There are 10 tiles per row in landscape.
Instead, it should stretch each tile horizontally to maintain one week per row.
The text was updated successfully, but these errors were encountered: