| Summary: | KWeather applet is not updated automatically | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Mingcong Bai <jeffbai> |
| Component: | tdeaddons | Assignee: | Slávek Banko <slavek.banko> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, jeffbai, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2696 | ||
|
Description
Mingcong Bai
2016-11-15 23:16:55 CST
The problem occurs on both amd64 and ppc64el? (In reply to Slávek Banko from comment #1) > The problem occurs on both amd64 and ppc64el? I do apologize. I meant to reply with an update that the weather applet does update the weather info, just with a bit of a delay. However, there are still two issues here: 1. Multiple entry of the same content was logged into the weather log. 2. Given 1, how about an option to allow for changing update interval (or is it the fact that the weather provider simply does not update any more frequently than once an hour?). (In reply to Mingcong Bai from comment #2) > (In reply to Slávek Banko from comment #1) > > The problem occurs on both amd64 and ppc64el? > > I do apologize. > > I meant to reply with an update that the weather applet does update the > weather info, just with a bit of a delay. > > However, there are still two issues here: > > 1. Multiple entry of the same content was logged into the weather log. > 2. Given 1, how about an option to allow for changing update interval (or is > it the fact that the weather provider simply does not update any more > frequently than once an hour?). Yes, I think that is common when the weather information is not updated very often. I observed that the updates are more frequent, if some events are current - for example, rain, thunderstorms,... That would explain why during the update KWeather may be weather information unchanged. For example, right now I have an update from the provider after 40 minutes. It seems that the bug report can be closed. What is your opinion? (In reply to Slávek Banko from comment #3) > (In reply to Mingcong Bai from comment #2) > > (In reply to Slávek Banko from comment #1) > > > The problem occurs on both amd64 and ppc64el? > > > > I do apologize. > > > > I meant to reply with an update that the weather applet does update the > > weather info, just with a bit of a delay. > > > > However, there are still two issues here: > > > > 1. Multiple entry of the same content was logged into the weather log. > > 2. Given 1, how about an option to allow for changing update interval (or is > > it the fact that the weather provider simply does not update any more > > frequently than once an hour?). > > Yes, I think that is common when the weather information is not updated very > often. I observed that the updates are more frequent, if some events are > current - for example, rain, thunderstorms,... That would explain why during > the update KWeather may be weather information unchanged. For example, right > now I have an update from the provider after 40 minutes. > > It seems that the bug report can be closed. What is your opinion? Okay that makes sense. Could it be done so that: - It won't write duplicate entries of weather information. or... - It write the real "time" in the log instead of posting the same time across multiple lines: that's just kind of confusing... (In reply to Mingcong Bai from comment #4) > (In reply to Slávek Banko from comment #3) > > It seems that the bug report can be closed. What is your opinion? > > Okay that makes sense. > > Could it be done so that: > > - It won't write duplicate entries of weather information. > > or... > > - It write the real "time" in the log instead of posting the same time > across multiple lines: that's just kind of confusing... Yes, you're right - in the log should be both - time information of KWeather update and also time information of update by provider. Proposed improvement was realized in GIT commit 8aedce54 (master) and 90fee640 (r14.0.x). Thank you for your insights and suggestions! |