Signal sent by the ExportJobInterface when the number of files is known.
Such an event is fired a short while after calling DataSessionInterface.export3D, DataSessionInterface.export2D or DataSessionInterface.exportSVG.
The attachment is a number telling the number of files of the export procedure.
Signal sent by the ExportJobInterface when ExportJobInterface.cancel is called and the export procedure was running.
The ExportJobFinished signal will be triggered shortly after.
The attachment for events of this type is a number telling the file offset that is over, or undefined if all job requests were cancelled.
Signal sent by the ExportJobInterface when the 3djuump Infinite backend has finished processing a file in the export job. Even when there was an error, or when the process has been cancelled, the ExportJobFinished signal will be fired.
The attachment for events of this type is a number telling the file offset that is over, or undefined if the procedure failed before retrieving the file count.
Signal regularly sent by the ExportJobInterface when the ExportJobInterface 3d export procedure is running to get the progress /state of the procedure (ExportJobInterface.getFileProgress / ExportJobInterface.getFileState).
The attachment is a ExportProgressAttachment.
Signal sent by the ExportJobInterface when the ExportJobInterface.getDownloadURL call is ready to be called.
Such an event is fired after ExportJobInterface.computeDownloadURL is called (this call should also be called after receiving the ExportJobFinished signal in case of success).
The attachment is a ExportURLAttachment.
The ExportJobInterfaceSignal lists all the signals that may be sent by the ExportJobInterface.
These signals are emitted by the ExportJobInterface to monitor the progress of an export job call (DataSessionInterface.export3D, DataSessionInterface.export2D, DataSessionInterface.exportSVG), and when the export job procedure is over (successfully or not).
Please refer to ExportJobInterface for more information.
See
ExportJobInterface