| /******************************************************************************* | |
| * Don't Be a Jerk: The Open Source Software License. | |
| * Adapted from: https://github.com/evantahler/Dont-be-a-Jerk | |
| ******************************************************************************* | |
| * _I_ am the software author - JohannesMP on Github. | |
| * _You_ are the user of this software. You might be a _we_, and that's OK! | |
| * | |
| * This is free, open source software. I will never charge you to use, | |
| * license, or obtain this software. Doing so would make me a jerk. | |
| * |
| using UnityEngine; | |
| /// <summary> | |
| /// Small helper class to convert viewport, screen or world positions to canvas space. | |
| /// Only works with screen space canvases. | |
| /// </summary> | |
| /// <example> | |
| /// <code> | |
| /// objectOnCanvasRectTransform.anchoredPosition = specificCanvas.WorldToCanvasPoint(worldspaceTransform.position); | |
| /// </code> |
UPM: How to make a custom package So, Unity has this shiny new package manager, and you have code you want to share between projects - wouldn't it be great if we could bundle up our shared code and plug it into all the projects that need it? Let's figure out how to make our own Package!
Todo
| { | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "name": "Example", | |
| "type": "node", | |
| "request": "launch", | |
| "runtimeExecutable": "node", | |
| "runtimeArgs": ["--nolazy", "-r", "ts-node/register/transpile-only"], |
| //NOTE: This is only a DICTIONARY with MOST character to keycode bindings... it is NOT a working cs file | |
| //ITS USEFUL: when you are reading in your control scheme from a file | |
| //NOTE: some characters SHOULD map to multiple keycodes (but this is impossible) | |
| //since this is a dictionary, only 1 character is bound to 1 keycode | |
| //EX: * from the keyboard will be read the same as * from the keypad... because they produce the same character in a text file | |
| Dictionary<char, KeyCode> chartoKeycode = new Dictionary<char, KeyCode>() | |
| { | |
| //-------------------------LOGICAL mappings------------------------- |
This is a guide for aligning images.
See the full Advanced Markdown doc for more tips and tricks
| // Mixin like functionality | |
| const textInput = props => ` | |
| color: ${props.error ? color.white : color.base}; | |
| background-color: ${props.error ? color.alert : color.white}; | |
| `; | |
| export const Input = styled.input` | |
| ${textInput} | |
| `; |
| Remote profiling can be enabled on Android devices through two different paths : WiFi or ADB. | |
| For WiFi profiling, follow these steps: | |
| Make sure to disable Mobile Data on your Android device. | |
| Connect your Android device to your WiFi network. | |
| Attach your device to your Mac/PC via cable, check the “Development Build” and “Autoconnect Profiler” checkboxes in Unity’s build settings dialog, and hit “Build & Run” in Unity Editor. | |
| When the app launches on the device, open the profiler window in Unity Editor (Window->Profiler) | |
| If the Unity Editor fails to autoconnect to the device, select the appropriate device from the Profiler Window Active Profiler drop down menu. Note: The Android device and host computer (running the Unity Editor) must both be on the same subnet for the device detection to work. | |
| For ADB profiling, follow these steps: |
| using UnityEngine; | |
| /* | |
| Copyright 2016 Max Kaufmann ([email protected]) | |
| Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: | |
| The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. | |
| THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN |
Various 'features' of C++ that show the hacky / inconsistent way in which the language was constructed. This is a work in progress, and currently contains some of the reasons I can remember why I've given up on C++. If you want to contribute, leave your favourite "hack" in the comments.
(in)Visibility: C++ allows changing the access modifier of a virtual function in the derived class. Not only does C++ have no notion of interfaces, it actually allows subclasses to hide methods declared public in the superclass.
Operator over-overloading: One of the increment operators takes a dummy int parameter in order to allow overloading. Can you tell which without googling? (hint: its postfix).
Exception unspecifiers: C++ has two types of exception specifiers: throw() and nothrow. The first is deprecated (because 'we screwed up, sorry, let's forget about this terrible mess'). The second one guarantees it's contract by terminating the application when violated. That's because functions declared
