| Summary: | Kolourpaint tries to save in wrong directory | ||
|---|---|---|---|
| Product: | [Applications] kolourpaint | Reporter: | Goran Brannstrom <goranbr> |
| Component: | general | Assignee: | kolourpaint-support |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | cfeck |
| Priority: | NOR | ||
| Version First Reported In: | Comes with KDE | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Goran Brannstrom
2011-10-09 16:56:18 UTC
What is the difference to bug 279219 you reported? Glad you asked. :-)
I can see why you would ask that... and here's why:
1. The bug is marked "resolved" if though it is not so in the version I hace
access to. So I report it again.
(And also because I could not see it under "My bugs" anymore. Couldn't
find it. )
2. In the report referred to I stated that the program saves the file under
the home directory, which, is slighly misleading. The save dialog opens in
the directory where the user last saved a picture.
So I'm wondering....
- Am I the only one that find this behaviour weird?
- Am I the only user?
- Or am I weird to wanna save a file in the same directory unless I tell it
otherwise? :-)
It would be an absolute gem if it worked properly.
Greatful for your efforts, and hopeful for improvements..... :-)
/Göran
2011/10/9 Christoph Feck <christoph@maxiom.de>
> https://bugs.kde.org/show_bug.cgi?id=283654
>
>
> Christoph Feck <christoph@maxiom.de> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |christoph@maxiom.de
>
>
>
>
> --- Comment #1 from Christoph Feck <christoph maxiom de> 2011-10-09
> 17:45:58 ---
> What is the difference to bug 279219 you reported?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
> The bug is marked "resolved" It is resolved as a duplicate, and this one is still open. *** This bug has been marked as a duplicate of bug 277168 *** |