Inkscape

Custom gradient swatches

Bug #594443 reported by su_v
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Inkscape
In Progress
Medium
Unassigned

Bug Description

followup to bug #594441
"Fully support custom swatches in the Stroke&Fill dialog"

Inkscape 0.47+devel r9495 on OS X 10.5.8

- when working with gradient swatches, the color chooser widget in the Fill&Stroke dialogs edits the first color stop and offers no possibility to edit the other stops. Either disable it for custom gradient swatches (and allow only the use of the gradient editor) or add a selector for the stops.

- changing between different gradient swatches works when clicking on the swatches in the 'Auto' palette, but not when selecting a different 'linearGradient' as listed in the Fill&Stroke dialog for swatches: changing the swatch using this popup-list does change the gradient but does not correctly update the location of the gradient stops so that the object appears e.g. as the same solid color as one of the gradient stops or empty (if the gradient fades to transparency).

Tags: color gradient
Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed on Windows XP, Inkscape r9451.

Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Jon A. Cruz (jon-joncruz) wrote :

Disabled dialog for custom swatches.

Changed in inkscape:
status: Confirmed → In Progress
Revision history for this message
ScislaC (scislac) wrote :

~suv: any comments on if the implementation is good by you in trunk?

Revision history for this message
su_v (suv-lp) wrote :

ScislaC wrote:
> ~suv: any comments on if the implementation is good by you in trunk?

1a - Editing custom gradient swatches in 0.48.x:
- ok (depends on the deprecated gradient editor).

1b - Editing custom gradient swatches in current trunk:
- The color selector widget displayed below the list of custom swatches does not update when selecting a custom gradient swatch and - if any value is changed - simply overwrites the first stop of that custom gradient swatch based on edits of whatever color it happens to display. IMHO either the color sliders are disabled (insensitive) when selecting a custom gradient swatch, or get a stop selector and update with the color of the first gradient stop. The current implementation is confusing.

- With default preferences ('Use legacy Gradient Editor' is _not_ enabled), it is still possible to edit a gradient swatch currently not in use via context menu of the 'Auto'-palette: 'Edit…' opens the deprecated gradient editor dialog. I don't know whether this went unnoticed or is intentional. Based on discussions elsewhere, it seems that no one really cares for this feature - probably the entry in the context menu of the 'Auto'-palette should be disabled if usage of the legacy editor is not enabled in the preferences, or removed completely.

2a - Position/size of custom gradient swatches in 0.48.x:
- see bug description (still present in 0.48.x)

2b - Position/size of custom gradient swatches in current trunk (r11535):
- Not yet fixed: Inconsistent placement and rendering of newly assigned custom gradient swatches still occurs (AFAICT behavior varies depending on whether the current (or prior) custom swatch was applied via Fill&Stroke or 'Auto'-palette, needs further investigation).

3 - changing from swatch paint to a regular gradient paint fails (0.48.x as well as trunk), see
<https://bugs.launchpad.net/inkscape/+bug/1015686/comments/3>

Revision history for this message
Lucian (lucian-j) wrote :

Hi,

For what it's worth, I quite like the "edit" option in the auto palette. It's by far the simplest way to experiment with changing your colour palette, because it doesn't require you to go hunting for specific objects that currently use a swatch to be able to edit it. Unfortunately, as things stand in 0.91 clicking the edit option in the auto palette context menu launches the in place gradient editor by default, which makes no sense, since there's nothing specific on the canvas to edit.

Is there another way that I'm missing to edit swatches without finding an object that uses them first?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.