Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0

Develop Artists Feedback & Testing
1

(Structured/thorough) Beta testing of resource system in Krita 5.0

I thought it would make sense to make a bit more structured beta testing of the resource system. The idea is: there are multiple sections in the resource system. They all need to be thoroughly tested, but it’s a lot of work. It would be better to divide the work into multiple testers. However, some sections are more often used than others. Hence, when testers just choose what they want to test, it will be usually the same things: brush presets, maybe bundles. And not everyone knows how to report issues efficiently.

Solution: a list of sections, where volunteers and/or developers can assign a specific section for themselves (can be more than one person for a section, but one section with 5 testers and another with 0 would be bad). Every section will have a list of example actions to test/check, but doing things outside of the list is encouraged, too. Ideally, I’d like to have every section being tested at least by two different people.

I assigned myself to “Bundles” already since I’ve seen some complaints about it, and I have a few minor known bugs to fix so I’ll be testing this part more thoroughly.

If you say that you’ll test some section and you end up not doing that, or doing just partially, then it’s completely fine, just write a comment about it so we know about it.

Also huge thank you for everyone who decides to participate in this action, I really really appreciate it and I know future users will appreciate it too.

Btw the pictures below are derivatives from @deevad 's work on the building Krita manual.

deevad_process
deevad_process482×325 139 KB

Process

  1. Tell in the comment below which section you want to test. I’ll add you to do the list.

  2. Test the section in the latest version of Krita 5.x you can get.

  3. Write a comment with:

    • which section you tested (in case you assigned yourself to multiple ones),
    • in which version (if beta, write beta1 or beta2 etc., if Krita Next, write the hash value; you can get it in Help -> Show system information for bug reports)
    • what are your general feelings (so if everything works, please do write that everything worked well/as expected in your tests, don’t just not write a comment because “everything works so there is nothing to say” since “everything’s fine” is an information, too).

  4. Write down every issue you encountered.

deevad_crying
deevad_crying480×365 100 KB

How to write about issues

  1. Write in a way you’d like someone to write a tutorial for a specific technique for you. Which means: precise, step-by-step don’t omit “obvious” (but not trivial) steps, don’t assume the person reading will know what you did. When in doubt, better write it out.

  2. If you see some “magic” happening, like “something appeared”, tell what exactly appeared and when it appeared (after some action you did? After a restart of Krita? etc.). Usually it’s not magic, but there is some detail that makes it behave this way: and this detail is crucial to fix the issue, which means, we gotta know all the details and then maybe we’ll be able to figure out which detail was the “guilty” one. (For example there is a known bug that brush tips from .abr files can’t be saved into bundles, so knowing which preset and what is the brush tip it uses is crucial to figure out whether the bug you’re experiencing is the same known one, or something new).

deevad_teaching
deevad_teaching543×398 140 KB

Tips for beta testing

  1. The more up-to-date version you use, the better; best way: download Krita Next the morning you start beta testing. But if you don’t want to bother with it, using the latest beta (now: beta1, but if we release beta2, please do update) is fine.

  2. Pay extra attention to what you’re doing (remember steps you’ve taken) and what is happening, for example if you can’t find a resource in the resource chooser for that resource type, check if it exists in the Resource Manager, and check in the resource folder itself if it exists and what is the situation.

  3. Try to break things; do something unusual, things that you don’t think Krita can handle. Like saving a bundle to inexistent directory (…for which there is a bug report already). Note that “Krita didn’t tell me that an action was unsuccessful” is a bug/issue, too.

  4. Bonus points if you know what a database is and you can check out the sqlite database for resources; I use little program called “DB Browser for SQLite”. This is the “behind the curtain” info Krita keeps about resources.

deevad_preparing
deevad_preparing522×211 84 KB

Before you start (how to back up things)

  1. Back up Resource Folder: Easiest way is to go to Krita, go to Settings → Manage Resources → Open Resource Folder and then go one folder up, and back up the whole krita folder. Keep it in a safe place.

  2. Back up configuration: Krita FAQ — Krita Manual 5.0.0 documentation - note that the files you might want to backup are: kritarc (general configuration), kritadisplayrc (display information: like whether to use OpenGL acceleration for the canvas, very important), kritashortcutsrc (custom shortcuts you haven’t saved into a shortcuts scheme), klanguageoverridesrc (keeps information about your custom language for Krita, if it’s different from the system language).

deevad_dictionary

Dictionary

  • Resource - one of: Brush Tips; Gamut Masks; Gradients; Layer Styles; Brush Presets; Palettes; Patterns; Sessions; Symbols (Symbol/Vector Libraries); Task sets; Window Layouts; Workspaces

  • Resource folder - one specific folder where the user can see all of the resources available for Krita. The user can choose a different location for the resource folder in Configure Krita -> General -> Resources.

  • Resource cache - the SQLite database file called resourcecache.sqlite that contains information about all the resources, but doesn’t actually have the resources inside. Though it does contain tags. Apparently you can choose the location of the cache too. By default, it’s located in the resource folder.

Special forum badges for all participants

I made a special badge for everyone who is participating in this initiative or more general beta testing of Krita 5.

How to get it: either participate in this beta testing of the resource system, or contribute to beta testing and improvement in some other way (for example make a bug report that was accepted by a developer, or report issues with Krita 5 on a thread etc.). It’s assigned manually by admins. Please do remember that the goal of it all is to improve Krita, not to get a badge :stuck_out_tongue: but if you did help already, you can nudge the admins to get it.

What can you do with it: you can click on your profile, then go to Badges, then find this badge, click on it, and then there will be a button or something “Use it as a user title”. Then a text “Krita 5 Beta Tester” will appear next to your nickname in every post.

The badge is similar to this emoji:

:microscope:

Sections that have no testers yet:

  • Brush Presets
  • Document
  • Patterns
  • Resource Manager
  • Resources
  • Search
  • Workspaces
  • Others
  • Resource folder & cache shenanigans

Sections that still need more beta testers:

Sections

A: Brush Preset Editor

Tests
  • Edit the name (to a unique one) and save the preset
  • Create New Brush Preset with unique name
    • RGBA brush tip
    • masked brush
    • animated RGBA brush tip
    • brush tip from an ABR storage
  • GRTT-1, GRTT-2, GRTT-3, GRTT-4

B: Brush Presets

Tests
  • Mypaint presets - Should have icons when you create a new one
  • Mypaint presets - Should have icons when you create and then import a bundle
  • Mypaint presets - Loading mypaint brushes from a bundle
  • Mypaint presets - Overwrite a mypaint preset after changes
  • MyPaint presets - Create New mypaint preset
  • Mypaint presets - Save a mypaint preset into a bundle
  • Resource Manager - Import Resources → Import a MyPaint Preset (what about the thumbnail?!)
  • Presets with .abr tips (Loading brush presets with .abr brush tips)
  • Selected preset (Preset selected when you restart Krita is the same one you see on startup next time)
  • Selected preset (Check the behavior on creating new documents, changing the current preset, and then closing all of them)

C: Brush Tips

Tests
  • ABR brush tips library (Download 3 Set of Eyes For Character Doodles Brushes - Free Photoshop Brushes at Brusheezy! and see that there are more than just one brush tip)
  • Import in Brush Editor (Import in brush editor, then select as a brush tip for the current preset)
  • Brush tips chooser (Loading brush tips from inside a folder inside /brushes/)
  • Brush Tips chooser (Import a .abr library)
  • GRTT-1, GRTT-3, GRTT-4 (just open the brush tip file in Krita and then save to overwrite - do it twice, because there was a bug in doing it the second time) in brush tip chooser

D: Brushes

Tests
  • Brush Editor (Change option; reload original preset)
  • Brush Editor (Change option; save new brush preset) - GRTT-3
  • Brush Editor (Change option; overwrite preset) - GRTT-4
  • 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)
  • Brush Editor (Add new preset in an engine) - GRTT-3
  • Brush Editor (Remove a custom preset)
  • Brush Editor (Filter by engine)
  • Brush Editor (Rename a default preset)- GRTT-2
  • 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) - GRTT-4
  • 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)
  • Brush Presets docker (Is switching brush presets fast)
  • Brush Presets docker (Switching brush presets with /)
  • Brush History docker (Switching brushes)
  • Brush History docker (Switching brushes after you delete one of them)

E: Bundles

Tests
  • Bundle Manager (Activate/deactivate bundle)
  • Bundle Manager (Create - the bundle needs to be importable)
  • Bundle Manager (Create - make sure it embeds brush tips without asking)
  • Bundle Manager (import a bundle)
  • Bundle Manager (Create - make sure it embeds tags you asked it to)
  • Bundle Manager (Open Bundle Manager with for example wojtryb’s bundle (long name))
  • Bundle Management (Remove a bundle from the resource folder (manually in the file browser), next time you open Krita, Krita should remove the bundle from the list (forget about the non-existent bundle))
  • Bundle Management (Create a bundle with resources from subfolders)
  • Bundle Creator (Create a bundle with metadata and import it)
  • Bundle Management (Potential issue: Krita doesn’t start if all the bundles are deactivated)
  • Bundle Manager (Correct metadata and a thumbnail for a selected bundle)
  • Resource Manager (import a bundle using “Import Resources” button)

F: Document

Tests
  • Layer Styles (Loading a file saved in 4.4.1 with layer styles - make sure that it contains a pattern and a gradient)
  • Layer Styles (Loading in 4.4 a file saved in 5.x with layer styles)
  • Layer Styles (Loading a file saved in 5.x with layer styles)
  • Layer Styles (Saving a file with custom pattern)
  • Layer Styles (Loading a file with custom pattern)
  • Layer Styles (Loading a file with a pattern that isn’t inside the file - not sure how to get this kind of file though…)
  • Layer Styles (Saving a file with custom gradient)
  • Layer Styles (Loading a file with custom gradient)
  • Palettes (Loading a file saved in 4.4.1 with a palette)
  • Palettes (Loading in 4.4 a file saved in 5.x with palette)
  • Palettes (Loading a file saved in 5.x with a palette)

