You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, but before I go through all this paper-work I'd like to ask the question whether or not the authors of this nice converter app expect that PDFs should be generated when the workflow condition "file accessed" is met?
Nothing happens when I access a file, but the conversion machinery does its job for newly generated files (really new files, renamed files). Copy would work safe for #449.
The text was updated successfully, but these errors were encountered:
Coming back to myself: this is actually a problem with the wording in the UI. From the notion "file accessed" as a user I would expect that such a condition would be met by accessing the file, e.g. by opening it in an editor or viewer. Instead, however, "file accessed" is really the "touched" event. And this is not so often triggered, AFAIK.
Still it would be could if a PDF conversion could be triggered by someone trying to view a file (think e.g. of HTML where there is no viewer, instead the cloud frightens the users by displaying just the HTML source code).
Sorry, but before I go through all this paper-work I'd like to ask the question whether or not the authors of this nice converter app expect that PDFs should be generated when the workflow condition "file accessed" is met?
Nothing happens when I access a file, but the conversion machinery does its job for newly generated files (really new files, renamed files). Copy would work safe for #449.
The text was updated successfully, but these errors were encountered: