help with inline options

[Youkai1977]

Ok, will take a look a little bit later today or tomorrow.

Yes, as I said, don't stress about it. But I had also written that to you in the thread.

Ok, please do so. I'd like to know how is it going on.

Implemented your suggestion now in the NewsFeed skin and test how it works. I will give you feedback accordingly.
Here is the current code (behind the SPOILER)

1.) newsfeed.ini

Code: Select all

[Rainmeter]
Update=20
DefaultUpdateDivider=50
AccurateText=1
DynamicWindowSize=1

[Metadata]
Name=NewsFeed Reader (Marquee)
Author=Youkai1977 
Version=03-21.V1 <> 13.02.2021
Information=This Meter is a Part of M.A.R.S.- 2021 Skin Package
License=Creative Commons Attribution-Non-Commercial-Share Alike 4.0

;==================================================
;=== VARIABLES & STYLES ===========================
;==================================================

[Variables]
@include=newsfeeddata.inc

;==============================================================
;=== VOICE OUTPUT =============================================
;==============================================================
;===                                                         ==
;=== FOR MORE INFO TO SPEECH-PLUGIN                          ==
;=== https://forum.rainmeter.net/viewtopic.php?f=127&t=31161 ==
;===                                                         ==
;==============================================================

[VoiceOutput]
Measure=PLUGIN
Plugin=Speech
Name=#VoiceName#
;Index=#IndexName# 
;Gender=#VoiceGender#
Debug=#DebugModus#
Volume=#VoiceVolume#
Rate=#SpeechRate#
UpdateDivider=-1

;==================================================
;=== MEASURES NEWS FEED & MARQUEE =================
;==================================================

;=== MEASURES NEWS FEED ===========================

[mRSS]
Measure=WEBPARSER
URL=#RSSUrl#
RegExp=(?siU)<description>(.*)</description>.*<link.*>(.*)</link>.*<item.*<title.*>(.*)</title>.*<link.*>(.*)</link>(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)(?(?=.*<item).*<title.*>(.*)</title>.*<link.*>(.*)</link>)
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
UpdateRate=60000
StringIndex=1
Debug=1
OnChangeAction=[!EnableMeasureGroup CHILDS][!ShowMeter HEADNAME][!UpdateMeterGroup FEED][!Redraw]
FinishAction=[!CommandMeasure VoiceOutput "#NewsUpdSpeech#"][!SetOption HEADNAME FontColor "#Color4##Alpha1#"][!UpdateMeter HEADNAME][!Redraw][!Delay 5000][!ShowMeter NewsFeed][!EnableMeasure mXPos][!UpdateMeasure mXPos][!SetOption HEADNAME FontColor "#Color3##Alpha1#"][!UpdateMeter HEADNAME][!Redraw]
UpdateDivider=1

[mRSSItem1]
Measure=WEBPARSER
URL=[mRSS]
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
StringIndex=3
Disabled=1
Group=CHILDS

[mRSSItem2]
Measure=WEBPARSER
URL=[mRSS]
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
StringIndex=5
Disabled=1
Group=CHILDS

[mRSSItem3]
Measure=WEBPARSER
URL=[mRSS]
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
StringIndex=7
Disabled=1
Group=CHILDS

[mRSSItem4]
Measure=WEBPARSER
URL=[mRSS]
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
StringIndex=9
Disabled=1
Group=CHILDS

[mRSSItem5]
Measure=WEBPARSER
URL=[mRSS]
Substitute="&apos;":"'","&quot;":"","&Quot;":"","&amp;":"&","&lt;br&gt;":"","![CDATA[":"","]]":"","...":"","<":"",">":"","/PRE&gt;":"","PRE&gt;":"","&lt;":"","&#39;":"'","&#228;":"ä","&#246;":"ö","&#8211;":"–"
StringIndex=11
Disabled=1
Group=CHILDS

;=== MEASURE MARQUEE FUNCTION =====================

[mXPos]
Measure=LOOP
StartValue=#StartPos#
EndValue=-[NewsFeed:W]
Increment=#Direction#
LoopCount=0
DynamicVariables=1
UpdateDivider=1
Disabled=1

;##################################################
;##################################################
;##################################################
;##################################################
;##################################################
;##################################################