G: Gamut masks

Tests
  • Gamut masks docker (Create new mask) - GRTT-3
  • Gamut masks docker (Edit selected mask) - GRTT-4
  • Gamut masks docker (Duplicate selected mask)
  • Gamut masks docker (Delete selected mask)
  • Gamut masks docker (Use Save button in the Gamut Masks docker after editing/creating/duplicating the mask)

H: Gradients

Known issues: see Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0 - #18 by TheTwo

Tests
  • Gradient chooser (Press Cancel after editing)
  • Gradient chooser (Edit the gradient)
  • Gradient chooser (Add a new gradient) - GRTT-3
  • Gradient chooser (Import gradient from gradient dialog) - GRTT-1
  • Gradient chooser (Delete gradient)
  • Foreground to back. (Foreground to background should be the exact opposite of background to foreground)
  • Gradient Map filter (Choosing Foreground to Transparent or Foreground to Background gradient should have an effect)
  • Gradient Map filter (Changing foreground or background color should make the gradient update)
  • Gradient Map filter (Foreground to background and foreground to transparent gradients should appear on the top of the list)
  • Gradients chooser (Remembering the last used gradient on closing Krita)

I: Layer styles

Known issues: Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0 - #22 by TheTwo

Tests
  • Layer styles menu (New) - GRTT-3
  • Layer styles menu (Import…) - GRTT-1
  • Layer styles menu (Collections/storages combobox)
  • Layer styles menu (Export…)

J: Palettes

Known issues: Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0 - #19 by Rebecca

Tests
  • Palette docker (Add a color)
  • Palette docker (Modify this spot)
  • Palette docker (Edit this palette)
  • Palette docker (Delete color)
  • Palette docker (Changing the palette)
  • Color Picker (Pick color from canvas into the palette)
  • Palette docker - palettes (Add a new palette - in resources)
  • Palette docker - palettes (Add a new palette - in a document)
  • Palette docker - palettes (Export current palette to file)
  • Palette docker - palettes (Import a new palette from file)
  • Palette docker - palettes (Remove current palette)
  • Palette docker (Edit palette to have less columns)
  • Color Sampler (Update view in Palette docker when the user uses color sampler to add swatches)
  • Palette docker (Color Sampler + Palette docker)
  • Palette docker (Create a new palette)
  • Saving
  • Color Sampler (Use “save to palette” on a custom palette, close and reopen Krita)

K: Patterns

Tests
  • Patterns docker (Import resource)
  • Patterns docker (Delete resource)
  • Filter docker
  • Patterns popup (Add to predefined patterns) - here check in both Patterns popup and Resource Manager afterwards if the pattern really exists
  • Patterns popup (Use as Pattern)

L: Resource Manager

Tests
  • Implementation (entry to open it)
  • Implementation (filter by storage)
  • Implementation (filter by type)
  • Implementation (filter by tag)
  • Implementation (Show deleted resources checkbox)
  • Implementation (filter box)
  • Implementation (brushes box)
  • Implementation (icon + info for the brush)
  • Implementation (tags selector)
  • Implementation (delete/undelete resource)
  • Implementation (import resource(s) or bundles/storages)
  • Implementation (open resources folder)
  • Gradients - nice thumbnails
  • Tag selector working as expected
  • List of resource types (List of resource types should be user-friendly, like “Brush Presets” instead of “paintoppresets”)
  • Create bundle (Create a bundle out of selected resources)
  • Storages listed
  • Resources List View updates (Select “All Untagged”, then add a tag to a resource)
  • Rename a resource (A text edit widget with a OK at the end)
  • Import of a resource (Importing a resource with the same name as existing one)
  • Import the preset file again (the same name), or create a new resource with this name)
  • Brush Presets (example) (- Import a preset | - Delete it)
  • Sorting
  • Tags widget [+] button

M: Resources

Tests
  • Resource choosers (Scrolling through pattern chooser or toolbar brush preset chooser or brush presets docker)
  • Resource management (Moving a resource into a subfolder or back - Krita should recognize it as removing the old resource and creating a new one; it’s an unsupported behavior but Krita shouldn’t break if someone does this…)
  • Resource choosers (Start of Krita)
  • Translations (Start of Krita in a new language - that can only work in some versions of Krita, I’m not sure if Krita Next now has translations… I think it can have, though)

N: Search

Tests
  • Brush Presets docker (Filter in tag checkbox - checked)
  • Brush Presets docker (Filter in tag checkbox - unchecked)
  • Brush Presets docker (Filter/search by name part working as expected)

O: SeExpr

Known issues: Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0 - #28 by TheTwo

Tests
  • Create a new script
  • Overwrite the old script
  • Rename a script
  • Import a script (.kse)

P: Sessions

