We currently use a cache tailedPids for two purposes:
The count of items is used to determine the location of the next tail window
If tail is re-invoked on a previously tailed window, to avoid repositioning it repeatedly (some scripts like work-for-faction re-tail themselves each time they perform focus work, or autopilot.js each time it launches a script).
The problem is this "global memory" cache isn't reset when we install augmentations, so since most startup scripts will get low PIDs (1,2,3...), which are probably in the cache, they won't get properly resized or positioned.
We either need a way to clear the cache on reset, or find a different mechanic to keeping previously tailed windows stable. The original solution hashed the processId to produce a deterministic number, and used that number to pick one of a series of designated positions, but the random nature of this approach might lead to a poor distribution of tail windows.
We currently use a cache
tailedPidsfor two purposes:The problem is this "global memory" cache isn't reset when we install augmentations, so since most startup scripts will get low PIDs (1,2,3...), which are probably in the cache, they won't get properly resized or positioned.
We either need a way to clear the cache on reset, or find a different mechanic to keeping previously tailed windows stable. The original solution hashed the processId to produce a deterministic number, and used that number to pick one of a series of designated positions, but the random nature of this approach might lead to a poor distribution of tail windows.