aboutsummaryrefslogtreecommitdiffstats
path: root/e-util/e-charset.c
diff options
context:
space:
mode:
authorMatthew Barnes <mbarnes@redhat.com>2013-05-11 00:44:10 +0800
committerMatthew Barnes <mbarnes@redhat.com>2013-05-11 00:44:10 +0800
commit72f465b17342831163422cad05eaa6e648fffa19 (patch)
tree214273c6aa0e125762e0d94f080cf527b29a24e4 /e-util/e-charset.c
parent16a95bfa16b3864268e0ab0916bb6c02ec626fe0 (diff)
downloadgsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar.gz
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar.bz2
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar.lz
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar.xz
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.tar.zst
gsoc2013-evolution-72f465b17342831163422cad05eaa6e648fffa19.zip
Bug 7000028 - Drag-n-drop export of a file produces 0 sized PDF file
em_utils_print_messages_to_file() was doing so asynchronously, but unfortunately drag-n-drop is a synchronous protocol. So by the time the asynchronous print operation completed, the URI list pointing to the temporary PDF files had already been passed to the file manager. The only reason the files were created at all was because we test the generated file name with open(...O_CREAT...) before starting the print operation, and I'm not convinced that test is even necessary.
Diffstat (limited to 'e-util/e-charset.c')
0 files changed, 0 insertions, 0 deletions