Open GoogleCodeExporter opened 9 years ago
This probably happens when there's no printer driver installed on your Mac.
Try install a printer driver --- even
a shared one or a 'fake' one will work.
Original comment by frankshaka
on 27 Feb 2009 at 6:11
I have no printer installed on my system, since I don't have one. So your
conclusion
is correct :) .
Installing a fake printer is of course an option, but all the other
applications on
my Mac work perfectly fine when using the Print dialog to save to PDF. Yes, I
can
install a fake printer, but that doesn't look like a real fix to me. Will this
problem nevertheless be fixed somewhere in the future?
Original comment by harmhilvers
on 5 Mar 2009 at 8:05
That's what we've also been hoped for since we're Mac users, too :) . Eclipse
SWT is the window system
framework XMind is based on, but unfortunately the printing abilities it
provides seems not so satisfying on
all platforms. It tries to treat each platform equally and thus have to give up
some great features on the Mac,
such as the Save-PDF-File-without-printer-driver feature. We don't know whether
it's going to support this
feature in the future. The answer seems no at least until their next version or
two from the last schedule
they've made. However, we have successfully saved the XMind maps to PDF files
as long as there's one shared
printer driver installed on our machines. The printer from which you installed
the driver is NOT required to be
in the network when you do the saving. Sorry for the inconvenience but we're
unable to guarantee when this
problem is going to be fixed.
Original comment by frankshaka
on 6 Mar 2009 at 11:05
Since I don't have a printer and there are none available on my Wireless
network; I
went into System Preferences, printers, IP, type "AAAA" in the Adress field..
and
clicked ADD.
Went back to XMind3 and used the Print features and "Save as PDF" option: the
PDF was
created.
THE WORKAROUND WORKS !
Original comment by gilloust...@gmail.com
on 24 Sep 2009 at 2:18
Original comment by stephen0...@gmail.com
on 23 Dec 2010 at 9:25
Original issue reported on code.google.com by
harmhilvers
on 26 Jan 2009 at 6:32