LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
I have no idea what UTF-16 LE is, never heard of it,
What text editor are you using? If you're using plain Notepad, open the Remote-Active-1.ini file into it, click Edit > Save as. In the opening Save as dialog, on the lower part of the window you have an Encoding menu. Check there the encoding of your file. It should be UTF-16 LE. If it's another, choose UTF-16 LE from the menu and click Save. In the opening Confirm save as dialog, click Yes, to rewrite the old file which has an improper coding with the UTF-16 LE coded file. Take care that the file with the old coding
is rewritten with the newly coded file.
If you're using Notepad++ as text editor, open the file into this app and click the Encoding menu, In the list you have to choose UCS-2 LE BOM as coding of your file. If you have to modify this, don't forget to save the file, to get the encoding changed to the proper one.
If you're using any other text editor I can't say precisely how do you modify the coding, but for sure it can be done in any editor.
LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
Also no idea what language I coded my skin in, I really did start with your hello world example in the tutorial and started adding bits to it by trial and error, after two weeks it had got to what I sent you, and half that fortnight was spent on making graphics for it. I'm amazed and impressed that it works.
Rainmeter uses plain .ini file to store the code of skins. This type of file is a dedicated sort of code, divided into sections (each of them has a name included into brackets, most of them being either measures - the one having a
Measure=... option, or meters - as you guesed these are the sections having a
Meter=... option and additionally a few "special" sections, like [Metadata], [Rainmeter] or [Variables]) and each section having options (like
Measure=Calc, or
Formula=( MyMeasure + 1 ), but obviously these are only two examples).
And don't be amazed, nor impressed it works. You did an excelent work, especially for a beginner in Rainmeter coding, if the posted code is yours. Don't worry we all started with altering existing codes, I also did this in my first attempt to realize a working code. And even today, after more than a decade of continuous work with these codes, I also get existing skins and alter them. So don't worry, it's a great job done...
LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
THIS MIGHT BE IMPORTANT TO OTHER USERS
SYSTEM RESTORE DELETED MY .ini Files - Didn't expect that!!!
I had to use restore because I wrote some other VBS scripts one of which was to hide and restore the desktop Icons, (makes rainmeter look so much better), anyway the script hid them but I couldn't get them back, even in windows, so I did a system restore, which worked but deleted my .ini files. (I have fixed those scripts) and they work perfectly at least in windows.
BUT NOW COPY MY ENTIRE SKIN TO MY D: DRIVE EVERY NIGHT
I assume I can just copy and paste it back over the working one in rainmeter to over-write it in case that happens again?
Sorry this has happened. Unfortunately (or fortunately?) I can't tell what a system restore does. But copying the files is a good idea to keep them safe. I do a backup of my whole system once per week, not daily. In any case, having some level of safeness is always a good idea.
LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
BRILLIANT NOW IT'S #*$%ING OBVIOUS WHAT THE PROBLEM IS !!!!!!
I'm glad if you found it. Congratulations.
LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
So glad I wrote a long boring post or I would not have spotted it Thanks so much for your time and patience. it's fixed now and works I just tested it. I have several other cool scripts, once I finish this I'll post the entire project somewhere so others can use it and them
No, you didn't write a boring post. There are no boring posts. Finally when we have no enough time (happens too often unfortunately) we don't read the long posts and are returning to them when have more time.
LuciferVisuals wrote: ↑April 13th, 2023, 5:52 am
But to be fair a simple typo in the scripts path would have caused exactly the same mistake and error message.
Right.