| 3 | | - Two Terminals teams is due to the fork: the exec are not yet done for the child team... |
| 4 | | - after an exec done by a team already detected in previous cycle, the team name and/or icon is not updated according to the new running image |
| 5 | | - depending on when the icon is retrieved, it could be the one from before or after the exec. As this retrieval is done in a lazy way (at drawing time), it would explain why the end icon is not always either wrong or right. In the Terminal icon case, it's either the (just) forked Terminal icon or the (new) /bin/bash (generic app icon) which was exec'ed in its place. |
| | 3 | - Two Terminals teams, due to the fork: the exec are not yet done for the child team... |
| | 4 | - after an exec done by a team already detected in previous cycle, the team name and/or icon is not updated according to the new running image and still show its former parent attributes. |
| | 5 | - depending on when the icon is retrieved, it could be the one from before or after the exec: icon is retrieved in a lazy/deferred way (at drawing time), it would explain why the end icon is not always either wrong or right. In this Terminal icon case, it's either the (just) forked Terminal icon or the (new) /bin/bash (generic app icon) which was exec'ed in its place. |
