[Feature Request] Is it possible to encode all the building blocks on the same screen so that it can be directly printed as a large picture
tanminggang opened this issue · 5 comments
Is your feature request related to a problem? If so, please describe it.
A description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A description of what you want to happen or what the feature would look like when implemented.
Describe alternatives you've considered
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
I'm a little confused on what this feature request is for - is this related to the Bricklink piece export, or maybe exporting the result as a .png?
He means to create a slightly different version of the instructions, with all of the 16x16 blocks shown together side-by-side, with the numbers on the tiles, and just one color key. Personally, I think that's the better and easier way to go, because you can verify that everything is lining up right as you build it... I just did it by cutting and pasting a screenshot of each 16x16 block.
Here's an example...
Looking into this - seems doable, but my main concern is memory usage. It would be nice if the instruction generation logic were smart enough to handle variable edge lengths for pages larger than being locked into 16x16, but that would require a large logic rewrite. Exporting as a single image seems like a good compromise, but I'll have to see if this causes issues for large resolutions.
Or to make it super simple, if you do it this way, it can really just be one single large PNG image. You can add the color-key to the bottom, plus a watermark for the site. If you've ever ordered a clone-brand art set, they just do the instructions like this, either as one single printed image, or as four quadrants if it's big, to save on costs. Personally, I like that way better. Easy! =)
Easy is subjective here. Exporting as a single image is doable, but causes UI bloat due to 2 options that are designed to do the same thing. I'll take a look, but will also have to be careful about how many additional lines of code will be added by having a completely separate way to create instructions.