I assume I’m like many of you, trying to use every last inch of a piece of nice proofgrade material. To do so I often position my next cut to take advantage of as much material as I can.
In doing so, I ran into an interesting problem.
When you rotate artwork, that includes a rastered (bitmap) image, the GFUI increases the bounding boxes of the artwork to capture the corners of the rastered image (even if it’s transparent). And in doing so, makes it much harder to place and print, because now there are non-printing regions going off the edge of the printable area, and it won’t allow it to be sent.
It is my guess that there are at least a few pixels that are not fully white. It will not make a lot of difference in the cut but the Gfui will still act on it,
If you can export the design and trim it to the minimal area that would be a start, If you brought it into Gimp and masked the design you could just make the rest white and export it as a png as a jpg will be squirrely where it is supposed to be white.
I’ve rotated and had the bounding box look like that while rotating but once I clicked off and back on again, it had shrunk to the size of the art itself and I was able to move it close to nest. I’m about 99.5% sure (but it is early and I haven’t retested it just yet).
I assume your bounding box stays that way? Though it may have been for vectors…
I had this very question a few years ago and I just couldn’t wrap my head around, so I had to make myself a visual. I think the only solution is to resave your artwork at the angle you want or moving the material away from the edge. I usually just use the premium line shape to whack off the chunk of material I want to use and then reposition it.
And while I understand why this happens, I’m still curious about solutions.
I wonder if you put the embedded image in a vector mask, if that would work, and solve this.
I think the GFUI does something smart with tightening up the bounding box when there are extra transparent background on a raster image. It just doesn’t seem to recompute that when you rotate the image. So maybe GF could fix it too.