-- Originally posted by (AT sourceforge.net): rtautenh -- -- This ticket was imported from http://sourceforge.net/p/rkward/bugs/74 on 2017-05-30 15:26:40 +0100 -- Since there is no kprinter in KDE4, rkward with default options will not show a printing dialog. Workaround is to install and use xpp. -- Labels: user interface --
Ok, this should finally be fixed in the development version, now. Please test. Note: To see the printing dialog with dev.print\(\), use "dev.print\(rk.printer.device\)". Using Device->Print from the menu / Ctrl+P should work out of the box. Note2: RKWard no longer set options\("printcmd"\). However, there's a new free text input field in Settings->Configure RKWard->R backend, in case you have use for that.
- **summary**: No printing dialog with KDE4 --> FIXED IN SVN: No printing dialog with KDE4
-- Originally posted by (AT sourceforge.net): rtautenh -- Ctrl+P works now within in the editor and brings up the KDE printing dialog. However, nothing happens if Ctrl+P is pressed \(or Device->Print is selected\) in a graphic window. No error message is displayed in the shell. Version 0.5.6z+0.5.7+devel1 Using KDE Development Platform 4.4.92 \(KDE 4.4.92 \(KDE 4.5 RC2\)\)
Thanks for testing. Is that with the development version of R, by any chance? If so, I think the problem should be fixed after an SVN up. Otherwise, could you please check the "Command Log" window? Any error messages, there? Regards Thomas
-- Originally posted by (AT sourceforge.net): rtautenh -- I'm using R version 2.12.1, which doesn't know the fileext argument for tempfile\(\). dev.set \(2\) dev.print \(rk.printer.device\) Error in tempfile\(fileext = ".ps"\) : unused argument\(s\) \(fileext = ".ps"\) Calls: dev.print ... eval.parent -> eval -> eval -> dev.copy -> device -> tempfile
I see, thanks. So does it work, now, after another svn up?
-- Originally posted by (AT sourceforge.net): rtautenh -- Device -> Print works now \! However, keys like Ctrl+P or Ctrl+W do not work in the graphics window, but that is probably a separate issue.
Yes, that's a separate issue. I have opened a new ticket for that.
- **status**: open --> open-fixed
- **status**: open-fixed --> closed-fixed