View Single Post
Old 01-19-2021, 01:48 PM   #279
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,203
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
If you have conditions (for chains) actually testing for selection count, you are not going to see much of difference as far as lag, because the old approach also made sure to calculate once when pressing the menu.

The new approach will make difference for people who do not use chain conditions with selection_count. It will also shorten the time between actions because the pre-calculation had to be repeated ahead of each action, regardless of action conditions.

Edit: Also you will notice the lag is proportionate to how many rows are selected when you press the menu.

Edit2: The lag comes from testing chain conditions before showing menu items. It is usually less than a second. Having a huge number of rows selected can make it longer, for people who have conditions using the selection_count().

Last edited by capink; 01-19-2021 at 01:58 PM.
capink is offline   Reply With Quote