Grid rows not filling the screen...

[Jaymer]

I've always wondered how others accomplish this (if at all).

I make a Query and I have to specify 20 rows, for example.
Then my customer has a user with a "large" screen and they could fit 35 rows.
But the grid is hardcoded for 20.

Why can't Aware/Kendo figure this out and just fill all of available vertical space with data?
The pulldown where you specify 10,25,50,Unlimited... couldn't it say "Use Available" ?

And then for the user who uses the system with a smaller laptop gets a scrollbar because only 18 or 19 fit.

Either I've done something wrong for years and haven't see the way to correct this, or everyone has this issue?

A new 8.5 option stretches a Form to align with the bottom of the screen, but I haven't see the value in that yet.

Screen Shot 2020-08-25 at 3.17.53 PM.png (3.68 KiB) Viewed 14016 times

[BenchmarkDan]

Agree, this is an issue. Difficult to explain to users.

I have tried to use the Display Settings on Standard Grid to give the user some control; but no luck.

Display Settings on Standard Grid
The display x (rows) per page;
Options are 20,30,40,50,Unlimited. These selections might be helpful - if the user could select them.

After publishing, the rows per page provided to the user are:
All, 5,10,20 - not very helpful. Why do these change when published?

Of course the best option is Jaymer's suggestion.

[ACDC]

I use this user-driven row setting :

[BenchmarkDan]

Checking the box "Allow user to specify..." has never worked for me.

Does it allow you to override the "items per page" dropdown?

[PointsWell]

I raised this issue with Vlad almost 2 years ago and was advised it is not something easily fixed.

The route I have taken is to do some analysis on what the grid is expected to show and the frequency of those records occurring. Make a sizing estimate and then pull back double that. Most times it will be over generous and you might have some edge cases where the query doesn't return all the records and shows a paging bar.

[Jaymer]

the options for 5,10,20 are worthless.
i've used JS to override those to 25,35,45,100 for example, so more rows could fill the screen.
but its lost everytime you come back to the grid.
not the "smart" fill that I'd like to see.

[ACDC]

Checking the box "Allow user to specify..." has never worked for me.

This works in ver 7.1 in both query and form grids

[PointsWell]

Am I missing something? Overtype the field with 500.

Screen Shot 2020-08-27 at 10.04.50.png (25.67 KiB) Viewed 13945 times

[BenchmarkDan]

Check box: "Allow USER to specify size of page returned by query."

"Display 5000 per page" This gives ALL users 5000, 5, 10 and 20. And if they change from 5000 to 20 - they cannot get back to 5000.

I was thinking "Allow USER to specify size of page returned by query." means each user.

"Items per page" This what I expected the user to be able to change. Different users, different monitors, different eyeglasses.

Multiple other systems I have worked with allow this as an option. Very helpful when there is no auto scaling of the displayed page. That is where my mind went.
Obviously - I'm on the wrong page. Thanks for comments.

[tford]

Sorry, not following Dan. How did you solve this in the end?

[BenchmarkDan]

No I haven't Tom. Currently dealing with a worst case scenario.

The food bank is all volunteers (myself included), we have a lot of old (donated) monitors and a few new ones with high resolution. Volunteers:some young - like a lot of records per page (smaller font is no issue), many older that want a larger font. Then the fun starts, they start cranking the browser plus & minus keys.

Jaymer's suggestion is probably the only thing that will really work here.

But for other projects - wish Aware would at least change the 5,10,20 defaults to something more useful - and let you get back to your original selection for items per page. I could live with that.

[johntalbott]

You can adjust user selected page sizes in the Init Script of the query. Example:

config.pageable.pageSizes = [10, 25, 50, 100, 500, "all"]

[Jaymer]

I told dan that on the phone.
I have done this.
Not even a solution to the original problem... or his problem, because it will revert to what is defined in the query when redrawn next 5ime.
This needs to be fixed by Aware. But with no one pushing that this is a big UI issue, then there’s no reason to fix it.
Will take some effort - sure... Some math to determine how many rows will fit in the viewport and set appropriate pagesize.

Prolly won’t work when Bruce wraps long text in the same column. But for a majority of simple 1-line height grids, certainly it can be done.

[customaware]

We used this in the Initialization Script of the Query to specify which options we want the user to be able to choose from.
The default is still set in the Display As Standard Grid option.

config.pageable.pageSizes = [10, 20, 25, 30, 50];

While Aware cannot yet display only the number of rows that fit the current screen, we usually set it to 20, 30 or 50 depending on the app.

[johntalbott]

https://docs.telerik.com/kendo-ui/knowl ... -to-height