Package Torello.Browser
Class Media.PlayerMessage
- java.lang.Object
-
- Torello.Java.Additional.BaseType
-
- Torello.Browser.Media.PlayerMessage
-
- Enclosing class:
- Media
public static class Media.PlayerMessage extends BaseType
Have one type per entry in MediaLogRecord::Type Corresponds to kMessage
Hi-Lited Source-Code:- View Here: Torello/Browser/Media.java
- Open New Browser-Tab: Torello/Browser/Media.java
-
-
Field Summary
Serializable ID Modifier and Type Field protected static long
serialVersionUID
For Object Serialization.Type Properties Modifier and Type Field String
level
Keep in sync with MediaLogMessageLevel We are currently keeping the message level 'error' separate from the PlayerError type because right now they represent different things, this one being a DVLOG(ERROR) style log message that gets printed based on what log level is selected in the UI, and the other is a representation of a media::PipelineStatus object.String
message
[No Description Provided by Google]
-
Constructor Summary
Constructors Constructor Description PlayerMessage(String level, String message)
ConstructorPlayerMessage(JsonObject jo)
JSON Object Constructor
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description boolean[]
optionals()
Implementing this method allows sub-classes to specify which JSON Properties may be absent or null.
-
-
-
Field Detail
-
serialVersionUID
protected static final long serialVersionUID
For Object Serialization. java.io.Serializable- See Also:
- Constant Field Values
-
level
public final java.lang.String level
Keep in sync with MediaLogMessageLevel We are currently keeping the message level 'error' separate from the PlayerError type because right now they represent different things, this one being a DVLOG(ERROR) style log message that gets printed based on what log level is selected in the UI, and the other is a representation of a media::PipelineStatus object. Soon however we're going to be moving away from using PipelineStatus for errors and introducing a new error type which should hopefully let us integrate the error log level into the PlayerError type.
-
message
public final java.lang.String message
[No Description Provided by Google]
-
-
Constructor Detail
-
PlayerMessage
public PlayerMessage(java.lang.String level, java.lang.String message)
Constructor- Parameters:
level
- Keep in sync with MediaLogMessageLevel We are currently keeping the message level 'error' separate from the PlayerError type because right now they represent different things, this one being a DVLOG(ERROR) style log message that gets printed based on what log level is selected in the UI, and the other is a representation of a media::PipelineStatus object. Soon however we're going to be moving away from using PipelineStatus for errors and introducing a new error type which should hopefully let us integrate the error log level into the PlayerError type.
Acceptable Values: ["error", "warning", "info", "debug"]message
- -
-
PlayerMessage
public PlayerMessage(JsonObject jo)
JSON Object Constructor- Parameters:
jo
- A Json-Object having data about an instance of'PlayerMessage'
.
-
-
Method Detail
-
optionals
public boolean[] optionals()
Description copied from class:BaseType
Implementing this method allows sub-classes to specify which JSON Properties may be absent or null. When binding aJsonObject
to a Java-Object, if some of the expected fields for the Java-Object map to Properties which might be left-out or omitted, then that may be indicated by setting that fields array positionTRUE
.
NOTE: This array should have a length equal to the number of fields contained by the Java Object. The first boolean in the array should specify whether the first Object Field may by absent. The second boolean should specify whether the second Object Field is optional in the JSON - and so on and so forth...
-
-