You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is being created to address the problem raised in the comments on issue #2.
When user accesses 'Saved Colors', selects a palette, toggles back to 'Fresh Input', goes back to 'Saved Colors', and then back to 'Fresh Input', the extract button displays.
If that button is clicked, it causes the colors to be run through the extract() function again, which duplicates the colors in the color-container section.
Currently, toggling and extracting and button displaying is controlled with the nasty/hacky usefulBoolean and usefulBoolean2 values being set to true or false depending on which functions run and then use if statements to determine if other code should run.
I suppose the necessity for a more elegant system for toggling is what is really being desired here.
The text was updated successfully, but these errors were encountered:
This is being created to address the problem raised in the comments on issue #2.
When user accesses 'Saved Colors', selects a palette, toggles back to 'Fresh Input', goes back to 'Saved Colors', and then back to 'Fresh Input', the extract button displays.
If that button is clicked, it causes the colors to be run through the
extract()
function again, which duplicates the colors in thecolor-container
section.Currently, toggling and extracting and button displaying is controlled with the nasty/hacky
usefulBoolean
andusefulBoolean2
values being set to true or false depending on which functions run and then use if statements to determine if other code should run.I suppose the necessity for a more elegant system for toggling is what is really being desired here.
The text was updated successfully, but these errors were encountered: