balala wrote: ↑July 25th, 2020, 2:27 pm
I'm using Notepad++ and as said I can edit it with no problems. If a !WriteKeyValue bang writes anything, Notepad++ ask me if I want to reload the file, but otherwise it is editable.
Hmm, well, the same thing with SublimeText3 it asks for a reload but inhibits editing once the file has changed on its own. So, I just unload the skin edit then restart.
You did see what happens though - the skin broke for you and would not work. Therefore you do know what I meant when I said there are 'issues' with editing.
At any rate, NP++ or PN3 or ST3 - I've used them all as well as others for editing several languages, so I know they all have different behaviour with 'live' editing. I like ST3 the best since it is the most configurable and I have indeed configured those all to some degree.
Thanks for the assistance, with this thread's topic as well as many others.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
Mor3bane wrote: ↑July 25th, 2020, 11:51 pm
You did see what happens though - the skin broke for you and would not work. Therefore you do know what I meant when I said there are 'issues' with editing.
At any rate, NP++ or PN3 or ST3 - I've used them all as well as others for editing several languages, so I know they all have different behaviour with 'live' editing. I like ST3 the best since it is the most configurable and I have indeed configured those all to some degree.
If there are such issues, try using Windows built-in Notepad, just for live editing. I agree it has a lot of disadvantages, but at least for sure won't have such issues.
balala wrote: ↑July 26th, 2020, 6:14 am
If there are such issues, try using Windows built-in Notepad, just for live editing. I agree it has a lot of disadvantages, but at least for sure won't have such issues.
My next option will be to move the variables that are being updated with the !WriteKeyValue Bangs to the inc file so editing the main functions will not be an issue with the skin running. It has been tricky as there seems to be some - I wouldn't call the redundancies, but what appear to be multiple Bangs that seem to be doing the same thing - anyway, it shouldn't require lua as far as i can see.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
Mor3bane wrote: ↑July 28th, 2020, 12:38 am
My next option will be to move the variables that are being updated with the !WriteKeyValue Bangs to the inc file so editing the main functions will not be an issue with the skin running.
Good idea, give it a try and let us know if you got it working well.
Mor3bane wrote: ↑July 28th, 2020, 12:38 am
anyway, it shouldn't require lua as far as i can see.
!SetVariable: Skin "C:\Users\Sapient\Documents\Rainmeter\Skins\\Options\options.inc" not found (Scroll Timer\CountDownTimer.ini)
!WriteKeyValue: File not found: C:\Users\Sapient\Documents\Rainmeter\Skins\\Options\options.inc (Scroll Timer\CountDownTimer.ini)
The problem is there are many !SetVariable, and !WriteKeyValue bangs in this.
I can post the skin if someone thinks they can help me find the lines being flagged.
I have checked the path and it is correct for the file in question, however, I may very easily be missing something painfully obvious.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
!SetVariable: Skin "C:\Users\Sapient\Documents\Rainmeter\Skins\\Options\options.inc" not found (Scroll Timer\CountDownTimer.ini)
!WriteKeyValue: File not found: C:\Users\Sapient\Documents\Rainmeter\Skins\\Options\options.inc (Scroll Timer\CountDownTimer.ini)
The problem is there are many !SetVariable, and !WriteKeyValue bangs in this.
I can post the skin if someone thinks they can help me find the lines being flagged.
I have checked the path and it is correct for the file in question, however, I may very easily be missing something painfully obvious.
Any help is appreciated.
I noticed this : Skins\\Options
should be "Skins\Scroll Timer\Options" I believe...
brax64 wrote: ↑August 26th, 2020, 4:19 am
Maybe doesn't matter but I noticed this : Skins\\Options"\\" instead of "\"
Yes, I noticed that as well. There is no instance in the ini file, or any other file where there are "\\".
I also tried replacing the path with the absolute path (the ini uses a #options# variable for that path), with no change in skin behaviour and the error continues after clearing the log.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
Mor3bane wrote: ↑August 26th, 2020, 4:38 am
Yes, I noticed that as well. There is no instance in the ini file, or any other file where there are "\\".
I also tried replacing the path with the absolute path (the ini uses a #options# variable for that path), with no change in skin behaviour and the error continues after clearing the log.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.