How to increase a scrolling speed in Makie menu - scroll

I am using Makie's menu with 30 items. However, the scrolling speed is annoyingly slow: I have to scroll 5 times with the mouse wheel just to move up one entry. Is there any way of changing this?

Related

touchpad double tap keeps moving very slightly (2mm) up and down while keeping my fingers on without moving them at all

touchpad double tap keeps very slightly (2mm) up and down while keeping my fingers on without moving them at all! Like when you scroll using both your fingers the page scrolls up or down as usual, BUT when you stop moving your fingers the page keeps shaking very slightly (few mm) up and down in a very annoying way and I have to take my fingers off the pad in order to stop this shaky behavior. the laptop is brand new out of the box with all recent updates but the issue persists! any suggestion?
Samsung galaxy book 2 360....running Windows 11
updating all drivers.
decreasing touchpad sensitivity
decreasing cursor speed
none has worked!

Chrome performances while scrolling in "device mode" - strange empty frames

During a touch scroll (scroll triggered then released to not introduce noise in the velocity decay) the scroll isn't always very smooth.
By analyzing the performances we can see sporadic gaps (empty frames). It seems nothing is going on during that time (see the screen capture attached).
What can be the root cause of such issue?
capture of gaps during a single touch scrolling

Custom infinite scrolling with items being removed while being scrolled out of view

The problem
Today's modern websites may use infinite scrolling technique to replace paged lists to make a more seamless experience to their users.
This is all nice and dandy as long as users don't scroll to far down which means that your document becomes very complex with huge amounts of DOM nodes. There are of course ways to mitigate this problem (i.e. replacing over-top overflowed scrolled elements with a single DIV of appropriate height for example), but they're either complex to implement and they still have their flaws.
The idea
I was thinking if anyone has already seen an implementation where items, that get scrolled out (top or bottom) somehow become smaller and fainter until they disappear and get replaced by its adjacent item.
I'm thinking of a mix of experience of:
scrolling
fading
scaling
Fading and scaling can be seen on Medium.com when you get to the bottom of any article and you click the next recommended one displayed below (click the title). When you do click and if you pay attention you can see the effect of original article disappearing while being replaced by an up-sliding new article.
Content scrolling could be done in this way and infinite scrolling would be much smoother and less resource consuming as elements would get replaced on the fly and in-place.
Number of simultaneously displayed items of course depends on items' size. In case of Medium-line articles it would likely be one article that would also scroll until you'd scroll it to the very bottom (or top). In case of posts like Facebook, it would be many more items simultaneously as they don't take as much vertical space.
Coverflow works in somewhat similar way as it displays middle content completely and rest is either hidden or scaled/transformed.
The question
Has anybody seen such an implementation on the web? If done properly it would actually make a much nicer infinite scrolling experience without hogging our browsers.
But to make my question more clear and non-debatable. Can you provide a working (albeit simplified) example of such experience?
Requirements:
when an item gets scrolled out it disappears (using fade/scale/both)
when items appear at the bottom (or top when scrolled up) they should display in the opposite to scrolled out items
pressing usual scrolling buttons Home, End, Page Up, Page Down and Space should work.
invisible items should be removed from DOM
scrolling should somehow be available using some sort of scrollbar as well
I think I might have found what you were looking for.
http://engineering.linkedin.com/linkedin-ipad-5-techniques-smooth-infinite-scrolling-html5

performance measurements on flex list (TileLayout)

I am doing some performance tuning on the item renderers in a list I have, so far I am listening to update-complete event to see when it is rendered for the first time.
However I would also like to measure the scrolling speed (when i change the viewport position the list blinks for a few seconds) , what event should i be listening too?
Thanks

Virtualizing horizontally and vertically for large grid

Is it possible to virtualize both horizontally and vertically?
All examples show one or the other.
Imagine a large grid like structure:
n amount of rows
and as many columns as there are hours in one month
At any one point only 4 rows maybe on screen showing only 2 columns (2 hours). Virtualization one way doesn't make sense. This is an up down / left to right scrollable grid.
I ask because I can't for life of me find any examples online? Also I can't find anyone else who has had the same query. Maybe the design in general is wrong or I don't quite know what I'm searching for.
I did think the design maybe wrong i.e. is there a better alternative but I don't think so. This planner-like-grid is required! The only other consideration I had was to dyanmically build pivot pages but this seems messy and won't have the same feel.
Can anyone begin to advise were I might look?
Whether right or wrong, the direction I'm going in is the following. I wanted to post one answer for any one stumbling across the question.
Using a grid, I'm creating a 2 x 2 grid. Top right, bottom left and bottom right will all contain scroll viewers. The scroll viewer in the bottom right when scrolled will dyanmically change the scroll position of the bottom left scroll viewer and top right scroll viewer. Similar scroll top right will dyanmically scroll bottom right, and bottom left will scroll bottom right.
Obviously a lot of scroll viewer bindings but this is one solution which will work in order to give me the planner functionality and layout.
In terms of the virtualization I am dyanmically going to queue controls in order to keep the performance decent, reusing controls where required.

Resources