;==================================================
;=== HEAD NEWS FEED READER (Side Lines) ===========
;==================================================

[LAYERxPosText]
Meter=STRING
MeterStyle=StLAYER
X=0
Y=0

[HEADLINES]
Meter=SHAPE
X=0
Y=20
Shape=Rectangle 0,0,8,8 | Extend ModifiersS1
Shape2=Line 8,4,26,4 | Extend ModifiersL1
Shape3=Rectangle 26,0,8,8 | Extend ModifiersS1
;-----
Shape4=Rectangle 0,16,8,8 | Extend ModifiersS2
Shape5=Line 8,20,26,20 | Extend ModifiersL2
Shape6=Rectangle 26,16,8,8 | Extend ModifiersS2
;-----
Shape7=Rectangle ([HEADNAME:W] + 48),0,8,8 | Extend ModifiersS1
Shape8=Rectangle ([HEADNAME:W] + 48),0,8,8 | Extend ModifiersS1
Shape9=Rectangle ([HEADNAME:W] + 48),16,8,8 | Extend ModifiersS2
Shape10=Rectangle ([HEADNAME:W] + 48),16,8,8 | Extend ModifiersS2
;-----
Shape11=Rectangle 872,0,8,8 | Extend ModifiersS1
Shape12=Line 854,4,872,4 | Extend ModifiersL1
Shape13=Rectangle 846,0,8,8 | Extend ModifiersS1
;-----
Shape14=Rectangle 872,16,8,8 | Extend ModifiersS2
Shape15=Line 854,20,872,20 | Extend ModifiersL2
Shape16=Rectangle 846,16,8,8 | Extend ModifiersS2
ModifiersS1=StrokeWidth 0 | Fill Color #Color3##Alpha2#
ModifiersL1=StrokeWidth 2 | StrokeColor #Color3##Alpha2#
ModifiersS2=StrokeWidth 0 | Fill Color #Color3##Alpha1#
ModifiersL2=StrokeWidth 2 | StrokeColor #Color3##Alpha1#
DynamicVariables=1
UpdateDivider=-1
Group=FEED

[HEADNAME]
Meter=STRING
MeterStyle=StHEAD
X=41
Y=r
LeftMouseUpAction=[#vURL#]

;==================================================
;=== MARQUEE NEWS FEED READER =====================
;==================================================

;=== CONTAINER NEWS FEED ==========================

[CONTAINER_NWF]
Meter=SHAPE
X=0
Y=r
Shape=Line ([HEADNAME:W] + 63),0,839,0 | StrokeWidth 47 | StrokeColor #Color0##Alpha1#
DynamicVariables=1
UpdateDivider=-1
LeftMouseDoubleClickAction=[#vURL#]
Group=FEED

;=== MARQUEE NEWS FEED ============================

[NewsFeed]
Meter=STRING
MeterStyle=StNEWS
X=[mXPos]r
Y=r

2.) newsfeeddata.inc

Code: Select all

[Variables]
;********************************************************************************************************************************************************
;********************************************************************************************************************************************************
;***                                                                                                                                               ******
;*** !!!!!!!!!!!!!!!!!!   DON`T CHANGE ANYTHING IN THIS FILE   !!!!!!!!!!!!!!!!!!!!!!!   Unless you know what you are doing :-) !!!!!!!!!!!!!!!!!! ******
;*** !!!!!!!!!!!!!!!!!!   DON`T CHANGE ANYTHING IN THIS FILE   !!!!!!!!!!!!!!!!!!!!!!!   Unless you know what you are doing :-) !!!!!!!!!!!!!!!!!! ******
;*** !!!!!!!!!!!!!!!!!!   DON`T CHANGE ANYTHING IN THIS FILE   !!!!!!!!!!!!!!!!!!!!!!!   Unless you know what you are doing :-) !!!!!!!!!!!!!!!!!! ******
;*** !!!!!!!!!!!!!!!!!!   DON`T CHANGE ANYTHING IN THIS FILE   !!!!!!!!!!!!!!!!!!!!!!!   Unless you know what you are doing :-) !!!!!!!!!!!!!!!!!! ******
;***                                                                                                                                               ******
;********************************************************************************************************************************************************
;********************************************************************************************************************************************************
;==================================================
;=== VARIABLES FONTFACE - SIZE - COLORS ===========
;==================================================
FontFace=SQUARE721 BT
FS1=10
FS2=8
Alpha0=1
Alpha1=255
Alpha2=70
Color0=0,0,0,
Color1=160,246,253,
Color2=48,180,200,
Color3=97,240,255,
Color4=253,193,0,
Color5=255,255,255
Color6=255,104,67,
;==================================================
;=== VARIABLES SPEECH PLUGIN (NewsFeed) ===========
;==================================================
VoiceName=Microsoft Hedda Desktop
;IndexName= 
;VoiceGender=
DebugModus=0
VoiceVolume=100
SpeedRate=-2
NewsUpdSpeech=News Feed aktualisiert
;==================================================
;=== VARIABLES NEWS FEED READER ===================
;==================================================
Direction=-1
StartPos=850
RSSUrl=https://news.google.com/rss?pz=1&cf=all&hl=de&gl=DE&ceid=DE:de
vURL=http://news.google.de/
;==================================================
;=== STYLE NEWS FEED HEAD (Side Line) =============
;==================================================

