dnrops
/
100-days-of-swiftui-and-combine
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Complete Day 86

This commit is contained in:
CypherPoet 2020-01-18 05:24:14 -06:00
parent f8cfacae28
commit 7f5e852d28
3 changed files with 4 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -91,10 +91,11 @@ I'm currently seeking freelance, remote opportunities as an iOS developer! If yo
- **Day 82:** [_Project 16: QRConnections (Part Four)_](./day-082/)
- **Day 83:** [_Project 16: QRConnections (Part Five)_](./day-083/)
- **Day 84:** [_Project 16: QRConnections (Part Six)_](./day-084/)
- **Day 85:** [_Project 16: QRConnections (Part Seven)_](./day-085/)
</details>
- **Day 85:** [_Project 16: QRConnections (Part Seven)_](./day-085/)
- **Day 86:** [_Project 17: Flashzilla (Part One)_](./day-086/)

BIN
day-086/Projects/Project17Concepts/Resources/paris.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.1 MiB

9
day-086/README.md
View File

@ -32,11 +32,6 @@ From the project description:
My intuition for when to use `@GestureState` vs `@State` when updating the UI via gestures remains a bit tenuous -- but I'm definitely seeing how the former can be useful: `@GestureState` is way of telling SwiftUI that this value can _only_ be mutated during a gesture's `updating` callback. `@State` is much more liberal.
# Code
## Making vibrations with UINotificationFeedbackGenerator and Core Haptics
## Disabling user interactivity with allowsHitTesting()
The concepts project to go along with this day can be found [here](./Projects/Project17Concepts/).