Known issues: Help Krita improve with structured Beta Testing of the new resource system in Krita 5.0 - #41 by emilm

Tests
  • Sessions dialog (New)
  • Sessions dialog (Rename)
  • Sessions dialog (Switch to…)
  • Sessions dialog (Delete…)
  • Sessions dialog (Correct/not empty MD5 sum in the database)

Q: Tags

Tests
  • Tag dropdown (Add a new tag)
  • Tag dropdown (Rename a default tag)
  • Tag dropdown (Rename a custom tag)
  • Tag dropdown (Delete a default tag)
  • Tag dropdown (Delete a custom tag)
  • Tag dropdown (Undelete a default tag - note that you need to do it just after deleting it, in the same session)
  • Tag dropdown (Undelete a custom tag - note that you need to do it just after deleting it, in the same session)
  • Preset context menu (Assign an existing default tag)
  • Preset context menu (Assign a new tag)
  • Preset context menu (Deassign from another tag)
  • Preset context menu (Deassign from the current tag)
  • Preset context menu (Deassign from the current tag when it’s “All” or “All untagged” - should be impossible)
  • Tag selected at startup - should reflect the last selected tag when you closed Krita
  • Brush Presets docker (Hover cursor over preset to show tooltip)
  • Tags Translated (On a Polish system with English Krita, it should create English tags)
  • All (“All” tag works)
  • All untagged (“All untagged” tag works)
  • Tags (Deactivating bundle should remove associated tags)
  • Create a few new tags, some with presets, some without; then go to Resource Manager → Export Tags to Folder; then remove the resourcecache.sqlite file; then open Krita and see if those tags are still there.

R: Task sets

Tests
  • Tasks sets docker (Save task set)
  • Tasks sets docker - chooser (Import a task set)
  • Tasks sets docker - chooser (Delete a task set)

S: Workspaces

Tests
  • Workspaces chooser (the button on the toolbar) (correct MD5 sum in the database)
  • Workspaces chooser (If the bundle Krita 3 is switched off, the workspaces should still be available)
  • Workspaces chooser (Import) - GRTT-I
  • Workspaces chooser (Delete) - it should stop being available in both Workspace chooser and Window → Workspaces
  • Workspaces chooser (Save) - GRTT-III
  • Workspaces chooser (Overwrite a workspace) - GRTT-IV
  • Workspace chooser - switching to a workspace
  • Menu → Window → Workspaces - switching to a workspace
  • Menu → Window → Workspaces → Import - GRTT-I
  • Menu → Window → Workspaces → Create - GRTT-III

T: Others

Tests
  • Script Ten Brushes (Potential issue: The current preset is activated, not the one assigned to the button)
  • Brush Presets docker (Switching on/off different storages)
  • Startup (Start krita for a second time after adding manually (in the file browser on your system) new resources to the folder)

U: Resource folder & cache shenanigans

Tests
  • Make sure to backup your resource folder and your configuration files beforehand!!! The instruction is above.
  • Remove the resources folder completely, start Krita 5.x, check that everything is fine, close it and start again. It should still be fine and the second time should be faster.
  • Remove the resources folder completely, start Krita 4.x, close, start Krita 5.x, check that everything is fine and that you see MyPaint brushes, then close Krita and start it again, still everything should be fine and this start should be faster.
  • Make a new custom resource, change the location of the resource folder AND the cache to some non-standard and empty location (but don’t change the cache location), and make the two above tests again (without removing the folder). The new resource shouldn’t appear in those tests.
  • Now do something similar, but with cache still pointing to the old location. Note if there is anything wrong. Cache should always just show the reality of the resource folder.
  • Try to have two different resource folders with different sets of custom resources and juggle between them. See i there is anything wrong.
  • Correct behaviour: (1) resource folder created by Krita contains all the resources that come with Krita 5.x, so for example MyPaint brushes and WaterC brushes and Krita 3 and 4 bundles and SeExpr bundles; (2) the cache always shows the reality of the resource folder; it shouldn’t show resources that are not available, (3) cache database contains the most up-to-date tags, so if you change the cache location, you will lose them (unless you copied the database? or unless Krita copies the database? I’m not sure what the current behaviour is :smiley: ).

Generalized resource type tests process (GRTT tests)

I. Import Resource File:

  1. Import a new resource file
  2. Import the same resource file again
  3. Import a different resource file with the same filename
  4. Import an incorrect resource file

II. Rename resource:

  1. Rename to something
  2. Rename to a name of an existing resource

III. Add a new resource

  1. Add a new resource with unique name
  2. Add a new resource with a filename that already exists: in case of brush presets, just create “Test Brush 2” and then try to create “Test Brush 2” again.
    • Choose “Cancel”
    • Choose “Overwrite”
  3. Add a new resource with a name that already exists: in case of brush presets, create a preset called “Test Brush 3A”, then rename it to “Test Brush 3B”, and then try to create a new brush called “Test Brush 3B”
    • Choose “Cancel”
    • Choose “Yes”

