[Free] Clock-Pro Extension đź’Ą

Extensions Extensions IDE
#1

ClockPro

ss

Documentation

GetDeviceTime

component_method

component_event
component_event1134Ă—170 17 KB

Purpose:
The GetDeviceTime function fetches the current time directly from the device on which your app is running. This function is particularly useful in scenarios where you want to obtain the device’s local time, which may differ from other time zones, especially if your app deals with scheduling or time-sensitive features.

Input Parameter:

  • id (String): A unique identifier for the request. This helps to associate the event response with the specific function call.

GetTimeByTimeZone

component_method (1)

component_event (1)
component_event (1)1134Ă—170 17.6 KB

Purpose:
The GetTimeByTimeZone function fetches the current time for a specified timezone ID. This is useful for applications that need to display time for different regions or manage scheduling across multiple time zones.

Input Parameters:

  • timeZoneID (String): The ID of the timezone for which you want to fetch the current time (e.g., “America/New_York”).
  • id (String): A unique identifier for the request, used to associate the response with this specific call.

SetTargetTime

component_method (2)

component_event (2)
component_event (2)1476Ă—170 18.1 KB

Purpose:
The SetTargetTime function sets a target date and time in the format dd/MM/yyyy HH:mm:ss and calculates the time left until that target. This is useful for countdowns and deadlines within your application.

Input Parameters:

  • dateTime (String): The target date and time in the specified format.
  • id (String): A unique identifier for the request, used to associate the response with this specific call.

SetStartAndEndTime

component_method (3)

component_event (3)
component_event (3)1476Ă—170 18.5 KB

Purpose:
The SetStartAndEndTime function sets the start and end date-times in the format dd/MM/yyyy HH:mm:ss and returns the time difference between the two. This can be useful for timing events or calculating durations.

Input Parameters:

  • startDateTime (String): The start date and time in the specified format.
  • endDateTime (String): The end date and time in the specified format.
  • id (String): A unique identifier for the request, used to associate the response with this specific call.

GetDeviceTimeZone

component_method (4)

Purpose:
The GetDeviceTimeZone function retrieves the current timezone of the device. This is helpful for applications that need to adjust their functionality based on the user’s location.

Input Parameters:

  • None: This function does not require any input parameters.

Work on progress to add more item suggest me what should i add

Download from here
ClockPro ( SILKTUNE ).aix (7.1 KB)

Demo Apk Available Soon

Get timezone ID Here

Donate Me :heart_eyes: :smiling_face_with_three_hearts:

5 Likes
#2

In most cases, it is enough to use a regular clock unit. it kind of takes time out of the device too. well, if it was necessary to have this separate extension, then why not:) the question arises 1. you are trying to make the process in an asynchronous way. i.e., a request and an answer through an event. Why? why can’t this be done with a synchronous direct response function? does it take a lot of time to make a request? I mean, why not get an answer right away, namely through an event? maybe it’s related to the ID.the role of this ID is not entirely clear. give an example if possible.

2 Likes
#3

Yes it have multiple times result second - hours - minutes - year - month - days that’s why I use it

Id system= for multiple call using one extention