IProgressData Interface
Assembly: Qlik.Engine.dll
Syntax
[ValueClass]
public interface IProgressData
Properties
Name | Description |
---|---|
Completed |
This property is not used. JSON property name: qCompleted |
ErrorData |
Information about the error messages that occur during the script execution. JSON property name: qErrorData |
Finished |
True if the request is finished. JSON property name: qFinished |
KB |
This property is not used. JSON property name: qKB |
Millisecs |
Request duration in milliseconds. JSON property name: qMillisecs |
PersistentProgress |
A progress message is persistent when it informs about the start or end of a statement. For example, it can inform about the total number of lines fetched from a data source or tell that the app was saved. All persistent progress messages between two GetProgress calls are summarized in this string. Contrarily to qPersistentProgressMessages, the content of the localized message string is displayed (not its message code). JSON property name: qPersistentProgress |
PersistentProgressMessages |
List of persistent progress messages. JSON property name: qPersistentProgressMessages |
Started |
True if the request is started. JSON property name: qStarted |
Total |
This property is not used. JSON property name: qTotal |
TransientProgress |
A progress message is transient when it informs about the progress of an ongoing statement. For example, it can tell how many lines are currently fetched from a data source. All transient progress messages between two GetProgress calls are summarized in this string. Contrarily to qTransientProgressMessage, the content of the localized message string is displayed (not its message code). JSON property name: qTransientProgress |
TransientProgressMessage |
Transient progress message. JSON property name: qTransientProgressMessage |
UserInteractionWanted |
True when the engine pauses the script execution and waits for a user interaction. JSON property name: qUserInteractionWanted |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!