separate colour-mapping from bitsy palette? #4

New Issue

max · 2020-11-21T15:08:53Z

max commented

2020-11-21 15:08:53 +00:00

under some situations, a user will need to pick background and foreground colours carefully to make sure a particular part of the image is the background (colour 0) and another part is the foreground (colour 1). the colours they pick for this mapping are not necessarily the colours they want for the actual Bitsy room. is it worth adding a separate step for the colour map before the final palette selection? is this just going to be confusing for users? does this feature need to be hidden behind an "expert mode" toggle?

max added the

enhancement

label 2020-11-21 15:08:53 +00:00

max commented

2020-11-21 15:23:40 +00:00

idea: copy the "new palette" colour inputs above the palette selection. add a default option to the palette selection called "as above". leave the "new palette" option as is.

if bg/fg are a part of SelectedPalette they will need to be separated out in the application state.

SelectedPalette will need a new enum variant.

render_preview() will need a new step to map the background/foreground to the desired colours, if selected palette is not "as above".

idea: copy the "new palette" colour inputs above the palette selection. add a default option to the palette selection called "as above". leave the "new palette" option as is. if bg/fg are a part of SelectedPalette they will need to be separated out in the application state. SelectedPalette will need a new enum variant. render_preview() will need a new step to map the background/foreground to the desired colours, if selected palette is not "as above".

Sign in to join this conversation.