| Summary: | Freezes when using undo with measuring tool. | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | chris27wjoyner |
| Component: | Layers/Vector | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | crash | CC: | halla, sven.langkamp |
| Priority: | NOR | ||
| Version First Reported In: | 2.9.7 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
chris27wjoyner
2015-09-02 15:52:26 UTC
Hi Chris, I haven't managed to reproduce the issue yet, I must be missing something. The measure tool actually should disappear from the canvas the moment you select another tool, playing with it shouldn't add any steps to the undo queue. I see we have an issue where the Undo action is enabled even if there's nothing left to undo, which is weird in itself... I tried to reproduce the bug by following the steps I took. But krita is behaving itself. You said the undo is enabled without anything int he undo. If the program performed an undo when it was blank, or unallocated it might have been able to read the unallocated or allocated dirty ram causing it to malfunction. On Thu, 03 Sep 2015 06:48:00 +0000 Boudewijn Rempt <boud@valdyas.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=352166 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |boud@valdyas.org > > --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> --- > Hi Chris, > > I haven't managed to reproduce the issue yet, I must be missing something. The > measure tool actually should disappear from the canvas the moment you select > another tool, playing with it shouldn't add any steps to the undo queue. I see > we have an issue where the Undo action is enabled even if there's nothing left > to undo, which is weird in itself... > > -- > You are receiving this mail because: > You reported the bug. Closing this as Waitingforinfo. If it reappears please reopen this bug. |