User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build Identifier: When rescheduling an event with the help of the rescheduling dialogue, the "Pick Date" button in the "Visual Search" tab does not work as expected. Reproducible: Always Steps to Reproduce: 1. Create an appointment with attendees where at least one attendee has a conflict so that the "Reschedule" button is active. 2. Click on "Reschedule" 3. Choose "Visual Search". 4. There is no obvious way to reschedule the meeting in this tab, so click on the "Pick Date" button. Actual Results: - Clicking on the "Pick Date" button seemingly does nothing. - Switch back to "Automatic Search" button: A new date entry called "Move your appointment" has been added to this tab (it was not there before clicking "Pick Date" in the other tab). - Switch back to "Visual Search" tab: The date entry stays active and it is now possible to proberly reschedule the event. Expected Results: "Pick Date" should enable the "Move your appointment" date entry within the "Visual Search" tab without having to switch to the "Automatic search" tab.
In 4.11.2, this bug actually got worse: Now, the "Pick Date" button just does nothing.
Pick Date still does not do anything in 4.11.5. I've changed the title of this bug to match the current situation.
indeed all code is commented...
Git commit 6c12678932aebc3d546d1573013b49e805ace4ab by Montel Laurent. Committed on 12/03/2015 at 07:55. Pushed by mlaurent into branch 'KDE/4.14'. Disable Pick Date button for the moment as all code is commented M +1 -0 incidenceeditor-ng/visualfreebusywidget.cpp http://commits.kde.org/kdepim/6c12678932aebc3d546d1573013b49e805ace4ab
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.
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.