Skip to content

Instantly share code, notes, and snippets.

View SteveALee's full-sized avatar

Steve Lee SteveALee

77 followers · 137 following
View GitHub Profile
@SteveALee
SteveALee / gist:a9f838b79639949ac879
Created September 9, 2015 18:57
.njsproj for https://github.com/Microsoft/nodejstools/issues/427
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{1bf69820-c08a-4207-8084-5f6b180e52ff}</ProjectGuid>
<ProjectHome />
<ProjectView>ShowAllFiles</ProjectView>
<StartupFile>index.js</StartupFile>
<WorkingDirectory>.</WorkingDirectory>
@SteveALee
SteveALee / gist:4bd828882f2027f8878eb9ef856f7f60
Last active October 31, 2019 17:06
Responsive SVG in Flexbox
<!DOCTYPE html>
<html lang="en">
<style>
body {
margin: 1px;
}
#main {
display: flex;
flex-direction: column;
@SteveALee
SteveALee / gist:0e78dff6040780720093a14ce3a6f0ba
Last active September 16, 2021 05:12
Have browsers update when editing 11ty config file

By default 11ty devmode uses browsersync to reload webbrowsers whenever it regenerates pages to _site. It does this automatically when template files change.

However, the .eleventy.js file is only loaded when 11ty starts so if you edit shortcodes (say) you need to stop and restart 11ty.

The solution is to use nodemon to restart 11ty automatically when the config file changes. But then you need to use browser F5 to refresh. The solution to that is to get browsersync to reload the browsers To achieve that, the 11ty browsersync config option allows you to define a callback when browsersync is ready and you can add a browser reload call there.

Here's example code from music-practice-tools

@SteveALee
SteveALee / README.md
Last active April 11, 2024 13:21
Build audacity with ASIO support on Windows

Build your own Audacity for Windows with ASIO driver support

You might want Audacity to work with the ASIO drivers supplied with your sound devices. Commmon reasons for this are:

  • Only ASIO drivers are available (eg Behringer mixers)
  • Performance - ASIO has low latency (delays)
  • You don't want to use the ASIO4All bridging driver with non ASIO drivers
  • Multi channel support - though Audacity is not so good at handling other than Stereo or Mono

Due to licensing restrictions the Audacity team cannot provide a prebuilt version with Windows ASIO driver support. But with this guide and script you can easily build your own Audacity with ASIO support.