so, we made this category and hope to fill it up with relatively short articles explaining color-related concepts in a light-hearted and visual manner. We recommend going over the color managed workflow page next - even if you don’t plan on using it, it will help make sense out of the many features related to colors and Color Management. Other than that, each article should stand on its own and can be all the rays come together is called the focal point, and the vanishing point in a 2d drawing is related to it as it’s the expression of the maximum distortion that can be given to two parallel lines as

so, we made this category and hope to fill it up with relatively short articles explaining color-related concepts in a light-hearted and visual manner. We recommend going over the color managed workflow page next - even if you don’t plan on using it, it will help make sense out of the many features related to colors and Color Management. Other than that, each article should stand on its own and can be all the rays come together is called the focal point, and the vanishing point in a 2d drawing is related to it as it’s the expression of the maximum distortion that can be given to two parallel lines as

all the rays come together is called the focal point, and the vanishing point in a 2d drawing is related to it as it’s the expression of the maximum distortion that can be given to two parallel lines as stroke. Stroke This input goes slowly from 0.0 to 1.0 while the stroke is being applied. This is related to "stroke duration" and "stroke holdtime" settings. Direction This input defines the angle of is -90. This is the same as tilt-direction in Krita. Custom This is a user-defined input. It is related to the "customized input" setting. Parameters Has the following parameters: Basic Color Speed

definitions (i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Krita’s shared pointers, then Qt’s, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, it’s only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesn’t work with wildcard imports (from

definitions (i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Krita’s shared pointers, then Qt’s, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, it’s only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesn’t work with wildcard imports (from

(i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Krita’s shared pointers, then Qt’s, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, it’s only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesn’t work with wildcard imports (from

definitions (i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Kritaʼs shared pointers, then Qtʼs, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, itʼs only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesnʼt work with wildcard imports (from

definitions (i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Krita’s shared pointers, then Qt’s, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, it’s only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesn’t work with wildcard imports (from

definitions (i.e. using) nullptr Deleted, default, override, final unique_ptr/QScopedPointer Performance-related (rvalues) Move Constructors Reference Qualifiers (rvalue references) C++11 features mostly for rule is: first Krita’s shared pointers, then Qt’s, do not use the std smart pointers. Performance-related (rvalues) Using move constructors and rvalues are very subtle and advanced features, but widely plugins etc. become no-ops. Thus, it’s only possible to test code units that are independent of Krita-related functions. Another caveat is that the mock krita module doesn’t work with wildcard imports (from