Make the "Remap" functionality available from scripts

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

Start with the transaction documentation in api/app.md and determine how script-driven palette changes relate to the existing Remap behavior. Clarify how scripts should invoke Remap and how the start of modifications is identified; the issue is done when that behavior is specified and exposed consistently for scripts.

Written by the indexing model from the issue text.

Description

It would be nice to be able to "Remap" the palette from scripts or make the button visible if the script modifies the palette.

At the moment the difficult part of this one is where/how to indicate the "start point of modifications". In the UI it's from the first modification of the user palette, on scripts it might be good to have a way to indicate the start of modifications (maybe the start of a transaction?)

From: https://community.aseprite.org/t/sort-swatches-by-usage-suggestion/1641/7?u=dacap

Dominant language
No language data
Stars
310
Forks
68
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aseprite/api

All issues in aseprite/api

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.