[StLAYER]
Padding=0,-3,-1,-3
SolidColor=#Color0##Alpha0#
FontColor=#Color1##Alpha1#
FontFace=#FontFace#
FontSize=#FS2#
StringCase=UPPER
AntiAlias=1
Text=LAYER NFR   POS: [NewsFeed:Y] [\x00B7] [mXPos]
InlineSetting=Color | #Color6##Alpha1#
InlinePattern=[NewsFeed:Y]
InlineSetting2=Color | #Color4##Alpha1#
InlinePattern2=[\x00B7](.*)
DynamicVariables=1
UpdateDivider=1
Group=FEED

[StHEAD]
Padding=0,4,-1,5
SolidColor=#Color0##Alpha0#
FontColor=#Color3##Alpha1#
FontFace=#FontFace#
FontSize=#FS1#
StringCase=UPPER
AntiAlias=1
Text=[mRSS]
ClipString=2
ClipStringW=105
ClipStringH=15
DynamicVariables=1
UpdateDivider=-1
Group=FEED

;==================================================
;=== STLYE NEWS FEED ==============================
;==================================================

[StNEWS]
Padding=0,4,-1,5
SolidColor=#Color0##Alpha0#
FontColor=#Color5##Alpha1#
FontFace=#FontFace#
FontSize=#FS1#
StringCase=UPPER
AntiAlias=1
Text=[\x2022][\x2022][\x2022]  [mRSSItem1]  [\x2022][\x2022][\x2022]  [mRSSItem2]  [\x2022][\x2022][\x2022]  [mRSSItem3]  [\x2022][\x2022][\x2022]  [mRSSItem4]  [\x2022][\x2022][\x2022]  [mRSSItem5]  [\x2022][\x2022][\x2022] 
InlineSetting=Color | #Color1##Alpha1#
InlinePattern=(?i)[mRSSItem1] | (?i)[mRSSItem3] | (?i)[mRSSItem5]
InlineSetting2=Color | #Color2##Alpha1#
InlinePattern2=(?i)[mRSSItem2] | (?i)[mRSSItem4]
DynamicVariables=1
UpdateDivider=1
Hidden=1
Container=CONTAINER_NWF
Group=FEED

By the way, I have optimized/rewritten the Marquee-Measures indes that this now only runs via ONE LOOP-Measure in combination that before the (variable) width of the newsfeed meter is implemented.
The advantage of the now variable width is (so I hope at least), that the newsfeed scrolls only as long as it is actually wide.
Now it has to be seen in practice, if it works without errors, or if I have to work on the update commands for the involved meters and measures, when the NewsFeed is updated. That is, the new width of the NewsFeed meter then also be passed to the LOOP-Measure.

Same here, Rainmeter has been developed extremely much in last few years, thanks to the devs. A lot of new features have been added, but in some cases this complicates things a little bit. But this forum can help you / anyone when needed.
About the TranformationMatrix, it's pure math. And I love it (not the math, but the TransformationMatrix - well, in fact math as well, but I was talking about TM).

Math ... I hate math.
N

ote that not all replyies / post here in the forum are acurate. People are mistaken from time to time, you don't always have to take all posts for granted. (Almost) everyone is mistaken at some point, ME FOR SURE.

I am aware that threads/postings can contain errors. I have that so far also on the screen. What I rather meant was that I noticed that there seems to be many, many solutions for one problem. If you then but times asks which then the better / preferred solution, then is often shrugged.

Example:
Reading out the CPU cores. There is %NUMBERS_OF_CORES% or something similar. Then there is WMIC with which you can do it.
Which is better now?
But as said, was now only an example....

Alright, just wanted to make sure that's not a mistake in the code. Good if it's not.

No no, it's all good. I had just the readable because of here in the posting the point at the 60000 set. I know that this is NOT allowed in the code.

PS: What still does NOT work is that with the colors in the individual [mRRSItem]s.
Stand there really on the hose, what goes wrong there

Ok, as for my slideshow (other THREAD), since I already roughly skimmed your answer. But must now only times again away from the PC. Say, I give you there later feedback

[balala]

Yes, as I said, don't stress about it. But I had also written that to you in the thread.

Yep and I replied, posting the code of three meters and a style section, which are implementing three extremely simple buttons, which definitely have to be improved, but at least are a start. Please let me know if you tried them out.

Implemented your suggestion now in the NewsFeed skin and test how it works. I will give you feedback accordingly.
Here is the current code (behind the SPOILER)

Your code does work. Good job.

[Youkai1977]

Yep and I replied, posting the code of three meters and a style section, which are implementing three extremely simple buttons, which definitely have to be improved, but at least are a start. Please let me know if you tried them out.

Yup, seen and answered

Your code does work. Good job.

Thank you.
However, something seems to be wrong with the update timing now. I have set it as in my last answer (the code behind the SPOILER). But now I notice that I have an update rate (real time) of almost 2 hours.
Since I take the Speech-Plugin to help to get a voice announcement, if the update runs I get it yes with.
And this is how it looks currently. At 19:52 (7:52PM) clock came the announcement that the NewsFeed was updated, and then now only again at 21:46 (9:46PM) clock.

Before, the way I had set it ...

- Update=20
- DefaultUpdateDivider=50
- UpdateRate=1200

... there the Update-Interval was about 20 minutes

Now (after your tip) ...

- Update=20
- DefaultUpdateDivider=50
- UpdateRate=60000 and an UpdateDivider=1 on the [mRSS]

... i have only (it seems) almost every 2 Hours an Update-Interval
Slowly this update story at Rainmeter reminds me of the sentence of a captain from StarTrek ... "Spare me time travel and its paradoxes. It gives me a headache"

This is how I feel now about the update stuff in Rainmeter

Ooooooooooooooooooooooohhhhhhhh ... now in this Second (22:19 clock) an Update ... (33 Minutes Interval) ... *WTF*

[balala]

However, something seems to be wrong with the update timing now. I have set it as in my last answer (the code behind the SPOILER). But now I notice that I have an update rate (real time) of almost 2 hours.
Since I take the Speech-Plugin to help to get a voice announcement, if the update runs I get it yes with.
And this is how it looks currently. At 19:52 (7:52PM) clock came the announcement that the NewsFeed was updated, and then now only again at 21:46 (9:46PM) clock.

Before, the way I had set it ...

- Update=20
- DefaultUpdateDivider=50
- UpdateRate=1200

... there the Update-Interval was about 20 minutes

Now (after your tip) ...

- Update=20
- DefaultUpdateDivider=50
- UpdateRate=60000 and an UpdateDivider=1 on the [mRSS]

... i have only (it seems) almost every 2 Hours an Update-Interval
Slowly this update story at Rainmeter reminds me of the sentence of a captain from StarTrek ... "Spare me time travel and its paradoxes. It gives me a headache"

This is how I feel now about the update stuff in Rainmeter

Ooooooooooooooooooooooohhhhhhhh ... now in this Second (22:19 clock) an Update ... (33 Minutes Interval) ... *WTF*

In this case you can use the values which are letting the skin to properly work.
Or you might pack the config and upload it here. This way I could check it EXACTLY as you have it. Posting only the code might not be enough.

