- User Since
- Jul 12 2017, 12:22 AM (118 w, 6 d)
Fri, Oct 11
Sun, Oct 6
- It could be just a rule: "if you add anything to settings, make sure it doesn't make it bigger than [maximum allowed size]".
- It could make other things inaccessible. But it should be enough for the user to be able to disable HiDPI mode.
- would work, but... I don't want to see the scroll view there. If it's gonna be an automatic one, that hides itself if it's not needed, then sure, but... it's just ugly and inconvenient. I dislike the scroll view with categories, too.
- Like 2., should be enough for disabling HiDPI mode.
- Like 2. and 4., should be enough to disable HiDPI mode.
Sat, Oct 5
Wed, Oct 2
Mon, Sep 23
Sep 18 2019
Sep 16 2019
Sep 14 2019
Sep 13 2019
Sep 12 2019
Sep 11 2019
Sep 10 2019
Sep 5 2019
"Oh no I'm sure I saved but the file is nowhere to be seen" can also be a result of user saving to AppData/Temp because that's where autosaves are being saved, and if you load an autosave, I think Krita later suggest this wild location to save the file as.
Sep 2 2019
I can translate to Polish when you finish the English text.
Aug 31 2019
That doesn't sound good: https://www.reddit.com/r/krita/comments/cxn349/krita_will_not_open_kra_file/ :( Will gather more information later (right now it's only the post), but I wanted to link it here before I forget.
Aug 30 2019
Aug 29 2019
Aug 27 2019
Aug 23 2019
Can you copy-paste the OpenGL Info section from help->show system information for bugreports
I added a link from my collection of links that mentions lldb and how to use it, I think I knew it from someone on IRC but can't say if the instruction is correct or not.
I added more explanation what I want from the explanation about tablet drivers.
Aug 22 2019
Aug 21 2019
Aug 15 2019
Aug 14 2019
Aug 4 2019
re-opening Krita should offer to recover the autosave file
Jul 30 2019
Jul 21 2019
Jul 19 2019
Jul 17 2019
Jul 11 2019
Jul 9 2019
Jul 8 2019
Anna Medonosová wrote:
(About the "Related" links about Dropbox issues and the workaround):
Anna Medonosová wrote:
I managed to reproduce it that way:
Open a big animation file.
Add a new layer on top of everything.
Add a new frame on 0th.
Draw something on it.
Wait for autosave to kick in and finish its work. (Save during autosave most probably won’t work, either, but it will leave the file unsaved, so Krita will ask whether we want to close it or not)
Save the file.
Very quickly click “X” on the window top bar; Windows ask if it should close Krita; don’t do anything
Krita will start responding and it will close just after that.
No saved file anywhere.
Not sure how reproduceable it is in general. Also there is that additional thing that Windows ask what to do with unresponding Krita - no one reported it beforehand.
I guess it happens when Krita is busy for example making a copy of the image and maybe that happens before Krita starts blocking itself because of the saving going on…