-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Broadcast - Use GridView.builder instead of ListView.builder #867
base: main
Are you sure you want to change the base?
Conversation
); | ||
child: Padding( | ||
padding: Styles.bodyPadding, | ||
child: GridView.builder( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The number of elements is not that large, I wonder if the GridView.count
would be more appropriate? The code would be a little easier to read I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know how it would affect performances. According to the GridView.builder
documentation the builder is called only for those children that are actually visible
. From what I understand the GridView.count
will create all widgets at once but it will only render them when they are visible on the screen whereas the GridView.builder
will create only the widgets that are needed.
Does the number of elements that is not that large applies to the puzzles too ?
Looks like you based this PR on the websocket branch. You should base it on main branch so I can only review the changes related to the |
Ah I thought you would review this after the websocket PR. You can view the changes related only to the |
2d609cf
to
748de56
Compare
No description provided.