In order to use the browser level scroll instead of grid level scroll I made domLayout = 'autoHeight' which actually did what I wanted but it is crashing the browser is there any solution to this, I searched for this but didn't find any solution, if anyone have solution for this even a reference link would be helpful.
If you do this, you are getting rid of row virtualization, so you are actually loading as many rows you are passing at once, note that this is not an ag-grid limitation, this is just the fact that you are passing too much data and running out of memory
If you have too much data, in ag-grid you are going to have either pagination or scroll, so that the rows are virtualized and then you don't crash the browser
Hope this helps
Related
I am trying to implement multipage functionality with quill. I want to fix the height of each page, and when user reaches the end of page, instead of editor height to grow or scrollbar to appear, I want cursor to go to next page(editor), similar behaviour as observed in Google Docs or Microsoft word document.
I have already added 2 editors in the view, but not having any idea on how to switch to new page as cursor reaches the end of first page.
i come straight from google trying to figure out something similar with quill and as far as i know and as far as i came while researching this specific topic:
to me it seems as if its not possible with multiple editors since as soon as the user wants to select paragraphs/elements over a multi page span you'd have to figure out how to
make the selection actually possible (try to select content over a span of two div elements which both are "contenteditable"-enabled, which was one of my first tries kinda).
spread the selection on multiple editors (you'd have to keep track of how much the user selected and when and how far the selection is within which editor which is kinda tricky)
execute an action over multiple editors which will be especially hard since there is no thing as "shared toolbar" yet (as far as i know)
so i really hope (🙏) the time helped you to find an sharable 🤲 solution to this but as far as i built up my knowledge about quill so far (which is a bit over a few weeks old now).
what i will try in the near future is to add a new module to show a page break and style all other elements accordingly to simulate the look of a page.
I am having a problem with list/scroll views in big screens.
In the application there is a scroll component who queries for more rows when its end is reached. However, when the screen has big enough resolution, the initial query is not enough to generate the scroll bar, and thus, the event is never triggered.
The team agrees that because of the instability of the Dimensions module in React Native, a better solution would involve already implemented abstractions instead of getting the screen's dimension with the mentioned module.
What could be a good solution to the problem? I hope I was clear.
Thanks in advance.
My solution was to query when the 'layout' event was fired. I did this through the 'onLayout' and 'onContentSizeChange' props. They store the heights of the list and the component, which made me able to compare both and query for more data.
I'd consider myself advanced in getting smooth scrolling performance, but this has stumped me. I have a UICollectionViewController that shows pictures from the camera roll. It was working just fine, then I added sections to show additional albums, using a different layout. Since then, the scrolling performance became extremely choppy. Setting the sections back to 1, it gets a little better. I've not been able to determine what's holding things up, but I think it may be due to calculations in the layout (layoutAttributesForElementsInRect: and friends).
Now here's the strange part--if I push a view onto the navigation stack, then pop back to this collection view controller, it's perfectly smooth.
Nothing is modified other than pushing a view controller. The collection view controller is not dealloc'd or anything, and looks the same as before the push. Any ideas what could be causing this?
There appears to be a bug with subviews being kept around after layout changes.
We had issue with the Scrolling of the WPF datagrid. With some analysis found the ScrollViewer.CanContentScroll = true was the culprit. Removing and making it false, the scrolling issue was fixed. BUT yesterday i was analyzing a bug on increase in memory footprint of the WPF application to more than 1.3Gb due to binding a 50k records by mistake. Still it questioned the capabilities of binding even a 10k records. Users dont want pagination. ( its a requirement, cant do much about it!)
On further reader found setting ScrollViewer.CanContentScroll = false makes UI virtualization false. which is making WPF bind all the records and render it on the screen. Which results in exploded memory foot print and performance issues.
For now we thought if the records to be bound are minimal, then set the ScrollViewer.CanContentScroll= false, else set it true.
In short: we are either stuck with scrolling issue or UI virtualization. Is there something which can fix both? Have read about Data Virtualization but do we really need to go that far? am i missing anything out of the box from .net4.0 which could help us?
If you check out the accepted answer of this question... In the 'Choosing between them' section of the answer there is a suggested tip to set the visibility of a custom decorator to hidden when the item is not in view.
But other than that... you're right. You either get smooth scrolling or virtualization... not both.
Additionally, if you group items in your datagrid, check out this answer I posted a while back for a convenient performance improvement.
I'm using an ItemSelector with two lists like the second one from this demo:
http://dev.sencha.com/deploy/dev/examples/multiselect/multiselect-demo.html
I have around 600 items in my first list and the performance when I drag the scrollbars is unacceptable in Firefox 3.x. For some reason, IE7 is not a problem. Are there any optimizations than can be done so scrolling will be faster?
[Update]
Seems like the problem occurs when the widget is placed in a xtype: 'fieldset'
The problem goes away once the widget is moved out of the fieldset.
did you try disabling firebug ?
In the demo I can't see any events firing on scrolling up and down.
Possibly you have some set up in yours.
You could possibly override the renderer of the list to use fewer elements, it's currently three per item. Not holding out a huge amount of hope on that front however.
Your best solution is likely to find a way to not have 600 items displayed on the page at a time.