A Drop Shadow, glow, blur, Feather or pixel filter listed before a fill's
or stroke's own Transform effect that makes copies is now drawn by each
copy from that copy's fill area or stroke outline, with its sizes scaled
by the copy's mean scale and a Drop Shadow's offset turned, reflected and
scaled with the copy. With Transform Patterns or Scale Strokes & Effects
on, the shadow is no longer scaled a second time. A raster effect listed
after the Transform effect paints once around all the copies, and with
either option on it stays on each copy as before.
Each copy of a path's own Transform effect that makes copies now carries
the raster effects of its fills and strokes the same way, for a single
fill, a single stroke, or several.
Before, one shadow was drawn around all the copies at the fill's or
stroke's own distances. The canvas, the object's bounds, export and
Expand Appearance draw the same copies, and copies that stop at the
effect budget each keep their effects. A fill or stroke whose effects
list raster effects before a Transform effect that makes copies and
another raster effect after it and before a later Transform effect that
makes copies or moves at random (for example Drop Shadow, Transform,
Drop Shadow, Transform) still paints its raster effects around all of
the copies.
The line that a round Eraser, the Knife, the Path Eraser, the Pencil with
Live preview off or a smoothing drag shows was one path of every point,
copied, flattened and tessellated again each frame, and with the
Eraser's Size following the pen each step was a new path each frame.
- A drag of more than 64 segments now shows in pieces of 64 segments,
each also holding the next piece's first segment so wide lines join
as one. Pieces the drag has passed come back as the same shared path,
and the canvas reuses their triangles while the view stays the same;
only the last piece is built again, and only when it changed.
- With Size following the pen, each step is kept as its own shared path
and only a new or moved step is built.
- The Knife's pieces carry where the dash pattern starts, so the dashes
run on across pieces (Overlay::SharedPath gains `dash`).
- The smoothing band is shared until it changes.
The canvas still copies the kept triangles into each frame. Release
commands (path.eraseRegion, path.knife, path.eraseSegments,
path.freehand) are unchanged.
Under a colored lightColor or a lights list, Revolve drew each face of a
solid-color or gradient surface on its own, so where two faces'
antialiased edges met, pixels inside the surface let the background
through at 1:1.
- The faces now lie over an underlay of themselves under one clip to
their outline, as colored Inflate's facets do (lighting::sealed, split
into lighting::underlay and sealed). The surface's opacity and blending
mode apply once, to the sealed surface.
- In a group, each run of one member's faces in the shared depth order
takes its own underlay; a translucent member's run keeps its opacity,
blending mode and mask on the sealed run.
- A face with a part of a mapped graphic gives its face to the underlay
and keeps the part right after it.
- Faces in a gradient with transparent stops carry its opacity mask and
are drawn as before. Revolve (Classic) is unchanged.
- The paint-copy budget counts the underlay in validation and drawing.
Docs: docs/three-d.md (Seams), docs/target-app-parity.md.
A PSD export now writes image resource 1050 in version 6 of the PSD file
format specification's slices resource format, the form that Import
Slices reads (crates/engine/src/cmd/fileio/psdslices.rs, version_6).
Flat and layered exports both carry it.
- The user and object slices that reach into the exported artboard are
written, clipped to it in its pixels, at least one pixel each way.
Auto slices are left out; opening the file lays them out again.
- An object slice is written as a user slice over its object's bounds,
and an HTML Text slice as No Image with its type's text as HTML. Name,
type, link, target, message, alternative text, cell text and
background color are kept; text alignment is written as the default.
- Slice IDs count from 1.
- More than 10000 slices or a text longer than 65536 characters is an
export error, matching the reader's limits. A slice without finite
bounds, or slices that would make the resource longer than 4 GB, is
also an export error; the size is checked before each text is added.
The Seam Fills group's clipping path was the image's box. A group with a
clip is measured by its clipping path, so on a trace with transparent or
ignored margins the expanded trace measured as the whole image, and
selection, alignment and resizing used that box. The clipping path is now
the image's box cut to the box of the traced paths: on a turned image it
has up to eight corners, and the anchor limit counts eight for it.
docs/mcp.md, the params text and the progress line describe the clip.
Danish is in COMPLETE_MESSAGES, but the untranslated report listed 2,066
status and error messages with no Danish row, and they showed in English.
- da.tsv gains 1,985 @msg rows in one block under a comment. Placeholders,
doubled braces, backticked names, command ids, double-quoted values and
bare true, false and null stay as the English writes them.
- Rows that other open pull requests add to da.tsv, and the 38 messages no
catalog has a row for yet, are left out. So are the three messages that
open #7353 rewrites so that a catalog row can match them.
- A test checks a sample of the new rows with their values filled in.
- docs/localization-parity.md and docs/target-app-parity.md give the new
counts: the report lists 81 Danish messages.
A row made with New Row holds no current colors until colors are merged
into it. OK already left its new color out of a rewritten color group;
now the other places that gather the dialog's colors leave it out too:
- Save All Colors, and its enabled state in the New Color Group menu
- OK on colors opened alone, which saves a new color group
- the Edit tab's wheel, color bars and chips, the harmony rules and
linked wheel moves
- the Color Theme Picker, which asks for and hands out colors only for
the rows that hold current colors
The Edit tab's color sliders edit the base color's row when the
selected row is one the tab does not show (empty or excluded).
Whether a trace's seam fills are strokes or outlines now depends on the
image object's own transform. A raster decoded scaled down to fit has its
two sides rounded separately, so it was scaled a little differently across
and down and every such trace got outlines. The stroke width now uses the
smaller scale of the raster, so a stroke still covers at most 0.75 pixels
on each side of its edge. The check for an even scale compares the axes'
lengths and angle directly, without a square root of a small difference.
Outlining the seam strokes now stops when the trace is canceled, checking
every 64 strokes. A stroke that reaches the make step without an outline
on a stretched image is left out rather than outlined outside the anchor
limit.
docs/mcp.md: the group clips the strokes or outlines.
import_fuzz builds PSD files from scratch whose image resource 1050
holds slices in version 6 (a version 16 descriptor after the first
record) and in the version 16 descriptors of versions 7 and 8. Each
sample has one user slice, one slice that follows a layer and one
generated automatically; the first two come in as user slices.
- the_sliced_psd_samples_bring_in_their_user_slices: each sample opens
with its two user slices and no warning, document.psdInfo counts 2,
and an embedded place brings 2.
- sliced_psd_samples_with_huge_counts_or_cut_short_come_in_without_their_slices:
slice counts of 10,001, 0x7fffffff and u32::MAX, data one byte
short, and data cut inside the count bring the art in without its
slices and with a warning.
- mutated_psd_slices_never_panic: mutated slice data, kept whole, cut
short with the resource length rebuilt, or with the file cut in the
resource block, never makes document.open, document.psdInfo or an
embedded file.place report an internal error.
tests_psdslices::damaged_slices_never_panic now fails when a command
reports an internal error instead of discarding the results.
Object › Plug-ins › Path Precision Tools › Common Tangents…
(`addon.pathtools.commonTangents`) adds the common tangent lines of two
selected convex closed paths as separate open paths: external (both
paths on the same side of the line), internal (the lines between them)
or all, and with Centerline the line joining the two centers. An
ellipse drawn with the Ellipse tool is measured as an exact ellipse at
any rotation and scale; any other path must be closed, have one outline
and bend the same way all around, with at most 10000 segments.
Each line runs between the points where it touches the two paths, or
covers a straight side that lies along it. Separate paths have four
tangents, overlapping paths only external ones (two for ellipses), and
a path inside the other none. Paths that touch, from outside or from inside, share
one tangent instead: a line centered on the point where they touch and
as long as the narrower path is wide along it. When there is no tangent
of the kind asked for, nothing changes and the result carries a warning
that says why. The lines take the current stroke and no fill, go
directly above the upper path and are selected, as one undo step. The
dialog has Preview.
The geometry is in vectorcraft-pathops: the tangents are the zeros of
the difference of the two outlines' support values over the normal's
angle, sampled at 720 even steps and at every angle where either
path's touching point passes to another segment, then refined, so the
work per pair is bounded.
Catalog rows for the menu item, the dialog and the messages are in
every catalog.
Docs: docs/mcp.md (Path Precision Tools add-on), docs/target-app-parity.md
and ROADMAP.
A type layer records neither the language nor the composer, so point type
whose runs name another language, or whose paragraphs use a Standard
composer, is written as pixels. New type's default paragraph settings
(the every-line composer, Burasagari and Mojikumi) no longer keep it from
becoming a type layer; Mojikumi other than the default still does in type
with Chinese, Japanese or Korean characters.
New Document opened on the most recent entry in the units that entry was
made in, so with Preferences › Units › General in millimeters, File › New
and New Without Dialog still made documents in points, and the rulers and
the Measure tool, which follow the document's units, read points. The
dialog now opens in the General units on a Recent entry too. An entry
made in pixels, and an entry that is a saved preset in the units it was
saved in, keep their units. Before, the dialog opened in the entry's
own units.
Units chosen in the Units menu were also replaced by the next tab, card
or preset chosen, for example the Web tab's pixels, or a Recent or Saved
card's units on a click or on the double-click that creates the
document. A choice made in the menu, or with ui.dialog.set (also while
More Settings or Manage Profiles is open), now stays until Create.
Without such a choice, clicking another Recent or Saved card still
brings back that card's own units.
Docs: docs/mcp.md (New Document), docs/target-app-parity.md evidence.
A ≈ button on a family's row in the font menus orders the listed families by
how alike they look to it: that family first, then the families that set the
same script (Japanese, Thai or neither), then the others, each group nearest
first. The Recent Fonts section is left out while the list is ordered this
way. A ≈ chip under the filters names the family and clears the order, with
that family still highlighted; closing the menu clears it too.
The measure is VectorCraft's own. Each face records its OS/2 PANOSE digits,
weight and width classes, x-height, cap height and average character width,
and its post italic angle; a named instance of a variable font takes its wght
and slnt settings. The system font scan reads the head table and the post
table's header besides the tables it read before, so installed families are
compared by the same numbers without loading them. A family is compared by its
face nearest an upright Regular, a number either face does not give is left
out, and a family of another kind counts as further away.
text.similarFonts {family, limit?} returns the same order, with errors for a
missing or non-string family, a family that is not available or not listed in
the font menus, and a limit that is not a whole number from 1 to 100000.
The Flattener Preview, Object > Flatten Transparency and the EPS, PDF and
print output that flatten transparency now walk each object without
transparency once, while planning, to list the type, strokes and
overprints that Convert All Text to Outlines, Convert All Strokes to
Outlines and dropping overprints change. The preview's lists, the no-op
check and the outlining all read that list.
On 100 groups of a stroked rectangle and stroked type plus five other
objects (309 nodes), with both options on and overprints dropped, the
preview looks at nodes 309 times where it looked 615 times, and
flattening looks at them 309 times where its walks made 2,352 visits,
outlines they made included. The flattened art and ids match the walk per option for
every mix of the three options.