Skip to content

Haque

My feedback

5 results found

  1. 16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Haque shared this idea  · 
  3. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Concerning scheduled maintenance, we have a standard 6-week release cycle, so scheduled downtime is usually fixed. You can add our Yodeck calendar to your calendar using this link:

    https://calendar.google.com/calendar/embed?src=starttech.eu_i0cravf325nspu504bihnl6q68%40group.calendar.google.com

    We do post an in-app notice for downtime of the Yodeck portal usually 24-48 hours in advance. We are planning to create a Status Page as well that will include a detailed health report of our platform along with scheduled maintenance notices, suing statuspage.io, which provides something like this: https://status.dropbox.com/

    Also, we are planning to include some sort of in-app message center that will also include changelog notices and other important messages that users might need to read.

    Hopefully, both the Status Page and the in-app message centre will be available within this year.

    Haque shared this idea  · 
  4. 57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We are planning to provide trigger support within 2020.

    We are now in the process of restructuring our rendering engine in order to allow several features to be implemented. One of these features is triggers. We are planning to initially support UDP, TCP/HTTP, GPIO events, and then support keyboard/mouse events.

    [Draft Specs follow:] Triggers will be available as a different menu item, in order to manage, set them up, test them, and so on. After setting them up, Users will be able to use them in Playlists, e.g. to skip a Media (or Subplaylist) entry, jump to specific Media (or Subplaylist) entry, and so on.

  5. 154 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Haque supported this idea  · 

Feedback and Knowledge Base