IV. Overwrite a resource

  1. Simply make changes and overwrite a resource - make sure that:
    • the resource selected is the one you overwrote
    • correct values are in GUI and the resource works correctly
    • that if you further make changes, the dirty indicator (if relevant) appears
    • reloading the resource works
  2. Make changes, change the name and overwrite a resource with a new name (if it’s possible)
13 Likes
2

Hi there, count me in. I can do 3:
Brush Editor, Tags and Task Sets.
Tomorrow morning I’ll install the latest nightly build and do the tests right after that. Thank you for including info on backing up files/folders before installing the nightly build. Much appreciated.

2 Likes
3

I can do gamut masks and palettes. I’ve already been using palettes with the beta, but I will give it a more thorough look. :smiley:

2 Likes
4

Thank you very much! That will be really helpful :heart_eyes_cat:

1 Like
5

Great, thank you very much! :heavy_heart_exclamation:

6

Brush Editor Test Results
Installed nightly build - Windows - 5.1.0-prealpha (git b058b37)
4 tests completed and please see note at the end.

Test 1)
Edit brush preset icon via .kpp file in paintoppresets folder
Navigated to paintoppresets folder by selecting Settings, Manage Resources, Open Resource Folder.
Located j)_WaterC_Basic_Lines_Wet and opened with doubleclick.
Added magenta strokes to brush icon.
Saved via Ctrl+S - all setting in save dialog left as is.
Used original filename.
New icon appeared immediately in Brush Presets docker. :white_check_mark:
Quit and restarted Krita.
Opened a .kra file, the active brush preset was b) Basic 5 Size (I didn’t call up that preset - that’s the one that automatically was selected by Krita).
Changed preset to the edited brush (j WaterC Basic Lines Wet). Icon edits were present. Brush functioned as expected. :white_check_mark:

Test 2)
Edit brush preset icon via Brush Editor
F5 to open Brush Editor
Expanded Brush Editer window to reveal presets selector.
Clicked on i) Wet Bristles Rough
Clicked on brush icon underneath scratchpad to reveal brush preset icon.
Added brush strokes to icon.
Clicked Overwrite Brush Preset.
Dialog box opened, selected Load Scratchpad Thumbnail.
Save.
Closed Brush Editor.
Edited icon observed in Brush Presets Docker. :white_check_mark:
Quit and restarted Krita.
Basic 5 Size brush was active.
Changed to edited brush to see if icon changes held (wet bristles rough). The icon is the edited one I created. :white_check_mark:

Test 3)
Edit brush preset name.
F5 to enter Brush Editor.
Expanded to reveal presets selector.
Selected a) Eraser Circle.
Clicked “rename the brush preset” and changed name to a) Eraser Big Circle.
Save.
Viewed icon in popup palette - it now has the new name I gave it. :white_check_mark:
Opened Brush Presets Docker and searched the word “erase” to look for duplicates. None found. The name was changed and only one instance exists. :white_check_mark:
Quit and restarted Krita.
Changed preset from Basic 5 Size to the renamed eraser. :white_check_mark:
The newly-named brush preset appears correctly with its new name and works as expected. :white_check_mark:

Test 4)
Create New Brush Preset
F5 - Open Brush Editor.
Expanded Brush Editor to reveal all presets.
Selected Wet Bristles Rough* (see note below).
Changed brush tip to Chalk Sparse.
Clicked Save New Brush Preset.
Brush name displayed as i) Wet Bristles Rough Copy.
Changed it to i) Wet Bristles Rough Chalk.
Clicked Load from Icon Library.
Selected new icon.
OK.
Painted a stroke in the icon box.
Save.
Closed Brush Editor.
Located new brush in Brush Presets Docker by searching on the word “chalk” - it showed up as expected. :white_check_mark:
Painted with the new brush.
Changed size from 20 to 281. Worked as expected. :white_check_mark:
Opened new brush in Brush Editor.
Changed saturation settings.
Closed Brush Editor - painted with new settings. Worked as expected. :white_check_mark:
Reopened Brush Editor, changed back to original settings via the “reload the brush preset” icon.
Reverted to original settings as expected. :white_check_mark:
Quit and restarted Krita.
Found new brush by searching the word “chalk” in Brush Presets Docker.
Selected and painted - worked as expected. :white_check_mark:
Verified existence new .kpp file in paintoppresets by choosing Settings, Manage Resources, Open Resource Folder and then open paintoppresets. :white_check_mark:

*NOTE: In my first test I edited a brush preset icon by accessing the .kpp file in the paintoppresets folder. Although all my usual brushes were fully available to me in this nightly build, I notice only about 1/3 show up in this folder. I checked with my backup folder I made before installing the nightly build (my backup is 5.0 beta 1) and it is the same - only about 1/3 of the brush presets show in that backup folder. In test 4 I wanted to see if both .kpp files existed – the original brush preset and the new one I just created off of that one. Only my new one is in that folder. I don’t where the .kpp file resides for the brush I selected as the basis for my new brush. There’s lots I don’t know about the backend so maybe this is nothing but I thought I’d mention this in case it’s relevant. :snowflake: (Tiar: the brush presets are inside a Krita 4 resources bundle).
End of Brush Editor test.

