You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One with a huge a complicated menu, traversing of which on every launch would show a visible lag. It might be better to always use the cached version (with maybe manual reset on rare app updates) to get no lag (even though you might miss some dynamic menu items)
One with a small menu, where the lag is smaller than typing the menu item. In this case there is no point in using cache since it's imperceptible
Would it be possible to add a config that for some selected apps in the first category would allow setting custom cache option (always use if exists) with custom menu/sub-menu depth (you'd basically set each to ∞ since it's only used once per app and then cached)?
(maybe cache could be auto-invalidated when app version changes, but that might be an unnecessary overcomplication)
Another potential improvement to get the best of both worlds (caching and dynamic items): is it possible to parse the whole menu only once, but also store specific paths that are dynamic and on each launch only update those paths while reading everything else from cache?
The text was updated successfully, but these errors were encountered:
Let's say there are two types of apps:
Would it be possible to add a config that for some selected apps in the first category would allow setting custom cache option (always use if exists) with custom menu/sub-menu depth (you'd basically set each to ∞ since it's only used once per app and then cached)?
(maybe cache could be auto-invalidated when app version changes, but that might be an unnecessary overcomplication)
Another potential improvement to get the best of both worlds (caching and dynamic items): is it possible to parse the whole menu only once, but also store specific paths that are dynamic and on each launch only update those paths while reading everything else from cache?
The text was updated successfully, but these errors were encountered: