[rheathParticipant]

Hi Peter.

It’s an issue for my users as they are being shown the green tick indicator that shows it is a valid move and are confused when it doesn’t work.

If this isn’t supported in the the grid that’s cool, but could you show a different indicator, maybe a red cross to indicate this to users? Alternatively it would be great to still get the event, so I can handle the move in my code.

Thanks,

Richard

[rheathParticipant]

Hi Peter,

With the renderer callback, I needed to add the <br> breaks myself. Is this the approach you are referring to? For me, this meant calculating the width of text to see where the breaks needed to go. As calculating the width of text is slow (unless you’re using a fixed width font!), I found it was better to let the browser wrap the text naturally and then set the height.

Another useful trick is, I used zero-width spaces (&#8203) to hint where the browser should wrap long, non-space-containing strings. In my case this is after _ and on camel case. This would allow

California_San_Diego_MeassureOne3 to be wrapped like this when space was tight

California_
San_Diego_
Measure
OneTwo3

and

California_San_Diego_
MeasureOneTwo3

when there was more width.

In situations where you know your column names, widths and grid size, I can see the column renderer callback being fine, but as my grid size and columns are dynamic, I needed to get a bit more creative to match the behavior elsewhere!

Thanks,

Richard

[rheathParticipant]

Summary of suggestions and bugs. Most are not critical, but would be nice to bring jqxGrid in line with the best bits of other grid controls.

Suggestions

1. Enhance groupsrenderer to allow per cell group summaries
2. CSS class to grouping summary row
3. Add column definition options to documentation API
4. Preload x rows before and after currently displayed rows
5. Column header wrapping
6. Separate height for grouping summary rows
7. Selection of multiple rows in a single call
8. Scroll event
9. Pin grouping expand / collapse arrows to left
10. Default to column definitions if datafields not on adapter
11. Support drag scroll for Windows touch, like iPad

Bugs

1. Call groupsrenderer less aggressively
2. Ensure horizontal scrollbar isn’t shown unless needed
3. Column reordering broken on Windows touch in Chrome & Edge
4. Missing cellrenderer param (sometimes)

Let me know if I can provide any more feedback.

[Author]

Posts