Compatibility with Chromo

  • ooaadmin

    (@ooaadmin)


    5 years, 8 months ago

    Hello,
    the clock works with Safary, but not with chrome.

    Is there any issue compatibility?

    this is my skin Code:

    ooaWhite: {
    outerBorder: { lineWidth: 185, radius: 1, color: “white”, alpha: 1 },
    smallIndicator: { lineWidth: 1, startAt: 89, endAt: 94, color: “black”, alpha: 1 },
    largeIndicator: { lineWidth: 2, startAt: 83, endAt: 94, color: “black”, alpha: 1 },
    hourHand: { lineWidth: 3, startAt: 0, endAt: 54, color: “black”, alpha: 1 },
    minuteHand: { lineWidth: 3, startAt: 0, endAt: 80, color: “black”, alpha: 1 },
    secondHand: { lineWidth: 1, startAt: -15, endAt: 85, color: “#207eb7”, alpha: .85 },
    secondDecoration: { lineWidth: 3, startAt: 0, radius: 2, fillColor: “black”, color: “black”, alpha: 1 }
    }

Viewing 1 replies (of 1 total)
  • Plugin Author Rolf Allard van Hagen

    (@ravanh)

    5 years, 8 months ago

    Hi, the custom skin parameters need to be added without a name wrapper.

    Try this in the Custom skin parameters field:

    
outerBorder: { lineWidth: 185, radius: 1, color: 'white', alpha: 1 },
smallIndicator: { lineWidth: 1, startAt: 89, endAt: 94, color: 'black', alpha: 1 },
largeIndicator: { lineWidth: 2, startAt: 83, endAt: 94, color: 'black', alpha: 1 },
hourHand: { lineWidth: 3, startAt: 0, endAt: 54, color: 'black', alpha: 1 },
minuteHand: { lineWidth: 3, startAt: 0, endAt: 80, color: 'black', alpha: 1 },
secondHand: { lineWidth: 1, startAt: -15, endAt: 85, color: '#207eb7', alpha: .85 },
secondDecoration: { lineWidth: 3, startAt: 0, radius: 2, fillColor: 'black', color: 'black', alpha: 1 }
Viewing 1 replies (of 1 total)
  • The topic ‘Compatibility with Chromo’ is closed to new replies.