[Youkai1977]

In this case you can use the values which are letting the skin to properly work.
Or you might pack the config and upload it here. This way I could check it EXACTLY as you have it. Posting only the code might not be enough.

I have now left the values as suggested by you for the time being.
What strikes me, now that the NewsFeed skin in the duration (BETA)-Final-Test runs, that the update rates seem to fluctuate between 30 - 45 minutes. Maybe I imagine that but also, no plan. Sit currently rather under stress at the PC, because I have to do other at the moment (i say only GERMAN Administrations and Agencies in Corona-Times ) , and Rainmeter therefore runs active, but my concentration / eyes are not really now on it.

Therefore as requested here my NewsFeed-Reader as *.rmskin package.
Look over it, you test him times in the endurance test. Maybe this color problem of the feed comes to light especially with you.

[balala]

What strikes me, now that the NewsFeed skin in the duration (BETA)-Final-Test runs, that the update rates seem to fluctuate between 30 - 45 minutes. Maybe I imagine that but also, no plan.

I added a few options which help you to follow exactly when the updates are going on, without being afraid of losing one.
So first add an Index=0 variable to the [Variables] section.
Add the following two measures and modify the FinishAction option of the [mRSS] measure, taking care not to modify the not posted options:

Code: Select all

[MeasureDate]
Measure=Time
Format=locale-date
UpdateDivider=-1
Group=DateTime

[MeasureTime]
Measure=Time
Format=locale-time
UpdateDivider=-1
Group=DateTime

