I have skin that just has thirteen image meters, thirteen text meters and one shape meter used as a button.
This shows me all the current colors from the Chameleon plugin and their variable names. (see code in spoiler below. Second spoiler has "BackColor.inc" variable include file)
The only meter with a tooltip is the shape meter, but ALL the meters, text, shape and image, show this same tooltip!
I have tried adding ToolTipText="" and ToolTipHidden=1 to all the other meters, but it still shows on all the meters!
[Variables]
Font=Fira Sans
Font2=LCDMono2
Size=14
Weight=300
Weight2=700
; Text colors for entire suite. [Bracketed] ones are from Chameleon plugin meters below
TextColor=[LT1]
TextColor2=[LT2]
; Inner background rectangle color for entire suite
AllOuterColor=255,255,255,40
AllBackColor=[DK2]
; Icon Hover color for launcher & LauncherClone
; Black
;HoverColor=0,0,0,255
; Yellow
;HoverColor=255,255,0,255
; Red
;HoverColor=255,0,0,255
; White
;HoverColor=255,255,255,255
; Blue
;HoverColor=0,0,255,255
; Light Blue
;HoverColor=80,241,255,255
; Purple
HoverColor=200,120,255,255
; DriveBack color for hard drive and CPU meters
DriveBack=0,0,0,100
; Line Color, both TopBars and SideBars
LineColor=200,200,200,60
[ChameleonDesktop]
Measure=Plugin
Plugin=Chameleon
Type=Desktop
; below are the Meters used to change colors with wallpaper in all suite Skins.
; To see a pallete showing all of the colors available, open ColorScheme.ini
[BG1]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Background1
[BG2]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Background2
[FG1]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Background2
[FG2]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Background2
[LT1]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Light1
[LT2]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Light2
[LT3]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Light3
[LT4]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Light4
[DK1]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Dark1
[DK2]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Dark2
[DK3]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Dark3
[DK4]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Dark4
[Aver]
Measure=Plugin
Plugin=Chameleon
Parent=ChameleonDesktop
Color=Average
Last edited by DanDaBear on April 28th, 2018, 4:26 am, edited 1 time in total.
[QuitButton]
meter=Shape
X=25
Y=335
Shape=Ellipse 0,0,10 | Fill Color #MyFillColor# | Stroke Color #BorderColor#
MouseOverAction=[!SetVariable MyFillColor 60,160,10][!SetVariable BorderColor 255,255,0,125][!UpdateMeter #CurrentSection#][!Redraw]
MouseLeaveAction=[!SetVariable MyFillColor #TextColor#50][!SetVariable BorderColor 0,0,0,125][!UpdateMeter #CurrentSection#][!Redraw]
ToolTipText=Close Me
LeftMouseUpAction=[!DeactivateConfig "Bordered2Tears\ColorScheme"]
AntiAlias=1
DynamicVariables=1
Remove all TooltipHidden=1 from all meters; that line should be in the [Rainmeter] section. You can place it there, and control all tooltips in your skin.
eclectic-tech was on the right track and close, but really the Shape meter should look like:
X=25
Y=335
Shape=Ellipse 10,10,10 | ...
With Ellipse, you want Ellipse CenterX, CenterY, Radius. With CentrerX and CenterY defining the center of the ellipse you want to draw.
The shape is drawn centered on the position defined by CenterX and CenterY. In a sense, it draws from the center out.
Generally, don't use CenterX and CenterY to position the meter in the skin, that isn't the point of them. Use X and Y on the meter. You can use CenterX and CenterY to position an ellipse in the context of other shapes in a Shape meter, but you will get some weird behavior if you use them to position the ellipse in the context of the skin.
I will have to dig a bit, but I think you may be on to something, that doing that can give you some issues with ToolTipText and where it is detected. What it looks like is that ToolTipText is not behaving with the Shape meter they way other mouse actions are designed to, where it is only detected on "solid" bits of the Shape meter. It seems to be using the method used by other meters, where the mouse detection is on the "meter" and not the "content of the meter".
So, the CenterX and CenterY are relative to the shape meter itself, Not the skin.
It's not very clear in the manual.
It is working correctly now with the meter X and Y used to position the shape meter
and the CenterX and CenterY used to position the center of the ellipse within the shape meter.
The tooltip now only shows when mouse is over the shape.
Thank you to both Balala and JSMorley
I've stolen borrowed many a code snippet from you guys! (like the WXD Weather parser variables)
Yes, all the "position" elements in the definition of the shapes are relative to the "meter", not the "skin".
However, I don't want to overstate that case. I guess I'm saying it seems inefficient to position an ellipse with a radius of 10 at an X of 500 in the skin by setting the CenterX of the Ellipse at 480 or something. That will create a really large meter container for the shape, that I don't think you need.
The real issue in this case though, is that ToolTipText isn't working the way it should on a Shape meter. It should ignore the meter container, even if it is bizarrely large, and only be detected on the solid part of the "shape", not the "meter". We will have to dig into this a bit.
jsmorley wrote:Well, I don't want to overstate that case. I guess I'm saying it seems inefficient to position an ellipse with a radius of 10 at an X of 500 in the skin by setting the CenterX of the Ellipse at 480 or something. That will create a really large meter container for the shape, that I don't think you need.
The real issue in this case though, is that ToolTipText isn't working the way it should on a Shape meter. It should ignore the meter container, even if it is bizarrely large, and only be detected on the solid part of the "shape", not the "meter". We will have to dig into this a bit.
Could it be that there is a background section [SkinBack] that covers the entire skin? So even though the shape meter is not detecting the mouse over, there is still a non-transparent pixel under it that is triggering the tool tip...just a guess.
eclectic-tech wrote:Could it be that there is a background section [SkinBack] that covers the entire skin? So even though the shape meter is not detecting the mouse over, there is still a non-transparent pixel under it that is triggering the tool tip...just a guess.
Maybe ToolTipText was missed when we were changing the approach to mouse detection on the Shape meter, or maybe there is something particular about the tooltip functionality in Windows that makes it difficult or impossible to do this way, but we need to look into it.
Regarding tool tips, I notice a strange behavior that I don't remember seeing before beta v3043; when over a skin with a tool tip displayed, when I move the mouse away, the same tool tip flashes briefly at the new mouse location... very strange.