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

Full View is not Rendered #23

Closed
dakshitagrawal opened this issue May 14, 2017 · 8 comments · Fixed by #33
Closed

Full View is not Rendered #23

dakshitagrawal opened this issue May 14, 2017 · 8 comments · Fixed by #33
Assignees
Milestone

Comments

@dakshitagrawal
Copy link
Member

When the cell size of the grid is very large, there is space left on the right. The problem could be in the bleed values.

@dakshitagrawal dakshitagrawal added this to the Summer Sprint milestone May 14, 2017
@suyashmahar
Copy link
Member

suyashmahar commented May 14, 2017

@dakshitagrawal97 I believe 2.2 section of Documentation explains this 2.2 Details of Bleed and Grid dimensions

@dakshitagrawal
Copy link
Member Author

@suyashmahar the 2.2 section states that the total area visible is (gridHeight + bleedY)*(gridWidth + bleedX). The app has the gridHeight and width set to match parent. There is a padding of 16dp and margin of 8dp. BleedX and BleedY have been set to 50dp. Hence, there should not be any space left.

@suyashmahar
Copy link
Member

suyashmahar commented May 14, 2017

@dakshitagrawal97

Bleed: Bleed defines the dimensions of extra size that TrianglifyView view generate so that triangles on the edge doesn't appear to be chopped off. In most of the cases min{bleedX, bleedY} > cellSize would ensure that the view is completely filled.

I was referring to the emphasized part, It says when cell size is large such that above inequality doesn't holds true, view will show white spaces. However we can make sure that above inequality holds true in our demo app.

@suyashmahar
Copy link
Member

@dakshitagrawal97 I think the issue has been addressed.

@dakshitagrawal
Copy link
Member Author

dakshitagrawal commented May 14, 2017

@suyashmahar Yes, I overlooked that part. We should add the inequality checker on our part though.

@suyashmahar
Copy link
Member

@dakshitagrawal97 I don't think that would be a good idea we should not control every aspect of trianglify behavior. User should be in control of every thing, though we can make it optional.

@dakshitagrawal
Copy link
Member Author

dakshitagrawal commented May 14, 2017

@suyashmahar The user would want that the view is filled completely into the space that is designated to the view. We can give a toast message to notify the user of the problem so that he can rectify it on his own. For the app, we should take care of it from our side.

@suyashmahar
Copy link
Member

@dakshitagrawal97 Showing toast notification or messages from library is a bad idea, however handling in our app seems right.

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

Successfully merging a pull request may close this issue.

2 participants