Object connections and unfolding

VectorPaint three scissors poses: relate blades and handles around one pivot

Construct opening states from two separate components, checking a shared pivot, handle/blade ownership and outlines without assuming a hidden rotation-centre command.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Open scissors do not consist of four independently floating handles and blades. Each component extends from one handle through the pivot toward its blade tip on the other side. Make open, narrower and closed schematic states, checking component ownership and a shared axis without simulating cutting, material strength or real-tool safety.

Name the two components separately

Create a 1200 by 900 pixel canvas with pivot (600,450). Component A runs from the lower-left handle through the pivot to the upper-right tip; B runs from the upper-left handle to the lower-right tip. Draw two pale centre references and label ownership before making four decorative shapes. Tip references may be (900,300) and (900,600), giving displacements of 300 horizontally and minus/plus 150 vertically. These coordinates support this drawing comparison, not real scissors manufacture.

Build continuous handle-to-blade components

Build A first, tapering the right-side blade to its tip and connecting the left side to the handle loop through an arm. Offset the loop beside the centre reference instead of forcing every feature onto one straight line, so both loops can remain distinguishable when closed. Build B with corresponding structural roles. A background-coloured loop opening is only a visual representation, not a transparent hole, and needs rechecking on a changed background; actual cut-outs also require output inspection. Identify each handle and blade as one component when selecting, without swapping A’s handle into B merely because their paths cross at the pivot.

Use the pivot circle only as a shared connection

Add a small pivot circle centred at (600,450), without using an oversized disc to conceal disconnected blade sections. Hide it first to verify that both component outlines actually pass through the shared location, then restore it. You may draw A above B, but use the same stacking convention in all three states. The circle does not bind motion constraints, and grouping does not create a mechanical hinge. Preserve a pale A/B checking version so ownership remains traceable after applying a unified final colour.

Reduce the opening against equal-radius references

Duplicate the first state without moving the pivot. New tip references can be (930,390) and (930,510), with displacement (330, minus/plus 60). Because 300 squared plus 150 squared equals 330 squared plus 60 squared, both states have the same pivot-to-tip distance. Retain a pivot-centred reference circle and check tips and handle arms along the new radial directions. If available rotation controls cannot ensure this axis, reconstruct an explicitly approximate illustration against the references rather than claiming rigid-rotation precision. Do not assume a hidden arbitrary-pivot command.

Retain both component identities in the closed view

For the third state, bring both tip directions near one horizontal ray and retain the same pivot-centred radius instead of shortening blades to appear closed. Blade edges may approach or overlap under the stated layering convention, while each handle loop remains traceable to its own component. If the schematic outline cannot preserve two readable loops when closed, adjust loop offsets in the first state and update all states rather than moving a handle arbitrarily only in the third. This depicts appearance, not acceptable physical cutting contact, clearance or edge angles.

Align pivots before comparing openings

Place all three states in equal presentation areas, aligning their pivots rather than substituting bounding-box centres. Extending handles change bounds, so centring solely on them can displace pivots and suggest a jumping whole tool. Label the states open, narrower and schematic closed. Optional arrows indicate this diagram’s state change, not an app-generated animation. Even without labels, blade angles should show a decreasing opening. If only handles move while tips remain fixed, check whether blade objects were omitted from the edit.

Inspect both component-coloured and monochrome views

In the A/B-coloured view, trace A from handle through arm to tip, then trace B without switching identity at the pivot. Duplicate a monochrome view, preserving readable opening through outlines and minimal divisions. Save the editable source and export a PNG, inspecting merged blade strokes, blocked loop openings and a pivot circle displaced from the crossing at actual viewing size. Actively hide or remove manually drawn reference circles for final output; calling them references does not stop their export. Verify grid/native-guide output from actual results.

Troubleshoot pivot, length and ownership in order

If blades seem to telescope, check pivot-to-tip distances first. For a translated whole tool, inspect pivot positions. For disconnected handle/blade movements, inspect component grouping. For white-block loop openings, inspect background and opening construction rather than thickening every outline. Record which points were coordinate-checked and which were approximately reconstructed; artistic inspection is not physical simulation. Retain all states, the component-coloured check and actual output so readers can trace each part through the shared pivot without appearing or disappearing blade components.

Related tutorials and sources

VectorPaint articulated desk lamps: connect arms through pivots to the shade, VectorPaint hinged boxes in three poses: keep the hinge fixed as the lid changes direction.

Sources checked on November 8, 2026: VectorPaint public version 1.0.8, requiring iOS / iPadOS 17.0 or later. Capability scope follows the official App Store description and Apple public version lookup. This original exercise can be performed independently; use the controls in your installed version. It does not claim completed physical-device, private-file or all-export-environment testing. Manual checks and external records are not newly promised automatic analysis features.