trolleway

POST /osc/commands/execute
{
    "name": "camera.startSession",
    "parameters": {}
}

#shoot
192.168.1.1/osc/commands/execute
{
  "name": "camera.takePicture",

rvl

Pushing to Multiple Git Repos

If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.

Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.

If in doubt about what git is doing when you run these commands, just

hujunfeng

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>PreferenceSpecifiers</key>
	<array>
		<dict>
			<key>DefaultValue</key>
			<string></string>
			<key>Key</key>

Birdie0

⚠️ This gist is no longer updated! For maintained, improved and even more extended guide click here.

---

How to use Discord Webhook

It's a JSON

First, learn JSON. It's not programming language, not even close. Just follow syntax rules and you will be fine.

shospodarets

const puppeteer = require('puppeteer');

(async () => {

    const browser = await puppeteer.launch();
    const page = await browser.newPage();
// Adjustments particular to this page to ensure we hit desktop breakpoint.
    page.setViewport({width: 1000, height: 600, deviceScaleFactor: 1});

    await page.goto('https://www.chromestatus.com/samples', {waitUntil: 'networkidle'});

fousa

class FairPlayer: AVPlayer {
  
  private let queue = DispatchQueue(label: "com.icapps.fairplay.queue")
 
  func play(asset: AVURLAsset) {
    // Set the resource loader delegate to this class. The `resourceLoader`'s delegate will be 
    // triggered when FairPlay handling is required.
    asset.resourceLoader.setDelegate(self, queue: queue)
    
    // Load the asset in the player.

ryanpato

//
//  XCUIElement+Wait.swift
//
//  Created by Ryan Paterson on 12/12/2020.
//

import XCTest

extension XCUIElement {
    /// The period of time in seconds to wait explicitly for expectations.

nicklockwood

// This gist demonstrates how you can implement versioning for a Codable struct to support loading
// old serialized data after changing the structure. Notable features of this solution:
//
// * No need to make new properties optional, or to perform post-processing on the struct after
//   loading in ordeer to populate missing values
// * No need to change the call site - from the outside this struct behaves just the same
//   as if we had implemented codable directly in the normal way.
// * Versioning can be applied individually to parents or leaves in a larger tree of
//   structs without affecting the other elements
// * This approach will work even if the original struct was not designed with versioning in mind