Yue wrote: ↑May 15th, 2023, 3:19 pm
Regarding the colors - I thought so. I guess you do that by variables for the colors implemented by styles? Coloring in the tooltip equal to the way in the "menu" would make the design look more consistent and, since you always have two meters, one for the value, one for the unit, which would be combined in one meter then, I guess it would spare you nearly half the code lines on that. On the other hand it would be a big rework I guess...
Regarding the raising questions when there are more values I do not see the problem - the coloring [more or less] would be decided by the coloring in the menu.
Yes, the colors are controlled by variables that are applied in the styles, but the coloring in the "menu" (the little bar at the top, which is actually the main skin) is different from the coloring in the "tooltip" (the bigger skin at the bottom where details are shown on hover over the main skin's white title), because their structure is different. In the "menu" I have 4 or less meters that are sometimes merged depending on the length of what needs to be displayed in that skin (for the Processor one, these are the title, the usage, the temperature and the frequency, each with its own color), but in the "tooltip" there are only 3 meters irrespective of what "menu" I hover on (the icon image, the title and the content).
This means that the entire content in the "tooltip" (i.e. what's not the icon or the first line reserved for the tooltip title) is a single meter. The coloring is done via the String meter's
inline options and - you guessed it, some regex -, and the alignment is done via the amount of spaces between "words" in the content string (which is why using a
monospaced font is highly recommended in the tooltips, in order to not "break" the alignment there and require volatile spacing adjustments). I did this to avoid creating a tooltip skin for each main skin in the suite, and has nice benefits, since their layout is consistent with minimal effort. It's not a problem to change the coloring to a different system, since it's just about adjusting the few InlinePatternN options in the following style:
Code: Select all
[STooltipContentText]
ClipString=2
ClipStringW=#TooltipClipContentSize#
ClipStringH=#TooltipClipContentSize#
FontFace=#TooltipTextFace#
FontColor=#TooltipTertiaryValueTextColor#
StringEffect=#TooltipTertiaryValueTextEffect#
FontEffectColor=#TooltipTertiaryValueTextEffectColor#
FontSize=#TooltipTextSize#
AntiAlias=1
InlineSetting=Color | #TooltipPrimaryValueTextColor#
InlinePattern="(?siU)(?:^|\n|● +?)([^∆≡ ][^●[\x200B]\n]*)(?= +?|\n|$)"
InlineSetting2=Color | #TooltipTitleTextColor#
InlinePattern2="(●|∆|≡)"
InlineSetting3=Color | #TooltipSecondaryValueTextColor#
InlinePattern3="(?siU)[\x200B]([^∆≡][^●[\x200B]\n]*)[\x200B]"
X=0r
Y=0R
Padding=#TooltipTextPaddingLeft#,#TooltipTextPaddingTop#,#TooltipTextPaddingRight#,#TooltipTextPaddingBottom#
the real problem is deciding on how to alternate colors in tooltips like this (especially the parts below the
● ● ● ● ● ● ● ● ● dividers):
Tooltip Skins.jpg
where the data being shown and its properties differ from each other considerably (yet they can be inserted into the same "framework", so to speak, due to the single tooltip skin being built in a such abstract and general manner, i.e. icon, title, content, from the start). Yes, I know that some of the parts below the dividers (like for memory or battery) could look better, but that's because Rainmeter still doesn't have a Justified alignment, so that's not under my control...
Yue wrote: ↑May 15th, 2023, 3:19 pm
I would leave out the commata. The spaces between the values are good enough as a seperator and besides you get a greater space between the left and the right group in each line what would make the grouping more visual [besides the triangle you added]. Additionally, that saves space you might need on other tooltips with bigger content [don´t know, but you surely do].
I wanted to leave out the commas to gain space as well, but while they can easily be removed, there won't be any space gained, because each of them will be replaced by a space (because of their format explained above). The reason is that I "reserve" 5 digit characters for the frequencies (99999 MHz seems like a reasonable maximum for quite some time, considering that the Guinness World Record for the highest CPU clock rate was "only" 8.42938 GHz in 2011 according to Wiki), 3 chars for the usage, and 3 chars for the temperatures, and they are all separated by two chars, of which one is a comma at this point. Removing the char for the comma entirely would leave just one char (now, a space) as the separator and that would be too less to avoid confusing one part with another (since one char is between the value and the unit as well).
Yue wrote: ↑May 15th, 2023, 3:19 pm
The toggling is a great Idea. This way you can have both variants depending on what you want to compare or keep an eye on. In fact I planned something similar for my skins [but will do that later].
Yeah, I was sure you'd like that - I like it too. Sometimes being undecided on layouts is a good thing, since you can provide different alternatives and let the user decide based on his needs.
Yue wrote: ↑May 15th, 2023, 3:19 pm
Im excited what the part the post scriptum is about will look like.
Well, it will be just another line in the text, but with a potential for improved observation because the variable nature of the data makes it difficult to estimate how much of an impact does something have on the CPU, GPU, and so on. Displaying averages along with the time they've been recorded is a way to solve that. I could add a histogram, but I'm more interested in functionality and purpose than in looks, especially in a minified suite, so the text based data will work just fine. I'll also probably add a Windows event log monitor and a network connections monitor to the suite in the future (I wanted to do them "real time" aka updated at 25 ms, but unfortunately it looks like I'll have to settle for a larger update interval of something like a couple of seconds).
You do not have the required permissions to view the files attached to this post.