2 Likes
7

@sooz I think you’ll find that Wet Bristles Rough is stored in the Krita_4_Default_Resources bundle. Many other brush presets are in there with it.
If you’re keen and interested, you can open up the bundle files with a .zip utility and have a look around inside them. Just take a copy and rename it as .zip instead of .bundle and then right-click Extract it.

1 Like
8

Thank you so much. I’m very curious. Now I know where to look.

1 Like
9

It is possible to see all brush presets in the ressource manager, go to “Managing Resources”, select Brush preset and the bundle. No need to unzip a bundle.

2 Likes
10

Thank you, @anon71590212

11

When you test tags, you can also tag multiple presets at once via manage resource, or delete tags as well. It’s really very helpful. Just select multiple brush presets and click + on tags. You will also see more additional info when you select a resource in this manager.

1 Like
12

I see what you mean, @anon71590212. That’s an awesome feature.

13

New special badge for participants

So thanks to @Dreatern 's suggestion I made a special badge for everyone who is participating in this initiative or more general beta testing of Krita 5.

How to get it: either participate in this beta testing of the resource system, or contribute to beta testing and improvement in some other way (for example make a bug report that was accepted by a developer, or report issues with Krita 5 on a thread etc.). It’s assigned manually by admins. Please do remember that the goal of it all is to improve Krita, not to get a badge :stuck_out_tongue: but if you did help already, you can nudge the admins to get it.

What can you do with it: you can click on your profile, then go to Badges, then find this badge, click on it, and then there will be a button or something “Use it as a user title”. Then a text “Krita 5 Beta Tester” will appear next to your nickname in every post.

So here I say officially that I give the first badge to @sooz for her help! :microscope:

(I won’t be announcing other users like that but I wanted to make this more special when it’s first time).

4 Likes
14

Too cool! Thanks

15

Tags Tests
Everything worked as expected - except see note on alpha order of tags.

Installed nightly build - Windows 10 - 5.1.0-prealpha (git b058b37)

Test 1: Tag dropdown (Add a new tag)
From Brush Presets Docker, click on dropdown menu, type name of new tag in blue-bounded box, click + sign.
New tag is added. :white_check_mark:
Verified by clicking dropdown menu in Brush Presets Docker and Presets section of Brush Editor.:white_check_mark:

Test 2: Tag dropdown (Rename a default tag)
Selected default “My Favorites” from Brush Presets Docker.
Clicked Tag dropdown menu, selected Rename Tag.
Typed new tag, clicked + sign. :white_check_mark:
Renamed tag now exists at bottom of the list of tags (not in alpha order). :ballot_box_with_check:
*NOTE: After restart, new tags are in 2 alpha orders - 1st all tags beginning with capital letter, 2nd alpha order is tags beginning with lower case letter. :ballot_box_with_check:

Test 3: Tag dropdown (Rename a custom tag)
Selected a custom tag from Brush Presets Docker.
Clicked dropdown menu, clicked on Rename Tag.
Typed new tag name, clicked on + sign. :white_check_mark:
Renamed custom tag now exists in tag list, 4th from the bottom (not in alpha order) :ballot_box_with_check:
*NOTE: After restart, new tags are in 2 alpha orders - 1st all tags beginning with capital letter, 2nd alpha order is tags beginning with lower case letter. :ballot_box_with_check:

Test 4: Tag dropdown (Delete a default tag)
In Brush Presets Docker, selected Sketch tag.
Clicked Tag dropdown menu, clicked on Delete this Tag.
Sketch tag was deleted from tag list. :white_check_mark:

Test 5: Tag dropdown (Delete a custom tag)
Selected a custom tag from tag list, clicked Tag dropdown menu and clicked Delete This Tag.
Tag was deleted from list. :white_check_mark:

Test 6: Tag dropdown (Undelete a default tag)
Undelete Sketch tag (default tag that was deleted) was available as an option in the Tag dropdown menu regardless of tag filter (All, All Untagged or various individual tags selected). :white_check_mark:
Clicked on Undelete Sketch.
Sketch tag was returned to tag list - inserted in alpha order. :white_check_mark:

Test 7: Tag dropdown (Undelete a custom tag)
Undelete My Favos (the name of the custom tag I deleted) was available while the Brush Presets tag list was set to All, All Untagged and when any tag name was selected to filter the presets list.
Clicked Undelete My Favos and the tag was returned to the list - inserted in alpha order. :white_check_mark:

Test 8: Preset context menu (Assign an existing default tag)
From Manage Resources, selected c)Pencil_1_Sketch(mypaint) which had no tags assigned.
Clicked + and clicked on Sketch from tags popup list. :white_check_mark:

Test 9: Preset context menu (Assign a new tag)
From Manage Resources, selected c)Pencil_1_Sketch(mypaint).
Clicked + and typed new tag name in New Tag box at bottom of popup list. Clicked + to add the tag.
Tag was added to the resource. :white_check_mark:

