Bug 234595 - Better handling of category deletion
Summary: Better handling of category deletion
Status: RESOLVED FIXED
Alias: None
Product: skrooge
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Stephane MANKOWSKI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-17 08:52 UTC by bubuche.pub
Modified: 2010-04-24 23:15 UTC (History)
1 user (show)

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 bubuche.pub 2010-04-17 08:52:38 UTC
Version:            (using KDE 4.4.2)

I know that you want to avoid panels... 

But deleting a category lets all attached operations without any category. Allowing users to pick another one or let the field empty would be great.

Right, this is not a top priority wish. But would secure a little bit skrooge's usage.

Regards.
Comment 1 Stephane MANKOWSKI 2010-04-17 17:28:06 UTC
I implemented a new feature: "New feature: Reparent operations on parent
category when a category is removed".
I think that it could be a solution for you.
If you want to remove category A and put all operations on category B, you can
do that:
1-By drag & drop, move A under B
2-Remove A 
==> All operations will be moved on B
Comment 2 Stephane MANKOWSKI 2010-04-17 17:29:18 UTC
SVN commit 1115813 by smankowski:

BUG: 234595: Better handling of category deletion ==> Reparent operations on parent category when a category is removed

 M  +1 -1      CHANGELOG  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1115813
Comment 3 bubuche.pub 2010-04-24 09:59:33 UTC
(In reply to comment #2)
> Reparent operations on parent category when a category is removed

Hello,

My point of view is that reassigning the category would be a side effect of the main action (remove a category), and that's not good and/or intuitive. Opening a popup like "The category is not empty. Remove anyway? Yes/No"? would be more explicit.

This could be compared to this situation: when you exit skrooge and that there are unsaved operations, there is a popup to ask you whether you want to save the document or not. They are not automatically saved. That's what users would expect.

Regards,
Gaëtan.
Comment 4 Stephane MANKOWSKI 2010-04-24 23:15:21 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Reparent operations on parent category when a category is removed
> 
> Hello,
> 
> My point of view is that reassigning the category would be a side effect of the
> main action (remove a category), and that's not good and/or intuitive. Opening
> a popup like "The category is not empty. Remove anyway? Yes/No"? would be more
> explicit.

When you select a category, you already know if some operations are affected to this category because you have the number of operation linked.
So, we don't have to display a confirmation panel.
In case of error, you can do "undo".

> 
> This could be compared to this situation: when you exit skrooge and that there
> are unsaved operations, there is a popup to ask you whether you want to save
> the document or not. They are not automatically saved. That's what users would
> expect.

The difference with save is that in case of error during save, you are not able to do undo because the application is closed.

> 
> Regards,
> Gaëtan.