If I set the <Lifespan> value on settings.ini to be 300ms, for example, it shows up for the 300ms when reloading the settings (because it is not switching desktop), or displaying a 'pinned window' tooltip. When switching desktops, however, it doesn't appear at all.
I believe this behavior occurs because the lifespan value starts being recorded when a command is executed, and not when the tooltip is first displayed. So actions that require the desktop change animation will delay the tooltip from appearing, shortening its lifespan
A fix for this would be to give <Lifespan> a higher value to make the tooltip stay on screen for longer. In turn, it will make it so that 'pinned window' tooltips stay on screen for that extra time longer (around 400ms on my machine).
If possible, the lifespan value should only start counting when the tooltip is displayed on screen.
If I set the <Lifespan> value on settings.ini to be 300ms, for example, it shows up for the 300ms when reloading the settings (because it is not switching desktop), or displaying a 'pinned window' tooltip. When switching desktops, however, it doesn't appear at all. I believe this behavior occurs because the lifespan value starts being recorded when a command is executed, and not when the tooltip is first displayed. So actions that require the desktop change animation will delay the tooltip from appearing, shortening its lifespan
A fix for this would be to give <Lifespan> a higher value to make the tooltip stay on screen for longer. In turn, it will make it so that 'pinned window' tooltips stay on screen for that extra time longer (around 400ms on my machine).
If possible, the lifespan value should only start counting when the tooltip is displayed on screen.