I'm ressurecting this thread a bit because I have another problem. Recently I've been able to start the tooltip skin (i.e. Tooltip.ini) hidden thanks to a (new, maybe?) option in Rainmeter.ini's skin section, called StartHidden
, and everything goes smoothly ... except for the fact that the built-in variables #CURRENTCONFIGX#
(and possibly even #CURRENTCONFIGWIDTH#
- although these don't interfere with the process here because their values are unchanged) are "behind" the mouse movement actions, from a timeline point of view.
In other words, if I move the parent skin on the screen and then quickly
hover over the relevant text, the tooltip (i.e. Tooltip.ini) skin's coordinates (and thus, #CURRENTCONFIGX#
values) don't update
according to the parent skin's last actual position, but to values from the recent past, resulting in the tooltip being shown in a past position from the dragging trajectory of its parent skin. However, if I move the the parent skin, wait a bit
, and only then hover to show the tooltip skin, all works well and the tooltip is shown according to its parent skin's actual position.
So, this begs the question: why are #CURRENTCONFIGX#
not updated to reflect their correct values in case of fast mouse movements / actions? Also, what can be done to correct this issue?
This is my (updated) skin:
And the code, if you don't want to download/install it (the files should exist in 2 subfolders - Skin
- of a normal skin folder):
And yes, I've used DynamicVariables=1
properly, so it's not that. You can see the parent skin's (correct or incorrect, depending on circumstances) position by checking the ParentX
variables from the Tooltip.ini file.
You do not have the required permissions to view the files attached to this post.