I had a design that the GFUI said was too complex and so it resulted in an error. Got it. I’d prefer that you increase server-side memory or whatever to make this unlikely, but this is what happens. Luckily, the GFUI presented a recommendation to use “ImageSplitter.net” to split my image. Bingo! Worked great. Wouldn’t it be great to integrate them (or their techniques) into your server workflow?
ImageSplitter’s output is a set of files, in my case four. They had filenames coded in their order:
- 0-0.png (northwest quadrant),
- 0-1.png (northeast quadrant),
- 1-0.png (southwest quadrant), and
- 1-1.png (southeast quadrant).
So far, so good. Now I load them into the GFUI. How do I place them? I zoomed in and carefully aligned the edges as best I could.
Unfortunately, while the GFUI shows no gap, a test print shows that there is one.
So here’s what I’d love.
Recognize a specific naming convention (or create a function) and auto-magically assemble the pieces and soft join them together.
I can choose the print settings and then the GFUI can load and process them sequentially at the rate the cloud is able to handle with one push of the start button.
Less WOW, but OK
Enable “auto-snap together” capability that “connects” two images by their proximate edges as if magnets snapping together.
Once I carefully aligned the images, I wanted a way to lock them in their spacial relationship.
Again, think of the magnet idea. Otherwise, it was too easy to nudge them slightly and get a gap.