fde101 Posted February 7, 2020 Share Posted February 7, 2020 Someone might want to review this behavior: There is a very strange discrepancy between the way objects which are positioned over artboards but are actually on a layer outside of artboards are treated when using File/Export compared to when using File/Print. I am aware there is another aspect of this that was already reported here: JGD 1 Link to comment Share on other sites More sharing options...
JGD Posted February 7, 2020 Share Posted February 7, 2020 42 minutes ago, fde101 said: Someone might want to review this behavior: There is a very strange discrepancy between the way objects which are positioned over artboards but are actually on a layer outside of artboards are treated when using File/Export compared to when using File/Print. I am aware there is another aspect of this that was already reported here: Yep, I'm aware. We are already discussing that also on the thread I opened, and all signs point to those objects always appearing regardless of the media your outputting to (as “printing” is, in a sense, a way of “exporting” your artwork to a physical format). I mean, if this was release-quality software, such a discrepancy would be unacceptable, but that's precisely the kind of thing public betas are meant to weed out. Mithferion and fde101 1 1 Link to comment Share on other sites More sharing options...
fde101 Posted February 7, 2020 Author Share Posted February 7, 2020 13 minutes ago, JGD said: I mean, if this was release-quality software, such a discrepancy would be unacceptable Your thread is exactly the one I linked to. I added this here to make sure it was getting the attention of the developers so that this "unacceptable" discrepancy was that much less likely to make it into the release version... I hope... JGD 1 Link to comment Share on other sites More sharing options...
JGD Posted February 9, 2020 Share Posted February 9, 2020 On 2/7/2020 at 1:00 PM, fde101 said: Your thread is exactly the one I linked to. I added this here to make sure it was getting the attention of the developers so that this "unacceptable" discrepancy was that much less likely to make it into the release version... I hope... I got it, and I ran with it as well. But after all, this is what, the first 1.8.x Beta? I'm confident it will get fixed before the GM release. It all fits with my whole “being cautiously optimistic” theme of late. Link to comment Share on other sites More sharing options...
fde101 Posted February 9, 2020 Author Share Posted February 9, 2020 1 hour ago, JGD said: the first 1.8.x Beta There have been several beta releases for Publisher 1.8 already, and it was already commented on that the major features they plan on adding for the 1.8 release are already there, so they are evidently focused on bug fixes and cleaning up right now... For Designer this is the first beta release, but given how far into the Publisher beta we are, I'm not sure how many more to expect they will be doing. Link to comment Share on other sites More sharing options...
JGD Posted February 11, 2020 Share Posted February 11, 2020 On 2/9/2020 at 5:45 PM, fde101 said: There have been several beta releases for Publisher 1.8 already, and it was already commented on that the major features they plan on adding for the 1.8 release are already there, so they are evidently focused on bug fixes and cleaning up right now... For Designer this is the first beta release, but given how far into the Publisher beta we are, I'm not sure how many more to expect they will be doing. Oh, yes, I hadn't thought of that… Well, if it isn't fixed it may become a serious StudioLink/cross-app file format interoperability issue. Better test this and/or do some demos to press them on this issue? Guys? Link to comment Share on other sites More sharing options...
Staff Sean P Posted February 12, 2020 Staff Share Posted February 12, 2020 Thanks for the heads up fde101, I've reproduced this and will get it passed on to development, it is worth noting that 1.7 does have the same behaviour, so at least it isn't a regression. JGD 1 Link to comment Share on other sites More sharing options...
fde101 Posted February 12, 2020 Author Share Posted February 12, 2020 59 minutes ago, Sean P said: at least it isn't a regression Perhaps not, but with the new layer editing behavior mentioned by @JGD in the thread that I linked to, it is more of a concern now than before. JGD 1 Link to comment Share on other sites More sharing options...
JGD Posted February 18, 2020 Share Posted February 18, 2020 On 2/12/2020 at 10:54 AM, Sean P said: Thanks for the heads up fde101, I've reproduced this and will get it passed on to development, it is worth noting that 1.7 does have the same behaviour, so at least it isn't a regression. It shouldn't be a terribly hard fix, though, or is it? How different is the print stack from the export one? Isn't printing pretty much the same as exporting to a universal format and sending the output to a printer? Maybe I'm oversimplifying things, but from what I read on it way back in the day, printing jobs basically consisted of feeding PostScript data through drivers and parallel ports to those devilish things. I know things have evolved a bit until now, but the overall process is probably very similar, as in “export > send to driver > send to USB controller > send to printer”… Link to comment Share on other sites More sharing options...
fde101 Posted February 18, 2020 Author Share Posted February 18, 2020 10 minutes ago, JGD said: feeding PostScript data On the Mac it would be PDF now. Not sure what Windoze is using these days... Link to comment Share on other sites More sharing options...
Recommended Posts