https://bugs.kde.org/show_bug.cgi?id=427196
Thomas Baumgart <tbaumg...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Thomas Baumgart <tbaumg...@kde.org> --- The design of KMyMoney at this point is to always operate on the next occurrence of a schedule. In some instances, the preview shows more than one occurrence of a schedule and I agree, that it is confusing that trying to skip the third occurrence suddenly skips the first. On the other hand, what you try to achieve is more of an exception to a schedule but the current implementation does not support exceptions to schedules. Technically, KMyMoney keeps the date of the next transaction and the recurring period. So the second and further occurrences do not exist on file but are generated for display purposes only. So skipping an occurrence simply forwards the date of the next transaction to the one following. What we could do is to make sure that we always present 'Operation on *next* occurrence of schedule' in the tooltips and descriptions. This seems to be a more or less easy task. The second best would be to disable the operations on any but the next occurrence of a schedule, which is more of a larger change. Any other ideas? -- You are receiving this mail because: You are the assignee for the bug.