I tested Sessions. (Never used this feature before and I don’t have a multi-monitor setup.) macOS 10.13.6 krita-nightly_b117b85
Sessions dialog (New)
-New session item with unique name works.
-New session item with pre-existing name from the list fails. (Works in 4.4.8 but with broken session switch until restart when it gets renamed to file name) (Tiar: I mean it still fails, but now it gets an error message).
-Picking a name that was previously used by another item that got renamed and still exist in the list doesn’t work.
Sessions dialog (Rename)
-Rename works only once per item.
-Selecting another item after renaming turns Rename… Switch to and Delete… -buttons unclickable/greyd out when the renamed item is re-selected.
-It’s possible to have several items renamed to the same name if created with unique name first. Then if you create another item twice with the same name as the renamed items(that all have the same name) the other items can get renamed.
Sessions dialog (Switch to…)
-Works unless it’s an renamed item.
-Switching to a session created with Krita 4.4.8 with documents opened throws an error dialog telling the files does not exist. Creating a session with the same documents in Krita 5 works.
-Window disappear after switching from a session with fullscreen mode to one without. With the Sessions… list still open one can go back to a fullscreen session to restore the window, then leave fullscreen mode and then switching session works correctly.
Sessions dialog (Delete…)
-Works on items that haven’t been renamed.
-Delete after rename works if no other items is selected inbetween.
-Unable to click button when item was renamed and another selected beforehand.
Sessions dialog (Correct/not empty MD5 sum in the database)
-Renamed items have the MD5 sum of the un-renamed file.
-Other items have correct check sum.
So I checked why those brush tips are not imported, and it looks like Krita does accept vbr brush tips, they are treated the same way as gbr brush tips. However that one particular pack cannot be loaded because basically the bytes are really weird, the spacing value is completely incorrect, but then I checked what the “version” is and it’s the version 760627794 (it means the bytes are just nonsense to Krita)… I can’t make GIMP recognize those brush tips either (though I’m not super experienced with Gimp). I think those brush tips are just too ancient format-wise.
I don’t know if this is the right place, but it has also something to do with tags and maybe it is worth of implement it into the tags test routine.
I noticed that Krita 5.0.0 beta1 does not load the tags stored in the folders using resource manager when I delete the database and krita has to recreate the database again. However, the tags i created, all all others are saved as .tag files in the brush preset folder. Could please someone confirm this so I can write a bug report? (I use macOS)
I think I used to indicate issues that has been fixed, but that’s a bit invisible, so now I’m going to replace with . I hope that will be a better strategy.
I will test brushes tonight, best with the nightly build right? But it may be that I do not understand everything and then write in the result in which points I do not know what I have to do.
@tiar Hard to test the nightly build on macOS cause all available nightly builds doesn’t include the binary to execute, and more than the half is missed, the size is less then half than the krita 5.0.0 beta1.
EDIT: I see this is only related to Krita Plus, and not Krita Next. It is a bit confusion. I thought Krita Plus is the nightly for 5.0, and Krita Next is for 5.1
Then i test the Krita Next 5.1 prealpha and post the hash with the test.
I tested Brushes now, macOS 11.6, krita-nightly_0a92c54.dmg (5.1.0-prealpha 0a92c54)
Brush Editor (Change option; reload original preset)
Brush Editor (Change option; save new brush preset)
Brush Editor (Change option; overwrite preset)
Brush Editor (Switch to another brush inside Brush Editor)
Brush Editor (Remove one of the default presets)
Brush Editor (Remove a preset from bundle_modified) (found no bundle_modified, did it with my own bundle i created and removed a preset from it)
Brush Editor (Add new preset in an engine)
Brush Editor (Remove a custom preset)
Brush Editor (Filter by engine)
Brush Editor (Rename a default preset)
Brush Editor (Select Ink Brush Rough and try to paint)
Brush Editor (Draw in the brush settings scratchpad)
Brush Editor (Click on the lock icon in Brush Editor)
Brush Editor (Create a new EMPTY preset in the brush engine, then edit its name)
Brush Editor (Clicking on “Temporarily save tweaks to presets”)
Brush Editor (shortcut to call it (F5 by default), and then maybe close?)
Brush Editor (Overwrite a preset)
Brush Editor (Rename a brush preset)
Toolbar dropdown (Import a preset)
Toolbar dropdown (Remove a default (unchanged) preset from a bundle)
Toolbar dropdown (Remove a preset that was default from a bundle, but then you overwrote it with your own changes)
Toolbar dropdown (Remove a custom preset (a new one that you created))
Brush Presets docker (Switching a tag shouldn’t remove a selection of the brush (selection = highlighting in the listview widget), unless the new tag doesn’t contain that preset)
Brush Presets History (Changing the current brush preset should make that one selected in both Brush Presets History and in the Brush Presets docker)
Brush Presets docker (Brush presets should be sorted by name)
“bundle_modified” means that you first edit a preset that comes from a bundle; for example “d) Ink-2 Fineliner” (and overwrite it, so it’s saved into the resource folder so the changes are available after restart). Then you remove that preset.
I cannot reproduce this one on Linux Btw does it work for you in Krita 4.4.8?
I fixed all other things I could. I guess the fix for md5 might fix some other bugs since it was a fix for all resource types… For the rename I’ll need to talk with Halla, and the Krita 4.x session incompatibility is a serious thing and I’ll try to fix that tomorrow or find someone else who could be responsible for that (preferably the person who broke it ). The fixes should be available in the next nightly build (Krita Next).
I’ve found a bug where clicking the eraser mode icon on the toolbar won’t work when using a mypaint brush present, unless the “E” key is pressed first to switch to eraser mode. Or if the eraser checkbox is clicked in brush settings
If i move the brushtip in the brushes folder into a subfolder, my custom preset that use this brushtip has an X now to show me some resource are missing. but it shows the brushtip in the library and the preset also uses the brushtip. Is this already known?
EDIT: It looks like this issue is only for the beta1, in todays nightly it is fixed.
I found a bug that causes data lose, it is critical in my opinion. @tiar
Krita can’t “fast save” to files with certain characters after the document is opened in a new session (second session). The tested characters are ä, ü, ö. Also overwriting with “save as” doesn’t work. Krita doesn’t show an error message, but there is no save bar at the bottom if you recognize it. Also on normal app exit when krita asks if you want to save the change and you say yes, it doesn’t save and krita exit normaly. And all the progress can be lost from this session, this is critical in my opinion because on this normal exit the autosave file is also deleted.
Tested with macOS 11.6, krita 5.1 prealpha from today and 5.0 beta1.
Steps to reproduce:
Create a new krita file that countains ä, ü, ö, é, à, è in the filename.
Save a few times after small edits. It should work (most of the time in the first session)
Exit krita completely, open krita, open the file again
Try to save with the shortcut, or save or save as
In most cases the first one works, then it doesn’t work for all later tries, never for me!
EDIT: It looks like krita doesn’t exit always if you say yes and was not able to save.
Guys does anyone test the new nightly? Sometimes i don’t know… there are face punshing bugs you recognize immediataly but then you see no other people recognize it or even take a look into it.
Create a new brush and try to apply a texture in the new nightly, does it work? no…
Also not the brushes created in the beta1, the texture simply don’t apply. But it is shown in the library and you could select it.
I’m no longer able to reproduce it the same way as before. (krita-nightly_b117b85, krita-nightly_8c43c42, krita-nightly_96794d1)
What I see now:
– Closing the session dialog now restores the invisible window after switching from single fullscreen window to windowed mode session.
– Opening the session dialog on the fullscreen view and then switching to one windowed session will result in correct behaviour.
– Going from one fullscreen + one windowed view session to a one windowed view can cause empty fullscreen views (sometimes with full menubar, sometimes with bare bone one).
– Going from one fullscreen + one windowed view session to a two windowed view session will sometimes have one of the windows disappear (if the visible window is selected before closing the session dialog I believe).
If the visible window is closed the software remains open with no windows as shown before. Quitting krita from menu item or by keyboard shortcut does nothing. Quit from dock menu works.
I’m able to reproduce the same behaviour in 4.4.8. Might be a macOS High Sierra only windowing bug?
Crashed x 3
Krita Next Sep 30 x64 5.1.0-prealpha f4c5ba267d Windows 10
SUMMARY: I got 3 crashes out of 5 tests and each time the crash occurred when I edited a brush using the brush editor while Fill was the active tool. The exact moment of crashes is when I closed the Brush Editor and selected B. In test where I made the switch to Brush tool before using the Brush Editor, no crash.
Test 1
Opened an existing document
Ctrl-A delete to clear contents
Filled empty layer with colour using Fill tool
INS to create new layer, renamed new layer
Opened Brush Editor - Changed from Basic-5 to Basic-1.
Edited Basic-1
Closed Brush Editor
Selected B for Brush tool
Krita crashed
Test 2
Duplicated steps in test 1. Krita crashed a second time.
Test 3
Same steps as 1 and 2 except this time I created a fresh document
Filled layer using Fill Tool
Created new layer, renamed it
Opened Brush Editor - Changed from Basic-5 to Basic-1.
Closed Brush Editor
Selected B for Brush tool Krita crashed (this is 3rd crash in a row)
Test 4
Restarted Krita, created new document
Filled using Fill tool.
Changed to Brush tool (this is where I varied from previous tests)
Basic-5 was selected. Changed to Basic-1 using Presets Docker.
Made a stroke, worked as expected.
Opened Brush Editor, edited Basic-1 as in prev. tests.
Closed Brush Editor. Worked as expected. I painted for several minutes with no problems.
Test 5
Just for the heck of it, I recalled the existing document used in tests 1 and 2 (in case there was some influence from doc created in previous Krita version). Redid the test that originally caused crashes except that this time I changed the tool from Fill to Brush before accessing the Brush Editor. No problems. Painted for several minutes, edited several brushes and painted with them.
Is it known that in beta1 and latest nigthly sometimes many resources are missing that you have selected when you create a new bundle? Sometimes it is even empty. But mostly patterns and brush tips are missed.
(Tiar: I mean it still fails, but now it gets an error message).
to indicate issues that has been fixed, but that’s a bit invisible, so now I’m going to replace 
(found no bundle_modified, did it with my own bundle i created and removed a preset from it)
Btw does it work for you in Krita 4.4.8?
). The fixes should be available in the next nightly build (Krita Next).
Crashed x 3