Test 10: Preset context menu (Deassign from another tag)
From Manage Resources, selected a)_Eraser_Circle.
Clicked on x next to Digital tag. Tag was deleted from resource. :white_check_mark:

Test 11: Preset context menu (Deassign from the current tag)
From Brush Presets Docker, filtered to Impression.
Right-clicked on v) Texture Impressionism-Accurate, left-clicked on Remove From This Tag.
Resource was removed from tag Impression. :white_check_mark:

Test 12: Preset context menu (Deassign from the current tag when it’s “All” or “All untagged” - should be impossible)
In Brush Presets Docker, tags set to All.
Remove From Other Tag is available on right click and presents a list of tag(s) from which resource can be removed. :white_check_mark:
Remove From This Tag is not available. :white_check_mark:

Test 13: In Brush Presets Docker, tags set to All Untagged.
Remove From Other Tag does not appear on right click. :white_check_mark:
Remove From This Tag does not appear on right click. :white_check_mark:

Test 14: Tag selected at startup - should reflect the last selected tag when you closed Krita
Yes. Selected Muses in Brush Presets Docker and popup pallete, then quit Krita.
Restarted Krita.
Muses is the selected tag in Brush Presets Docker and popup palette. :white_check_mark:

Test 15: Brush Presets docker (Hover cursor over preset to show tooltip)
Hovered cursor over 10 different presets in Brush Presets Docker. Tooltip showed in each one. :white_check_mark:

Test 16: Tags Translated (On a Polish system with English Krita, it should create English tags)
Not tested.

Test 17: All (“All” tag works)
All tag works in Brush Preset Docker, Brush Editor and Manage Resources. :white_check_mark:

Test 18: All untagged (“All untagged” tag works)
All Untagged tag works in Brush Preset Docker, Brush Editor and Manage Resources. :white_check_mark:

Test 19: Tags (Deactivating bundle should remove associated tags)
From Manage Resources Libraries, selected Muses, clicked Deactivate. Close.
Muses tag is deleted from tags list. :white_check_mark:

Test 20: Reactivated Muses from Manage Resources Libraries and the tag and resources returned (phew!) :white_check_mark:

3 Likes
16

Task Sets Testing

Test 1: Tasks sets docker (Save task set)
From Task Sets Docker, clicked record button.
Recorded 4 tasks.
Recorded Tasks saved and Task Sets Docker cleared by clicking trashcan icon. :white_check_mark:

Test 2: Tasks sets docker - chooser (Import a task set)
Click on the folder icon on Task Sets Docker, all saved task sets appear.

task set
task set511×262 11.9 KB

There is a little problem here. The highlight bar is solid - can’t read the name of the task set when the highlight is on it. In the screen cap above, there are 2 task sets but you can only see the one name “2nd”. The one above it is hidden. But it does function as expected other than the opacity of the highlight. :ballot_box_with_check: (should be fixed now: 7b7ec23a048b)

Test 3: Delete a Task Set
Works as expected except for opacity of highlight as noted above. :white_check_mark:
Click on folder at bottom of Task Set Docker.
Highlight task set to be deleted, click on trashcan.
Task is deleted. :white_check_mark:

1 Like
17

I reported it before Bug 441639

what is this？

2 Likes
18

I tested gradients with 5.0 beta

  1. Press Cancel after editing: normal :white_check_mark:
  2. Edit the gradient–
    If I click “Yes”, a file xx.0001 will appear in the resource folder. Is this redundant? :snowflake:
    If the editor is “stop gradients”, the gradient inside the small icon will not be updated in real time. It needs to be switched to another gradient and converted back. But when you create a new gradient, it will be updated in real time. :ballot_box_with_check:
    image

If you edit “segmented gradients”, you will have the same problem as above, in addition, the preview image in Gradient chooser is not correct. :ballot_box_with_check:
image

If you change the name of the gradient while editing, it creates a copy and then both gradients change to the new name together :red_square:
image

  1. Add a new gradient–
    The preview image of “segmented gradients” is not normal :red_square:
    If the new gradient is of the same type as the existing gradient and has the same name, you will be asked whether to overwrite it: the Chinese name will be overwritten, but the name will be garbled; :red_square: the English name and numbers will be normal. :white_check_mark:
    image

When overriding “segmented gradients”, it is always invalid :red_square:
If you delete a gradient and create a new gradient with the same name, you will be prompted whether to overwrite it, but no new gradient will be created after you click “Yes”. :red_square:

4.Import gradient from gradient dialog–
Import gradient from gradient dialog–when importing gradient with Chinese name, it becomes garbled. :red_square:
The thumbnails of the foreground and background colors show the colors at the time of export. :red_square:
image

  1. After deleting the gradient, the contents of the resource folder do not disappear, and it prompts to overwrite when creating a new gradient with the same name. Then the problem mentioned in 3 will arise. After deleting directly from the resource folder, there is no such problem. (:snowflake: :question:)
  2. Foreground to back: normal :white_check_mark:

