on a vector layer in Krita you are actually drawing paths passing through points that are called nodes, which are located on specific coordinates on the ‘x’ and ‘y’ axes. When you re-size or move these with the Select Shapes tool, and in the tool options you can specify the exact coordinates. Editing nodes and special parameters If you have a shape selected, you can double-click it to get to the appropriate In the Edit Shape tool, you can move around nodes on the canvas for regular paths. For special paths, like the ellipse and the rectangle, you can move nodes and edit the specific parameters in the Tool

with the Select Shapes tool, and in the tool options you can specify the exact coordinates. Editing nodes and special parameters If you have a shape selected, you can double-click it to get to the appropriate In the Edit Shape tool, you can move around nodes on the canvas for regular paths. For special paths, like the ellipse and the rectangle, you can move nodes and edit the specific parameters in the Tool (Vector Only) This allows you to snap to a horizontal or vertical line from existing vector objects’ nodes (Unless dealing with resizing the height or width only, in which case you can drag the cursor over

(ベクターのみ) This allows you to snap to a horizontal or vertical line from existing vector objects' nodes (Unless dealing with resizing the height or width only, in which case you can drag the cursor over two parallel rulers, one vertical and the other horizontal. To snap them perfectly, drag one of the nodes after you have made the ruler, and press the Shift key to snap it horizontal or vertical. In 3.0, selected, and draw a line over the canvas, you will be able to see the nodes, and the stops in the gradient. Move around the nodes to move the gradient itself. Select the stops to change their color in

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()’es are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()’es are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()’es are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()ʼes are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()’es are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It

common phases: 1. Lock the image 2. Do the processing of nodes 3. Unlock the image 4. Emit setDirty() calls and update the projection of the nodes 5. Wait until all the setDirty()’es are finished 6. Emit cannot fit all these requirements, because it has important design limitations: first, walking through nodes is implemented inside the visitor itself and, second, emitting signals is put into visitors as well can be applied to nodes concurrently in multithreaded way. applies a usual qt-command to the image. Sequentiality properties may vary as well. emits setDirty() calls for all the nodes which need it. It