Bug 299889 - The view doesn't update after an event is added.
Summary: The view doesn't update after an event is added.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: incidence viewer (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-12 15:48 UTC by Larry Pearson
Modified: 2017-01-07 22:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Larry Pearson 2012-05-12 15:48:38 UTC
If I add a new event and click OK, the window showing the calendar for that period doesn't update to show the new event.  If I happened to be viewing a day view and change to a week view, the window doesn't update.  If I delete an event, the window doesn't update.  The simplest way I've found to get the window to update is to minimize the display and then restore it.  If I change from a week view to a day view, the line that shows days of the week, i.e. Mon-Sun, changes to 'day' 'day of month' 'month' 'year', but the panel below with the times on the left still shows the week view.

I'm not familiar with your terminology, so I may have entered this bug in the incorrect category.


Reproducible: Always

Steps to Reproduce:
1.  Add or delete an event
2.  Change to a day view from a week view or vice versa
3.
Actual Results:  
No change in calendar view.

Expected Results:  
Calendar view updated to reflect the change.

I know of no additional information.
Comment 1 Denis Kurz 2016-09-24 18:52:48 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:08:07 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.