7, 8. These two gradients do work, but when I click “Confirm” and open the filter again, they have changed to custom colors. I need to change the color scale to foreground/background again :snowflake:

image
image438×94 2.57 KB

image
image436×47 1.3 KB

  1. Normal :white_check_mark:
  2. It doesn’t, it automatically changes to the first one

Other s–
I noticed that there are also “Compact Gradient Editors” and “Generic Gradient Editor”
The “Compact Gradient Editors” in “Multigrid” do not recognize the foreground and background colors. :red_square: :snowflake:

image
image425×73 2.24 KB

The “segmented gradients” created and edited in “Generic Gradient Editor” can display thumbnails normally :white_check_mark: . Creating gradients with a file of the same name will not do anything. :red_square:
When you open the “Generic Gradient Editor”, the gradients you meet cannot be overwritten. You have to switch to another gradient and then you can overwrite it. :red_square:
image

(I also encountered a problem when creating “stop gradients”, but I couldn’t reproduce it later. I only remember that it had about 15 gradients, with foreground and background colors, several of the same color, and then when I clicked “Sort stops by hue” several times, the transparency of the last gradient changed :warning:)

Question.
Should some functions of “Generic Gradient Editor” be added to the Gradient chooser? For example, “Convert gradient button”. :question:
When using the “Gradient Map filter”, the foreground/background color above becomes gray. This is not very intuitive, need to change it in some places? :question: :snowflake:
image

4 Likes
19

PALETTES

Tested with the nightly 1c72b2c.

Given tests:

  • Palette docker (Add a color) :white_check_mark:
  • Palette docker (Modify this spot) :white_check_mark:
  • Palette docker (Edit this palette) :white_check_mark:
  • Palette docker (Delete color) :white_check_mark:
  • Palette docker (Changing the palette) :white_check_mark:
  • Color Picker (Pick color from canvas into the palette) :question:
    • Not sure what’s meant with this — when I ctrl+click a colour from the canvas, the colour in the palette that’s closest to that colour gets highlighted. But this doesn’t add a new colour to the palette.
  • Palette docker - palettes (Add a new palette - in resources) :white_check_mark:
  • Palette docker - palettes (Add a new palette - in a document) :white_check_mark:
  • Palette docker - palettes (Export current palette to file) :white_check_mark:
  • Palette docker - palettes (Import a new palette from file) :white_check_mark:
  • Palette docker - palettes (Remove current palette) :white_check_mark:
  • Palette docker (Edit palette to have less columns) :warning: Weirdness when colors present
    • Create a new palette, which has 16 colums by default
    • Add 8 colors to the first row
    • Reduce the column count to be less than 8, for example 6
    • The last two colours that don’t fit in the row are all the way at the bottom of the palette. I’d expect the two colours to be in row 2.
    • Bring column count back up to 16
    • The last two colours are still all the way at the bottom. I’d expect everything to be back as it was before resizing.
      image
      image1958×987 88.4 KB
  • Color Sampler (Update view in Palette docker when the user uses color sampler to add swatches) :red_square: Palette docker doesn’t update
    • If the docker and the palette is visible while you sample colours, the palette doesn’t update. (Or sometimes updates, but incomplete or “a step behind”)
    • Switching to another palette and back then shows the correct palette with all the colours added with the sampler
  • Palette docker (Color Sampler + Palette docker) :question:
    • Not sure how this is different from the test above
  • Palette docker (Create a new palette) :white_check_mark:
  • Saving :white_check_mark:
  • Color Sampler (Use “save to palette” on a custom palette, close and reopen Krita) :white_check_mark:

Additional tests:

  • Palette docker - assign tag to palette :white_check_mark:
  • Palette docker - filter by tag :white_check_mark:
  • Palette docker - edit this palette - add group :red_square: Krita hangs
    • Click on “Edit this palette”
    • Click “Add Group” and confirm with “OK”
    • Click “Add Group” again and confirm with “OK”
    • Confirm the edit palette dialog with OK
    • Krita hangs in an endless busy loop, printing “updating the palette model inside the palette editor object” in the console
  • Palette docker - select a palette :red_square: Can’t select first palette
    • Open an image with the palette docker open, initially there should be no palette selected
    • Try to select the first palette in the palette dropdown — can’t be selected because it’s already highlighted and clicking on it is a no-op.
    • Clicking on a different palette and then on the first one works

Gamut masks to follow tomorrow. :smiley:

4 Likes
20

If you use the Color Picker tool, in Tool Options there is an option “Add color to the palette”, that’s what this test it about :slight_smile:

This is also about the same thing. There is actually some known bug there but fixing it is not trivial…

Going down, I’ve noticed that all tests you were confused about were about that feature, so, yeah.

Damn I KNEW there was an infinite loop there :smiley: I think I can guess which code is it. Not sure how to make it not buggy though.

Thank you for testing!

1 Like