It's already here in the thread
Hi, can you send me version 4.23 or a link.
If you open Activity Monitor.app and enable the "Restricted" column, you'll find that the processes that are "Restricted" are the ones that do not show the print driver PDE (print dialog extensions) features, but instead show the generic print options interface.
Whether the app's are sandboxed is irrellevant as Xerox's drivers are properly sandboxed and signed (and 64-bit) themselves.
Apple is contraditory in their behaviour in regards to print vendors as Apple have effictively shut down the ability to use PDEs in print drivers for all but apps who explicitly opt out of "library validiation" (none of Apples Mojave apps opt out as far as I can see) yet I cannot seem to find an official statement from Apple that is so.
Works for me. FYI this version does not provide the prompt for code in Apple applications. But I suspect you knew that ahead of time based on our past discussion.
Small steps forward. Be nice if Apple replied in kind.
Bare with me gang, I have two colleges with a high percentage of Mac users on accounting based copiers that seem to wait for a daily update from me on this.
Thanks for the good works.
treat it as a beta, in xerox terms "spar"
Okay, I missed the link. But that begs a bigger question. If this is NOT on the support site does Xerox consdier it ready for prime time or should we treat it as a late beta?
BTW, I do work with a rather large distibutor of Xerox equipment here in the NE (who supplies our University with machines) and they would like to hear an answer to that too.
So we are talking hungreds of machines with lots of users. N'est pas?
It was linked by Fabio right here in this very thread
I would like to give the new driver a try out but each time I dial through the options on the support page I still come up with 4.22.2(2025). Is there another location for retreiving an up-to-date driver?
in my case 4.23 worked, my case was that if i entered an account id number, the machine always printed out, invalid account id
so upgraded from 4.22 to 4.23 fixed it, this was on a altalink machine
so now using XSA without any issues