Hello,
I would like to contribute to bugreport B97047.
I can observe the same problem here. But this time it does not happen with openoffice files, but with MS Office or other files. I think, this has nothing to do with the filetype, but i happens after running the application for some time and opening a bunch of files.
Maybe it comes from spaces in filenames, I'm not sure.
Any case after closing and reopening the application the problem has disappeared, but reappears again after some time. I did not observe this error in previous versions.
thanks
reinhold
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hello Reinhold,
The FileAttachment editor (as well as the FileAttachmentController class) saves information into a temporary file. To open this file, it uses the 'Process.Start' method, which automatically searches an associated application and starts it.
The FileAttachment editor adds a handler to the 'Exited' event of the started process to delete the created file.
Currently, we suspect that the file is opened by an intermediate application which starts a new process and immediately finishes. So, the FileAttachment editor immediately receives a notification that the started process "exited" and deletes the created file.
We will work on this issue and publish a solution when it is ready.
Thanks,
Dan
Hello,
We have fixed this issue.
For more details, see "FileAttachments.Win: Introduce a capability to implement a custom algorithm to open an attachment with the help of some application" at http://www.devexpress.com/issue=S30555
Thanks, Dan.