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
I wouldn't say it's preventing correct reading of the scrambles, but it's definitely noticeable enough to make the eyes go out of the scrambling line (at least with my printed version of the scrambles).
I get why we would put watermarks on scrambles unusable officially (eg: the staging/unofficial ones).
For manually generated scrambles I'm not sure where this comes from as I couldn't find an issue in the repository (but maybe I missed it).
Even though these are manually generated, such scrambles can (will) be used officially, and I'd rather avoid making the scramblers' life harder than it already is.
Describe the solution you'd like
Would it be possible to simply remove that watermark?
Other solutions: move it out of the way (eg: at the top/bottom?).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I just noticed there is now a "MANUAL" watermark on manually generated scrambles: 3x3x3 Multiple Blindfolded Round 1 Scramble Set A Attempt 1.pdf
I wouldn't say it's preventing correct reading of the scrambles, but it's definitely noticeable enough to make the eyes go out of the scrambling line (at least with my printed version of the scrambles).
I get why we would put watermarks on scrambles unusable officially (eg: the staging/unofficial ones).
For manually generated scrambles I'm not sure where this comes from as I couldn't find an issue in the repository (but maybe I missed it).
Even though these are manually generated, such scrambles can (will) be used officially, and I'd rather avoid making the scramblers' life harder than it already is.
Describe the solution you'd like
Would it be possible to simply remove that watermark?
Other solutions: move it out of the way (eg: at the top/bottom?).
The text was updated successfully, but these errors were encountered: