이 페이지의 이전 버전을 보고 있습니다. 현재 버전 보기.

현재와 비교 페이지 이력 보기

« 이전 버전 8 현재 »

Finding the cause of a W Player API failure

The cause of a W Player API failure can be received as an error object through the callback function that is set as $wp.setDefaultCallback().

  $wp.setDefaultCallback(function(dataset) {
  // dataset.type: ‘error’
  // dataset.sub: ‘content.getPage.setProperty’
  // dataset.data: ‘Error: setProperty: Requested property is not supported, property = ip
  }   
  

Checking the exceptions during running of W Player API

Exception occurrences during running of API can be checked by adding a try-catch statement in the code.

  let version = null;
  try {
      version = $wp.utility.getApiVersion();
  } catch (e) {
      console.log("[getApiVersion] Exception occurred = ${e}");
  }
  

Using Tizen API in web content

Use Tizen API to access device functions (e.g., remote-control signal reception) directly. Refer to the Tizen developer page for details. ▶ Tizen 개발자 홈페이지

Importing logs

If you enter "wplayer_api_nopswd" in the log script, logs that were saved by using $wp.utility.log() can be imported as a file.