Menu ▾ ▴

#717 inflation of priority when using maximize function

Release_1.0.3
closed
Frank Niessink
All platforms (377)
1
2012-09-15
2010-05-28
xstoffr
No

When using the maximize priority function, the new priority of the task is the greatest priority ever used +1. This cause inflation in the range of priority each time the function is used and make the maximize priority function unusable for people who want to keep the priority range moderate. Consequence: the new priority is greater than the number of time the maximize priority function had been used.

Sugestions:
- don't increment the value => set the new priority to the grestest priority ever used - and provide a function to reset this value to avoid trouble if an unsuitable value is set by mistake by the user once
- set the new priority to the greatest curent priority +1 and don't keep track of the greatest priority ever used

Discussion

  • Frank Niessink

    Frank Niessink - 2010-05-29

    A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.

    If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.

    Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.

    Thanks, Task Coach development team

     

  • Frank Niessink

    Frank Niessink - 2010-05-30

    This bug should be fixed in the latest release of Task Coach. Can
    you please install the latest release of Task Coach and confirm
    that this bug has indeed been fixed?

    Thanks, Task Coach development team

     

  • xstoffr

    xstoffr - 2010-05-31

    The behavior is much better. It could be improved and made more intuitive if the new value used would be greatest curent priority of curent view +1 instead of all existing tasks as in my case the greatest priority was a completed task hidden in curent view and it took me quite some time to understood why the new priority was so high in some cases.

    Thanks for the fix in any case, the function is now fully usable :-).

     

  • Frank Niessink

    Frank Niessink - 2010-06-01

    Thank you for taking the time to check the bug fix and reporting back to us.

    Regards, Task Coach development team

     

  • Frank Niessink

    Frank Niessink - 2010-06-01

    I'm not sure it's a good idea to limit the maximalisation to whatever is visible in the current view. However, it might make sense to ignore completed tasks when determining the maximum priority. You may want to open a feature request for that on http://taskcoach.uservoice.com.

    Thanks, Frank

     

Log in to post a comment.