Yincognito wrote: ↑January 31st, 2021, 1:46 am
Well, I guess it depends on how you look at it, LOL. Although the form of the solution I proposed wasn't precisely how you implemented it, the idea was the same. You had to get rid of #CURRENTSECTION#
from Offset 0,#CURRENTSECTION#
and replace it with a variable holding the Y position of the item; the only difference was that I proposed storing the item index
as a variable and use it to get the [Item_ItemIndex:Y], which is why I said:
and further explored the approach in my first EDIT, while you, on the other hand, stored that Y directly
as a variable in the snippet you mentioned from [Style6]'s MouseOverAction.
As I said, I didn't criticize you or your approach. On the contrary, it was clear that you had made the right move.
And ultimately, who knows what it's good for, it shouldn't be a bad thing to have several solutions at hand. Because if Rainmeter taught me one thing, a solution doesn't always have to work twice.
Anyway, I think it's better when folks find solutions themselves (as opposed to copying or replicating stuff from others), cause doing so helps them get better at what they do, so it's all good - well done!
Thank you for the praise.
Yes that's probably true, learn by doing it yourself.
But scouring the forum and other sources, and possibly copying first, I still like to use it.
However, this method has often been, and is current to me, precisely now also the undoing.
Because if you don't really deal with what code snippet / syntax etc. is actually there for what, then in the worst case it will be really tight with your own knowledge.
Because that's exactly what I actually took with my current SKIN suite. I started by copying it in 2014. And over the years I only changed the look and layout. Seldom has a function been added or something similar.
And so we are now writing in 2021, I have been using Rainmeter for 7 years now and basically don't really know anything about the code basics.
But that should change now, as I said, I really want to be able to say that "I" did and created it.
For me, however, really difficult, because there would still be the language barrier. Forums or something similar, certainly not such a good manual like "https://docs.rainmeter.net/
" in my language "German" is almost an absurdity. Sometimes I have the feeling that nobody in Germany knows Rainmeter. Only Facebook, Instagram, Youtube ... and currently Corona -.-
Yep, the big advantage is the text's colors - it makes much easier identifying bits of the code. Add a dark theme to it and it will be softer on the eyes as well:
Yes with the colors is really a relief. I also set it so dark. Really nice. Also the tab function as with the browser.
But there are also a few things to which I still have to get used to and which I currently consider to be a hindrance. But let's see, I don't understand the Rainmeter syntax (always) and still use it * lol *
- Win11 Pro x64 (23H2 - 22631.2506)
- Rainmeter 4.5.18
- Gigabyte B550i AORUS Pro AX V1.2
- Corsair Venegeance LPX 2x 16GB (32GB) DDR4 3200MHz @ 2933MHz
- RYZEN 5 3400G (Only Temporary)
- PowerColor RX570 8GB
- Samsung 980Pro 250GB (NVMe) - Windows - Drive C:
- Samsung 840 128GB - Rainmeter-Skins & Others - Drive D:
- Samsung 870 EVO 500GB - Games - Drive E:
- NAS Synology DS216j - 2x 1GB HDDs - My Main Backup & Data Storage in my Home-Network
- Mon 1: 24" HP 24f (1920 x 1080 @ 75Hz) - Primary
- Mon 2: 22" Philips 226VL (1920 x 1080 @ 60Hz) - Secondary 1
- Mon 3: 50" Philips 50PUS7304/12 (3840 x 2160 @ 60Hz) - Secondary 2
- Corsair CX 650M Power Supply
- NZXT H210 Case
- ISP Vodafone with 1000/50 Mbit Cable Internet
The absolutly High-End Machine on 2023