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

Deprecate Ext.Net.BufferedRenderer (now private on ExtJS) #1484

Closed
fabriciomurta opened this issue May 26, 2017 · 1 comment
Closed

Deprecate Ext.Net.BufferedRenderer (now private on ExtJS) #1484

fabriciomurta opened this issue May 26, 2017 · 1 comment
Assignees
Milestone

Comments

@fabriciomurta
Copy link
Contributor

fabriciomurta commented May 26, 2017

Found: 4.2.1
Ext.NET forum thread: BufferedScrolling Bug

The GridPanel's BufferedRenderer plug in is currently private in ExtJS. This means it may no longer be exported to userspace, as it may break without further notice, unless hiding it hinders intrinsic features.

In fact, it seems now just referencing it from code is resulting in inconsistent code as reported in the thread above, if locking columns in the grid. The same and working result can be achieved if the plug in is commented out and its options passed directly to the store definition (if any).

The correct way to enable buffered rendering (which is true by default) now is by setting the grid panel's BufferedRenderer setting to true (also documented in ExtJS).

So the plug in should be marked as deprecated/obsolete and removed from the next major release.

@fabriciomurta fabriciomurta added this to the 4.3.0 milestone May 26, 2017
@fabriciomurta fabriciomurta self-assigned this May 26, 2017
@geoffreymcgill geoffreymcgill modified the milestones: 4.3.0, 4.3.1, 4.4.0, 4.5.0 Aug 2, 2017
@geoffreymcgill geoffreymcgill modified the milestones: 4.5.0, 4.x Oct 11, 2017
@fabriciomurta fabriciomurta modified the milestones: 4.x, 4.7.1, 4.3.0 Aug 29, 2019
@fabriciomurta
Copy link
Contributor Author

This has been marked as deprecated since 4.3.0 and left open by mistake.

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

No branches or pull requests

2 participants