[krita] [Bug 372357] Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357 --- Comment #12 from Jelena <jelen...@t-online.de> --- For testing: Is there a DMG build anywhere which incorporates the bugfix? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 --- Comment #7 from Jelena <jelen...@t-online.de> --- Thanks for working on it but the current implementation of the color selector unfortunately also doesn't work too well for me: When I choose a black color the whole outer circle turns black and I first have to select a different saturation to see colour on the outer circle again. (Acoordingly when I choose a white color the whole circle turns white.) As I use black or grey most of the times I don't see any colors in the wheel most of the time which is quite irritating. Is there a toggle anywhere to switch back to the previous behaviour (i.e. always showing a colored outer circle)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372357] Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357
--- Comment #5 from Jelena <jelen...@t-online.de> ---
And another one if that should help.
Steps: Open Krita - new Docuent - add text - save - crash:
1 0 QKeyEvent(ShortcutOverride, Key_Control, ControlModifier)
QKeyEvent(ShortcutOverride, Key_Control, ControlModifier)
1 0 QKeyEvent(KeyPress, Key_Control, ControlModifier) QKeyEvent(KeyPress,
Key_Control, ControlModifier)
1 0 QKeyEvent(ShortcutOverride, Key_S, ControlModifier)
QKeyEvent(ShortcutOverride, Key_S, ControlModifier)
1 0 QEvent(Leave, 0x7fff5fbfbf50) QEvent(Leave, 0x7fff5fbfbf50)
1 0 QEvent(WindowBlocked, 0x7fff5fbfc3d0) QEvent(WindowBlocked, 0x7fff5fbfc3d0)
1 0 QFocusEvent(FocusAboutToChange, OtherFocusReason)
QFocusEvent(FocusAboutToChange, OtherFocusReason)
1 0 QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
1 0 QEvent(WindowDeactivate, 0x7fff5fbfabb0) QEvent(WindowDeactivate,
0x7fff5fbfabb0)
1 0 QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
1 0 QFocusEvent(FocusOut, ActiveWindowFocusReason) QFocusEvent(FocusOut,
ActiveWindowFocusReason)
1 0 QPaintEvent(Paint, 0x7fff5fbfa3b0) QPaintEvent(Paint, 0x7fff5fbfa3b0)
1 0 QEvent(WindowUnblocked, 0x7fff5fbf9870) QEvent(WindowUnblocked,
0x7fff5fbf9870)
1 0 QEvent(WindowActivate, 0x7fff5fbface8) QEvent(WindowActivate,
0x7fff5fbface8)
1 0 QEnterEvent(QPoint(0,0)) QEnterEvent(QPoint(0,0))
1 0 QFocusEvent(FocusIn, ActiveWindowFocusReason) QFocusEvent(FocusIn,
ActiveWindowFocusReason)
1 0 QInputMethodQueryEvent(queries=0x101, {})
QInputMethodQueryEvent(queries=0x101, {})
1 0 QInputMethodQueryEvent(queries=0x101, {})
QInputMethodQueryEvent(queries=0x101, {})
1 0 QPaintEvent(Paint, 0x7fff5fbfb8d0) QPaintEvent(Paint, 0x7fff5fbfb8d0)
1 0 QEnterEvent(QPoint(660,313)) QEnterEvent(QPoint(660,313))
Process 41198 stopped
* thread #1: tid = 0x2b7bde, 0x000101367a25
libkritaflake.15.dylib`KoShapeManager::paint(QPainter&, KoViewConverter const&,
bool) + 101, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=EXC_I386_GPFLT)
frame #0: 0x000101367a25
libkritaflake.15.dylib`KoShapeManager::paint(QPainter&, KoViewConverter const&,
bool) + 101
libkritaflake.15.dylib`KoShapeManager::paint:
-> 0x101367a25 <+101>: movq 0x28(%rax), %rbx
0x101367a29 <+105>: movq %r12, %rdi
0x101367a2c <+108>: callq 0x101448c94 ; symbol stub for:
KisPaintingTweaks::safeClipBoundingRect(QPainter const&)
0x101367a31 <+113>: cvtsi2sdl %eax, %xmm0
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 372357] Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357
--- Comment #4 from Jelena <jelen...@t-online.de> ---
The last lines of lldb before Krita crashed:
1 0 QEvent(CursorChange, 0x7fff5fbfbda0) QEvent(CursorChange, 0x7fff5fbfbda0)
1 0 QHelpEvent(ToolTip, 0x7fff5fbfcd28) QHelpEvent(ToolTip, 0x7fff5fbfcd28)
1 0 QKeyEvent(ShortcutOverride, Key_Control, ControlModifier)
QKeyEvent(ShortcutOverride, Key_Control, ControlModifier)
1 0 QKeyEvent(KeyPress, Key_Control, ControlModifier) QKeyEvent(KeyPress,
Key_Control, ControlModifier)
1 0 QKeyEvent(ShortcutOverride, Key_S, ControlModifier)
QKeyEvent(ShortcutOverride, Key_S, ControlModifier)
1 0 QEvent(Leave, 0x7fff5fbfbf50) QEvent(Leave, 0x7fff5fbfbf50)
1 0 QEvent(WindowBlocked, 0x7fff5fbfc3d0) QEvent(WindowBlocked, 0x7fff5fbfc3d0)
1 0 QFocusEvent(FocusAboutToChange, OtherFocusReason)
QFocusEvent(FocusAboutToChange, OtherFocusReason)
1 0 QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
1 0 QEvent(WindowDeactivate, 0x7fff5fbfabb0) QEvent(WindowDeactivate,
0x7fff5fbfabb0)
1 0 QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
QFocusEvent(FocusAboutToChange, ActiveWindowFocusReason)
1 0 QFocusEvent(FocusOut, ActiveWindowFocusReason) QFocusEvent(FocusOut,
ActiveWindowFocusReason)
1 0 QPaintEvent(Paint, 0x7fff5fbfa3b0) QPaintEvent(Paint, 0x7fff5fbfa3b0)
1 0 QEvent(WindowUnblocked, 0x7fff5fbfade0) QEvent(WindowUnblocked,
0x7fff5fbfade0)
1 0 QEvent(WindowActivate, 0x7fff5fbfbe48) QEvent(WindowActivate,
0x7fff5fbfbe48)
1 0 QEnterEvent(QPoint(0,0)) QEnterEvent(QPoint(0,0))
1 0 QFocusEvent(FocusIn, ActiveWindowFocusReason) QFocusEvent(FocusIn,
ActiveWindowFocusReason)
1 0 QInputMethodQueryEvent(queries=0x101, {})
QInputMethodQueryEvent(queries=0x101, {})
1 0 QInputMethodQueryEvent(queries=0x101, {})
QInputMethodQueryEvent(queries=0x101, {})
1 0 QKeyEvent(KeyRelease, Key_Return, text="\r") QKeyEvent(KeyRelease,
Key_Return, text="\r")
1 0 QPaintEvent(Paint, 0x7fff5fbfb8d0) QPaintEvent(Paint, 0x7fff5fbfb8d0)
1 0 QEnterEvent(QPoint(269,313)) QEnterEvent(QPoint(269,313))
Process 41035 stopped
* thread #1: tid = 0x2b65f6, 0x000101367a25
libkritaflake.15.dylib`KoShapeManager::paint(QPainter&, KoViewConverter const&,
bool) + 101, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=EXC_I386_GPFLT)
frame #0: 0x000101367a25
libkritaflake.15.dylib`KoShapeManager::paint(QPainter&, KoViewConverter const&,
bool) + 101
libkritaflake.15.dylib`KoShapeManager::paint:
-> 0x101367a25 <+101>: movq 0x28(%rax), %rbx
0x101367a29 <+105>: movq %r12, %rdi
0x101367a2c <+108>: callq 0x101448c94 ; symbol stub for:
KisPaintingTweaks::safeClipBoundingRect(QPainter const&)
0x101367a31 <+113>: cvtsi2sdl %eax, %xmm0
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372357] Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357 --- Comment #2 from Jelena <jelen...@t-online.de> --- Another info: This bug is new in 3.0.92. I switched back to 3.0.91 and doublechecked that adding text and saving worked perfectly with 3.0.91. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372357] Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357 --- Comment #1 from Jelena <jelen...@t-online.de> --- Info: Disabling OpenGL doesn't make any difference. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372357] New: Crash on save after adding text
https://bugs.kde.org/show_bug.cgi?id=372357 Bug ID: 372357 Summary: Crash on save after adding text Product: krita Version: 3.1 Beta Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: Text Tool Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de Target Milestone: --- With the latest beta (3.0.92) Krita crashes most times after adding a text and trying to save the file. Steps to reproduce: 1. Create a new file 2. Add a text (single line or multiline makes no difference) 3. Save Krita crashes without saving the file. If it doesn't crash yet add a second text and save again and you will most probably see the crash. There was a similar bug earlier: https://bugs.kde.org/show_bug.cgi?id=365643 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366823] Consistent direction for changing zoom and changing brush size
https://bugs.kde.org/show_bug.cgi?id=366823 --- Comment #2 from Jelena <jelen...@t-online.de> --- > we do have a heads-up display now where you can extend the popup palette and > drag sliders for these settings You're right! I really like this popup palette especially if working in full canvas mode. This might be a sufficient replacement for an opacity mode. I would suggest one usability improvement: a) close popup palette automatically after changing opacity OR b) Automatically close popup palette when starting to paint. (Currently an additional click is needed to close the palette). Might I add a feature request for this? > I'm not sure about changing the direction of the zoom action; other people > might get upset when it changes. I understand your concerns. However I think a horizontal movemement for changing zoom would be a sane and consistent behaviour - especially as the orientation of the zoom slider both in the status bar and in the overview dock is horizontal (and not vertical) as well. Another option would be to support both horizontal AND vertical movements (even though it would be simpler to only use horizontal movements). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355544] Some tools in toolbox docker can't be used
https://bugs.kde.org/show_bug.cgi?id=355544 --- Comment #9 from Jelena <jelen...@t-online.de> --- Created attachment 101433 --> https://bugs.kde.org/attachment.cgi?id=101433=edit 4 tools don't react and are aligned wrong The four tools (crop, move, transform and measure) also don't align correctly (there's a space at the left side of the crop tool; see attached screenshot). Are they grouped somehow and could we maybe solve the reported bug (and the incorrect alignment) by breaking up the group? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355544] Some tools in toolbox docker can't be used
https://bugs.kde.org/show_bug.cgi?id=355544 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363253] Transform tool in toolbox docker is not responsive when resized to certain sizes.
https://bugs.kde.org/show_bug.cgi?id=363253 --- Comment #8 from Jelena <jelen...@t-online.de> --- The bug I'm referring to has already been reported as https://bugs.kde.org/show_bug.cgi?id=355544 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363253] Transform tool in toolbox docker is not responsive when resized to certain sizes.
https://bugs.kde.org/show_bug.cgi?id=363253 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de --- Comment #7 from Jelena <jelen...@t-online.de> --- I can confirm this on 3.0.1.90 on Mac. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367610] Krita freezes upon file recovery
https://bugs.kde.org/show_bug.cgi?id=367610 --- Comment #6 from Jelena <jelen...@t-online.de> --- @kouame Thanks for working on this! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367684] Crash when using popup palette
https://bugs.kde.org/show_bug.cgi?id=367684 --- Comment #5 from Jelena <jelen...@t-online.de> --- I don't know whether it is the same bug (or related): I can reproduce the following with the nimmy2.dmg: Acitvating "OpenGL" (Trilinear Filtering with "use texture buffer") and then opening the popup palette crashes the app. The app also crashes when deactivating OpenGL and opening the popup palette. However after restarting the app everything works fine (with AND without OpenGL). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367684] Crash when using popup palette
https://bugs.kde.org/show_bug.cgi?id=367684 --- Comment #3 from Jelena <jelen...@t-online.de> --- Still crashes on 3.0.1 final. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368119] Line Tool - strange line to corner
https://bugs.kde.org/show_bug.cgi?id=368119 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de --- Comment #7 from Jelena <jelen...@t-online.de> --- Activating the stabilizer at the brush tool at krita 3.0.99.91 on OSX has another strange effect for me which might be related: I draw a stroke from position A to B, then release the mouse. Then I click at position C to start a new stroke. On mousedown a stroke from C to B gets drawn. When I then start the moving the cursor (with mousedown) a stroke from B back to C gets drawn and only then the stroke starts to follow my mouse as expected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367684] New: Crash when using popup palette
https://bugs.kde.org/show_bug.cgi?id=367684 Bug ID: 367684 Summary: Crash when using popup palette Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de 1. Create a new image 2. Open pop-up palette by rightclicking 3. Click the bottom right small circle button (with a > symbol) 4. Krita crashes immediately Additional bug: If you click the other small circle button and choose "Favorite Presets" nothing happens. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367610] Krita freezes upon file recovery
https://bugs.kde.org/show_bug.cgi?id=367610 --- Comment #3 from Jelena <jelen...@t-online.de> --- I tested it again (even rebooted in between) and I can still reproduce it. The file opens indeed but you e.g. cannot click any tools and have to kill Krita hard in order to get it working again. Another detail: Are you sure the file is completely blank? There should be a long soft brush stroke in the middle of the canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367610] Krita freezes upon file recovery
https://bugs.kde.org/show_bug.cgi?id=367610 --- Comment #1 from Jelena <jelen...@t-online.de> --- Created attachment 100695 --> https://bugs.kde.org/attachment.cgi?id=100695=edit Recovery file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367610] New: Krita freezes upon file recovery
https://bugs.kde.org/show_bug.cgi?id=367610 Bug ID: 367610 Summary: Krita freezes upon file recovery Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de After recovering a file (named .krita-8841-document_0-autosave.kra in my case) Krita doesn't react any longer (i.e. most menu items are greyed out, tools cannot be selected...). If I choose not to recover this file everything works smooth. Reproducible: Always Steps to Reproduce: 1. Place the attached file in your home directory 2. Start Krita 3. Choose OK in the file recovery dialogue in order to recover the file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363779] Undo applies at beginning of stroke
https://bugs.kde.org/show_bug.cgi?id=363779 --- Comment #8 from Jelena <jelen...@t-online.de> --- Oh, I got it wrong then. Thanks for the correction and happy coding! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 367570] New: Add toggle for pick layer mode
https://bugs.kde.org/show_bug.cgi?id=367570 Bug ID: 367570 Summary: Add toggle for pick layer mode Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de CURRENT: I need to hold the R key in order to pick a layer under the cursor. FEATURE WISH: Additionally I can activate this pick-layer-mode by pressing (and releasing) a key once. I can then deactivate the pick-layer-mode by pressing (and releasing) the same key again. REASON: This improves krita usability on graphics tablet because many tablets don't have that many physical keys on the tablet which can be pressed (and hold). However if you can toggle the pick-layer-mode by press of a key you can use a virtual key from the onscreen menu of the tablet to toggle the pick-layer-mode. IMHO the same would apply for other modes such as the rotate mode (activate it with a single key press, then rotate with the mouse) or the mode to change the brush size (activate it with a single key press, then use the mouse to change the brush size) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363779] Undo applies at beginning of stroke
https://bugs.kde.org/show_bug.cgi?id=363779 --- Comment #6 from Jelena <jelen...@t-online.de> --- AFAIK the upcoming release of Krita will fix OpenGL for Mac. :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366825] Only show tabbar when necessary
https://bugs.kde.org/show_bug.cgi?id=366825 --- Comment #6 from Jelena <jelen...@t-online.de> --- Ok. Thanks for investigating this. Maybe Qt will add this feature one day and we can add it to Krita then. We'll see. Thanks and keep up the great work! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366825] Only show tabbar when necessary
https://bugs.kde.org/show_bug.cgi?id=366825 --- Comment #4 from Jelena <jelen...@t-online.de> --- That's bad luck. So I would have to send a feature request to the Qt developers whether they can expose the QTabBar's autohide property to the QMdiArea class? Do you think there's any chance that they would accept such a feature request? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366825] Only show tabbar when necessary
https://bugs.kde.org/show_bug.cgi?id=366825 --- Comment #2 from Jelena <jelen...@t-online.de> --- (In reply to Boudewijn Rempt from comment #1) > I'm sorry, that is not possible technically. But if you switch to > multi-window mode, the tabbar will be gone. Thanks for your fast reply. You're right - the tabbar disappear in multiwindow mode. But unfortunately I get a title bar on top instead which consumes nearly as much space as the tabbar. You say it's technically not possible to implement this idea. What I described in "Step 1" did NOT mean a tabbar which hides automatically and appears on hover. Rather my idea was to simply hide the tabbar permanently and only show it if another file or view gets opened. This is similar to what many tabbed web browsers do. Is this technically impossible as well? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366825] New: Only show tabbar when necessary
https://bugs.kde.org/show_bug.cgi?id=366825 Bug ID: 366825 Summary: Only show tabbar when necessary Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de Currently krita always shows the tabbar which lists the open files / views. I prefer to have as much space for painting as possible (especially when changing to canvas-only mode using the tab key). As a *first step* it would be nice if the tabbar would hide if there's only ONE file or view open. A *second step* could be to hide the tabbar automatically and let it only appear if the user moves the cursor to the upper window border (at least when working in the canvas-only TAB mode). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366823] New: Consistent direction for changing zoom and changing brush size
https://bugs.kde.org/show_bug.cgi?id=366823 Bug ID: 366823 Summary: Consistent direction for changing zoom and changing brush size Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de In zoom mode (Ctrl+Space) you have to drag the mouse UP and DOWN to change the zoom. In brush size mode you have to drag the mouse LEFT and RIGHT to change the brush size. I would be happy if the drag directions would be consistent as I often by mistake drag into the wrong direction when changing zoom and brush size one after another. BTW is there an opacity mode (similar to brush size mode) to change opacity by dragging the mouse? (I already know about the keys 'I' and 'O') -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366818] New: Zoom with pen flickering
https://bugs.kde.org/show_bug.cgi?id=366818 Bug ID: 366818 Summary: Zoom with pen flickering Product: krita Version: 3.0.1 Alpha Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de I programmed a key of my Wacom tablet to toggle zoom mode. Now when I press this key and move my pen up and down for zooming the canvas starts flickering - i.e. the canvas jumps rapidly in random directions while zooming. Reproducible: Always Steps to Reproduce: 1. Set a key of Wacom Tablet to toggle zoom mode (or relative zoom mode) 2. Press this key on Wacom Tablet and keep it pressed 3. Press pen down on the tablet and move it up and down Actual Results: Canvas starts flickering - i.e. the canvas jumps rapidly in random directions while zooming Expected Results: Smooth zoom in and zoom out without flickering I disabled the scrollwheel zoom in the canvas input settings as recommended. This bug does not appear when activating OpenGL. However currently I need to keep OpenGL disabled due to bug #363779. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361813] [WACOM] Wacom CTL-460/Intuos Pro Small+Krita 2.9.11: Stylus Side Buttons Not Working with Click-Based Shortcuts
https://bugs.kde.org/show_bug.cgi?id=361813 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de --- Comment #3 from Jelena <jelen...@t-online.de> --- It's working now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366814] Preview outline cursor doesn't follow the Wacom pen
https://bugs.kde.org/show_bug.cgi?id=366814 Jelena <jelen...@t-online.de> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jelena <jelen...@t-online.de> --- I found this bug which points to a fix in the latest development build: https://bugs.kde.org/show_bug.cgi?id=366523 It really works! Great! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366814] New: Preview outline cursor doesn't follow the Wacom pen
https://bugs.kde.org/show_bug.cgi?id=366814 Bug ID: 366814 Summary: Preview outline cursor doesn't follow the Wacom pen Product: krita Version: 3.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Instant Preview Assignee: krita-bugs-n...@kde.org Reporter: jelen...@t-online.de Using the pen of my Wacom Cintiq with Krita 3.0: When painting using the freehand brush tool the preview outline cursor initially displays fine. However as soon as I finish the stroke and lift the pen the preview outline cursor stays "frozen" at the end of the stroke and does not follow my pen any longer. This means I don't see the preview outline cursor on the screen when I move the pen to a new position. As soon as I click again to paint a new stroke the outline appears again and the whole story repeats. When I activate the crosshair cursor at least the crosshair cursor follows the pen. However the preview outline still stays frozen. This bug exists with and without having OpenGL activated. Good to know: When leaving the canvas with the pen and moving back to the canvas the frozen preview outline jumps back in place and starts following the pen again. When using the mouse instead of the Wacom Pen everything works fine (the outline cursor follows the mouse cursor as expected). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363779] Undo applies at beginning of stroke
https://bugs.kde.org/show_bug.cgi?id=363779 --- Comment #3 from Jelena <jelen...@t-online.de> --- Good news. I discovered that you can workaround this bug by disabling Preferences - Display - OpenGL. This might have other side effects but at least now we can draw again using Mac OS X. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364173] Tablet proximity events zoom out image to the smallest size
https://bugs.kde.org/show_bug.cgi?id=364173 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363779] Undo applies at beginning of stroke
https://bugs.kde.org/show_bug.cgi?id=363779 Jelena <jelen...@t-online.de> changed: What|Removed |Added CC||jelen...@t-online.de --- Comment #2 from Jelena <jelen...@t-online.de> --- Same here. Mac OS X 10.11.6, Krita 3.0. After Stroke and Undo and Starting a new stroke the previous stroke gets removed - but even then it doesn't get removed completely but a light shadow remains. This shadow only disappears if you paint something else close to the previous shape (you see that rectangle parts of the screen get refreshed step by step). -- You are receiving this mail because: You are watching all bug changes.