[mRSS]
...
OnChangeAction=[!EnableMeasureGroup CHILDS][!ShowMeter HEADNAME][!UpdateMeterGroup FEED][!Redraw]
FinishAction=[!UpdateMeasureGroup "DateTime"][!SetVariable Index "(#Index#+1)"][!CommandMeasure VoiceOutput "#NewsUpdSpeech#"][!SetOption HEADNAME FontColor "#Color4##Alpha1#"][!UpdateMeter HEADNAME][!Redraw][!Delay 4000][!ShowMeter NewsFeed][!EnableMeasure mXPos][!UpdateMeasure mXPos][!SetOption HEADNAME FontColor "#Color3##Alpha1#"][!UpdateMeter HEADNAME][!Redraw][!Delay "1000"][!WriteKeyValue Variables DateTime#Index# "[MeasureDate] - [MeasureTime]"]
...
DynamicVariables=1

This way you get a new variable in the [Variables] section each time the [mRSS] measure update, so you'll be able to exactly follow the moments of updates.

[Youkai1977]

Sorry for the late reply ... I'm not much at the PC at the moment.

So I have implemented your idea now. If I understand it correctly, the Variable Index +1 should be set with each update, and accordingly then with each update of the feed a ...

DateTime0=Time1
DateTime1=Time2
DateTime2=Time3
...
..
.

...and be written continuously. So I could compare the times and read the update rates.

Well, in principle your idea works. But what does NOT work is to set the Variable Index +1 continuously.
So the value DateTime is always written only DateTime0 with the then current date/time at the time of the update of the [mRSS]-Measure. And the previous DateTime0-Value is overwritten. So no comparison of the Update cycles is possible, which makes your idea obsolete.

In short ... NO ...

Example:
DateTime0=27.03.2021 - 10:00
DateTime1=27.03.2021 - 10:30
DateTime2=27.03.2021 - 11:00
...
..
.

Somehow the Variable Index is not incremented and remains at 0
And yes, I have set [!SetVariable Index "(#Index#+1)"], and also previously set Index=0 in the [Variables] section.

[balala]

Sorry for the late reply ... I'm not much at the PC at the moment.

So I have implemented your idea now. If I understand it correctly, the Variable Index +1 should be set with each update, and accordingly then with each update of the feed a ...

DateTime0=Time1
DateTime1=Time2
DateTime2=Time3
...
..
.

...and be written continuously. So I could compare the times and read the update rates.

Yep, this is the idea.

Well, in principle your idea works. But what does NOT work is to set the Variable Index +1 continuously.
So the value DateTime is always written only DateTime0 with the then current date/time at the time of the update of the [mRSS]-Measure. And the previous DateTime0-Value is overwritten. So no comparison of the Update cycles is possible, which makes your idea obsolete.

The basic idea was to restart the DateTimeX variable always when you're refreshing the skin. Those dates and times are interesting to be followed while the computer (and the skin) is / are running continouosly. If you restart the computer (or you are booting it up), the dates and times should be restarted. Knowing when the measure has been updated into a previous work of the skin doesn't provide any useful information. So even if the already written variables are not removed, but they are continouosly rewritten after refresh.

In short ... NO ...

Example:
DateTime0=27.03.2021 - 10:00
DateTime1=27.03.2021 - 10:30
DateTime2=27.03.2021 - 11:00
...
..
.

Somehow the Variable Index is not incremented and remains at 0
And yes, I have set [!SetVariable Index "(#Index#+1)"], and also previously set Index=0 in the [Variables] section.

But did you also add the DynamicVariables=1 option to the [mASS] measure?

[Youkai1977]

Yep, this is the idea.

Perfect ... I have understood formula-technically once something at the first go

The basic idea was to restart the DateTimeX variable always when you're refreshing the skin. Those dates and times are interesting to be followed while the computer (and the skin) is / are running continouosly. If you restart the computer (or you are booting it up), the dates and times should be restarted. Knowing when the measure has been updated into a previous work of the skin doesn't provide any useful information. So even if the already written variables are not removed, but they are continouosly rewritten after refresh.

Ok I understand that now again only partially, so contentwise...
But is probably due to the translation.
But does not matter for now, because ....

But did you also add the DynamicVariables=1 option to the [mASS] measure?

...insofar as by [mASS] you actually mean [mRSS] ... exactly that I had forgotten ... and now it runs

Here a Screenshot-Snippet:

Update-Cycle.png

1. Update-Cycle: 09:32:31 - 10:06:08 = 33 Min & 37 Sec
2. Update-Cycle: 10:06:08 - 10:39:48 = 33 Min & 40 Sec

If I have now calculated correctly ...
I mean, I know there is a [!Delay 1000] in the code before the key is written. but a difference of 3 seconds is still weird. Let alone that I have such a weird crooked update cycle of 33 minutes and crooked seconds.

Because according to your explanation the last few days on the subject, or what the manual gives, should be with my current coding of the NewsFeed....

Code: Select all

Update=20
DefaultUpdateDivider=50

[mRSS]
...
...
UpdateRate=60000
...
UpdateDivider=1

...but if I remember your explanation or tip correctly (I can't find it in the thread here), you should get an update cycle of 20 minutes.
With my coding, without UpdateDivider=1 on the [mRSS] and an UpdateRate=1200 it was so anyway.

This is not to say that I don't believe you. I think that you are better positioned in the knowledge on the subject than I am. So the error is probably somewhere with me or my coding to look for. Or are we both right and here are the once from me jokingly thrown in small Gobblins in Rainmeter at work?

[balala]

Here a Screenshot-Snippet:

Update-Cycle.png

1. Update-Cycle: 09:32:31 - 10:06:08 = 33 Min & 37 Sec
2. Update-Cycle: 10:06:08 - 10:39:48 = 33 Min & 40 Sec

If I have now calculated correctly ...
I mean, I know there is a [!Delay 1000] in the code before the key is written. but a difference of 3 seconds is still weird. Let alone that I have such a weird crooked update cycle of 33 minutes and crooked seconds.

Because according to your explanation the last few days on the subject, or what the manual gives, should be with my current coding of the NewsFeed....

Code: Select all

Update=20
DefaultUpdateDivider=50

[mRSS]
...
...
UpdateRate=60000
...
UpdateDivider=1

...but if I remember your explanation or tip correctly (I can't find it in the thread here), you should get an update cycle of 20 minutes.
With my coding, without UpdateDivider=1 on the [mRSS] and an UpdateRate=1200 it was so anyway.

The fact that the updates don't always go on on the same interval is not something weird. A WebParser measure always needs certain time until parses the resource.
However I don't have an explanation why the updates happen on an interval of 30 minutes (or even a little bit more), instead of 20. But I think you can live with this. If needed, you can adjust the UpdateRate to a value which updates properly the measure. A few tries are needed in order to get the proper value, but I think you can determin the proper value.