| @propertyWrapper | |
| public struct AnyProxy<EnclosingSelf, Value> { | |
| private let keyPath: ReferenceWritableKeyPath<EnclosingSelf, Value> | |
| public init(_ keyPath: ReferenceWritableKeyPath<EnclosingSelf, Value>) { | |
| self.keyPath = keyPath | |
| } | |
| @available(*, unavailable, message: "The wrapped value must be accessed from the enclosing instance property.") | |
| public var wrappedValue: Value { |
| touch ~/.android/repositories.cfg | |
| brew cask install caskroom/versions/java8 | |
| brew cask install android-sdk | |
| brew cask install intel-haxm | |
| brew install qt | |
| export ANDROID_SDK_ROOT="/usr/local/share/android-sdk" | |
| sdkmanager "platform-tools" "platforms;android-27" "extras;intel;Hardware_Accelerated_Execution_Manager" "build-tools;27.0.0" "system-images;android-27;google_apis;x86" "emulator" | |
| avdmanager create avd -n test -k "system-images;android-27;google_apis;x86" | |
| /usr/local/share/android-sdk/tools/emulator -avd test |
While I love my Geeklets, I had a pretty hard time to set them up consistently across varying monitor setups (home, work, on the go,...). The bad news first: There is no built in mechanism (as of 01/2013) to take care of this problem. Still there are good news: With some minor tinkering, you can automagically position your Geeklets across multiple setups.
The initial step is to add your Geeklets - you can totally ignore the positioning for the moment.