[krita] [Bug 358146] Window size and position are not saved
https://bugs.kde.org/show_bug.cgi?id=358146 zottg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #3 from zottg --- Sorry, I tested this a little more and this is still an issue, despite the information in https://bugs.kde.org/show_bug.cgi?id=349165 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349165] Krita's Window not resizing properly, maximize button not working either
https://bugs.kde.org/show_bug.cgi?id=349165 --- Comment #12 from zottg --- Some clarification on the behavior on 3.0 alpha. It seems that Krita thinks it's starting in full screen mode, but the UI is clearly not displayed as such. It appears like another window. If you try to resize the window, you get odd behavior, as described in https://bugs.kde.org/show_bug.cgi?id=349165#c11 If you try to move the window, it doesn't work. If you double click the title bar to max/min the window, the window won't change, but the min/max icon on the top right (in MS Windows) will change to reflect that it's now in window mode. Now the window can be moved and resized without any odd behavior. If you close Krita now and reopen, everything will be fine. If you close Krita while it's maximized and reopen, this bug will happen again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358146] Window size and position are not saved
https://bugs.kde.org/show_bug.cgi?id=358146 zottg changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from zottg --- After some more inspection, it appears this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=349165 *** This bug has been marked as a duplicate of bug 349165 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349165] Krita's Window not resizing properly, maximize button not working either
https://bugs.kde.org/show_bug.cgi?id=349165 --- Comment #13 from zottg --- *** Bug 358146 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358718] New: When at min width, tools docker UI overlaps timeline docker
https://bugs.kde.org/show_bug.cgi?id=358718 Bug ID: 358718 Summary: When at min width, tools docker UI overlaps timeline docker Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Enable timeline docker. 2. Place timeline docker at bottom of window. 3. Resize tools docker to be 2+ columns 4. Resize tools docker to be 1 column wide Actual: The icons in the tools docker overlaps the timeline docker. Expect: The UI should prevent the user from resizing a docker smaller than the content can fit. In this case, since there isn't enough vertical space to have a single column of tools, the UI should set the minimum width to what will accommodate the tool icons. 5. Click on any of the icons that overlap the timeline docker. Actual: The timeline docker shrinks to minimum height. Expect: This to not happen. May be related to https://bugs.kde.org/show_bug.cgi?id=355544 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358717] Unable to dock timeline to bottom of window once it's removed
https://bugs.kde.org/show_bug.cgi?id=358717 zottg changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358717] Unable to dock timeline to bottom of window once it's removed
https://bugs.kde.org/show_bug.cgi?id=358717 --- Comment #1 from zottg --- After some more fooling around, it seems the ability to dock to the bottom of the window depends on the sizes of the docks on the sides. If both side docks are at their minimum width, then you can't dock to the top or bottom of the window. If you resize either side dock to increase its width a little, then you can attach the timeline to the top or bottom. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358717] Unable to dock timeline to bottom of window once it's removed
https://bugs.kde.org/show_bug.cgi?id=358717 --- Comment #2 from zottg --- Downgraded to minor, since there's a work around. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358717] New: Unable to dock timeline to bottom of window once it's removed
https://bugs.kde.org/show_bug.cgi?id=358717 Bug ID: 358717 Summary: Unable to dock timeline to bottom of window once it's removed Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Add timeline docker 2. If the timeline docker is at the bottom of the window, drag it away so it detaches. 3. Click and drag the timeline docker to the bottom of the window Expect: Timeline to attach to the bottom of the window Actual: This doesn't happen. FWIW, the docker can still attach to the side of the window, where the layers docker is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349165] Krita's Window not resizing properly, maximize button not working either
https://bugs.kde.org/show_bug.cgi?id=349165 zottg changed: What|Removed |Added CC||zottgram...@gmail.com --- Comment #11 from zottg --- Something similar is happening on the 3.0 alpha on Windows 10. When I try to resize vertically, the window sizing is super sensitive. So just moving my mouse down a little (a few pixels) causes the window to shift off the screen. I'm not sure if it's shifting off screen or just resizing so fast that the window's top position falls of the bottom of the screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358619] New: Moving a layer to the top is annoying
https://bugs.kde.org/show_bug.cgi?id=358619 Bug ID: 358619 Summary: Moving a layer to the top is annoying Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Have at least 2 layers. Layer 1 and 2, 2 is at the top. 2. Try to click and drag and move Layer 1 above layer 2. There is a 1 pixel window/border where the cursor has to land and release to allow this move. This is a very precise requirement for a simple and common action. It seems to be an inefficient UX. Suggest: Increasing the target size to something like 10pixels or so to make it easier to 'land' on it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357460] Copy/pasted content shifts when a keyframe is created on a new layer
https://bugs.kde.org/show_bug.cgi?id=357460 zottg changed: What|Removed |Added Version|2.9.10 |3.0 Alpha -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357460] Copy/pasted content shifts when a keyframe is created on a new layer
https://bugs.kde.org/show_bug.cgi?id=357460 --- Comment #2 from zottg --- This still occurs in the 3.0 pre alpha -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357619] Moving a layer and undoing the move positions the layer in the wrong place.
https://bugs.kde.org/show_bug.cgi?id=357619 --- Comment #5 from zottg --- This is fixed for me in the 3.0 pre alpha. Can reporter confirm as well? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358148] New: Export/import settings/keymap or automatically do it when upgrading from previous versions
https://bugs.kde.org/show_bug.cgi?id=358148 Bug ID: 358148 Summary: Export/import settings/keymap or automatically do it when upgrading from previous versions Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com I upgraded from the 2.9.10 animation beta to 3.0 pre alpha. None of the keymaps or settings were persisted/imported from the previous version. The most ideal solution would be to prompt the user to import the settings or not. Another solution would be to provide an import/export settings & keymap option so the user can do so manually. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 zottg changed: What|Removed |Added Severity|grave |crash --- Comment #3 from zottg --- Degraded severity. Read the release notes more. It's related to the Intel graphics chip/disable OpenGL work around. If I disable OpenGL in settings and restart, everything's OK. But this makes animation playback really choppy and unreliable. Keeping this open because Krita crashes. The release notes just said the screen might go black. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 --- Comment #2 from zottg --- May be related to https://bugs.kde.org/show_bug.cgi?id=334497 https://bugs.kde.org/show_bug.cgi?id=335382 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 --- Comment #1 from zottg --- It turns out that Krita will crash from just creating a file as well. 1. Open Krita 2. Create a new file 3. Crash Right before the crash, a warning box appears and says, "You have an Intel(R) HD Graphics". Immediately after the program crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 zottg changed: What|Removed |Added Summary|Crash when trying to open a |Crash when trying to open |file from 2.9.10 animation |or create a file |beta| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open or create a file
https://bugs.kde.org/show_bug.cgi?id=358147 zottg changed: What|Removed |Added Severity|crash |grave -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358146] Window size and position are not saved
https://bugs.kde.org/show_bug.cgi?id=358146 --- Comment #1 from zottg --- May be related to https://bugs.kde.org/show_bug.cgi?id=335923 https://bugs.kde.org/show_bug.cgi?id=331819 Both were fixed but I don't know if they've been included in the 3.0 pre alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] Crash when trying to open a file from 2.9.10 animation beta
https://bugs.kde.org/show_bug.cgi?id=358147 zottg changed: What|Removed |Added Component|Animation |general -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358147] New: Crash when trying to open a file from 2.9.10 animation beta
https://bugs.kde.org/show_bug.cgi?id=358147 Bug ID: 358147 Summary: Crash when trying to open a file from 2.9.10 animation beta Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Launch Krita 2. Open a Krita file that was made with 2.9.10 animation beta. The file doesn't need to have any animation frames in it. 3. Krita crashes Windows 10 64bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358146] New: Window size and position are not saved
https://bugs.kde.org/show_bug.cgi?id=358146 Bug ID: 358146 Summary: Window size and position are not saved Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Launch Krita 2. Resize and reposition window 3. Close Krita 4. Open Krita 5. Previous size and position settings are not saved Windows 10 64bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357241] [Animation] Unable to remove/hide layer from timeline without deleting it
https://bugs.kde.org/show_bug.cgi?id=357241 zottg changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from zottg --- Ah, I was confused by the UX. There seems to be a bug in the "Show in timeline" checkbox. 1. Create new document 2. Create a new layer (should have layer 1 and 2 now) 3. Click on layer 1 4. Go to timeline view 5. Timeline menu/Add existing layer/Layer 2 Now the timeline shows both Layer 1 and 2 6. Click on Layer 2 7. Observe "Show in Timeline" checkbox Expect: It should be checked since we just added Layer 2 to the timeline Actual: It's unchecked 8. Timeline menu/Show in Timeline. Note: Since Layer 2 is already set to be shown in the timeline, this should now hide the layer. 9. Observe the Timeline menu/Show in Timeline. Expect: Show in timeline checkbox is unmarked Actual: Show in timeline checkbox is checked -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357502] New: Undoing should not separate keyframe selection
https://bugs.kde.org/show_bug.cgi?id=357502 Bug ID: 357502 Summary: Undoing should not separate keyframe selection Product: krita Version: 2.9.10 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com I noticed that selecting keyframes is considered a unique action that has its own entry in the undo history. Personally I prefer if it wasn't or if they were collapsed to the last action that actually modified a layer. Current experience: 1. Draw something on keyframe 1 2. Select keyframe 3 3. Select keyframe 2 4. Undo Actual: Goes back to 2, where keyframe 3 was selected Expect: Go back to step 1. That is, select keyframe 1 and undo the drawing action. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356379] Requesting features for animation such as animated .gif support, video export options, audio import support, and easier keyframe copy/paste.
https://bugs.kde.org/show_bug.cgi?id=356379 zottg changed: What|Removed |Added CC||zottgram...@gmail.com --- Comment #2 from zottg --- Related to https://bugs.kde.org/show_bug.cgi?id=342479 I think GIF/video export support would make sense for Krita, given it seems animation is intended to be part of it's feature-set. Having to export every single frame and then composite it in another program is an awkward and clunky user experience. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356646] Animation Beta - Cannot select start frame over 99
https://bugs.kde.org/show_bug.cgi?id=356646 zottg changed: What|Removed |Added CC||zottgram...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357488] New: Undoing moves is broken
https://bugs.kde.org/show_bug.cgi?id=357488 Bug ID: 357488 Summary: Undoing moves is broken Product: krita Version: 2.9.10 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com Undoing a move on a layer doesn't put the layer back at the original spot. 1. Create new image 2. Draw something 3. Move the image 4. Undo Expect: Image to return previous position Actual: Image is offset. It appears that the offset is proportional to the direction of the movement. For example, if I draw an X in the center of the image and move halfway towards the bottom right corner, then after undoing the x is moved to the top left corner of the image. So it's almost like a scale of -2 is being applied to the translation vector. May be related to: https://bugs.kde.org/show_bug.cgi?id=357460 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357487] New: Allow keyframing on groups
https://bugs.kde.org/show_bug.cgi?id=357487 Bug ID: 357487 Summary: Allow keyframing on groups Product: krita Version: 2.9.10 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com It'd be nice to keyframe groups. Then transformations can be applied to a group uniformly. Example: Panning/rotating/zooming scenes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357460] Copy/pasted content shifts when a keyframe is created on a new layer
https://bugs.kde.org/show_bug.cgi?id=357460 --- Comment #1 from zottg --- May be related to: https://bugs.kde.org/show_bug.cgi?id=355968 https://bugs.kde.org/show_bug.cgi?id=356540 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357460] New: Copy/pasted content shifts when a keyframe is created on a new layer
https://bugs.kde.org/show_bug.cgi?id=357460 Bug ID: 357460 Summary: Copy/pasted content shifts when a keyframe is created on a new layer Product: krita Version: 2.9.10 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com Copy/pasted layer contents shift when creating the first keyframe for that layer. Reproducible: Always Steps to Reproduce: 1. Create a layer, draw on it 2. Create a keyframe for that layer 3. Now copy something from that layer and paste it. A new layer is created 4. Create a keyframe for that new layer. Actual Results: The drawing shifts position on the layer. It looks like krita is trying to center the pasted content. Expected Results: No position shifting. A key frame should simply be created for the layer's content without any modification to the layer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357241] New: [Animation] Unable to remove/hide layer from timeline without deleting it
https://bugs.kde.org/show_bug.cgi?id=357241 Bug ID: 357241 Summary: [Animation] Unable to remove/hide layer from timeline without deleting it Product: krita Version: 2.9.10 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com I added a layer to the timeline using: Add existing layer Now whenever I select a different layer to edit, that other layer will always appear I don't see an option to disable that without actually deleting the layer and content from the project Reproducible: Always Steps to Reproduce: 1. Animating on Layer 1 2. Create new layer 2 3. Create new layer 3 4. Select layer 2 from the Layers panel 5. Add Layer 1 to timeline with the above option 6. Layer 1 now appears in timeline 7. Select layer 3 8. Layer 1 appears in timeline 9. Select Layer 1 10. Select Remove Layer from timeline menu Actual Results: Layer 1 is deleted Expected Results: Layer 1 is hidden from timeline, but is still in the project Tried: Select the "Remove layer" option from the timeline. This causes the layer to actually be deleted, which is not the intent. The intent is to hide the layer from the timeline. Hiding layer 1 Krita 2.9.10 animation beta Windows 10 64bit -- You are receiving this mail because: You are watching all bug changes.
