collision-detection
Here are 270 public repositories matching this topic...
-
Updated
Jul 7, 2019 - C
-
Updated
Jun 28, 2020 - C++
-
Updated
Dec 20, 2018
-
Updated
Jun 28, 2020 - C++
-
Updated
Jun 28, 2020 - Java
-
Updated
Jun 24, 2020 - JavaScript
-
Updated
Apr 14, 2020
-
Updated
Oct 15, 2019 - C++
It would be nice to have a crosshair instead of a cursor while aiming for the shot.
-
Updated
Jun 4, 2020 - C++
-
Updated
Mar 8, 2019 - JavaScript
-
Updated
Mar 6, 2018 - C++
-
Updated
Jun 29, 2020 - C++
-
Updated
Apr 30, 2018 - JavaScript
-
Updated
Dec 29, 2015 - JavaScript
-
Updated
Jun 29, 2020 - C
Expected/Desired Behavior or Experience:
User documentation can be generated automatically from each user interface.
Actual Behavior:
Software development is completely separated from user documentation even though user documentation is essentially a spoken language explanation of nothing else but the user experience with a particular user interface. So coders write the program in
-
Updated
Jun 14, 2020 - Go
-
Updated
Sep 8, 2019 - C#
-
Updated
May 28, 2020 - HTML
-
Updated
Apr 27, 2019 - HTML
-
Updated
Nov 14, 2018 - C++
-
Updated
Jun 29, 2020 - Java
-
Updated
Feb 18, 2020 - Haxe
Improve this page
Add a description, image, and links to the collision-detection topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the collision-detection topic, visit your repo's landing page and select "manage topics."


I've been treating tuShorten/tuWiden as a string-ish conversion between UTF16 and UTF 8, so I recommend this.
Here's the code; add it to the end of every tuShorten/tuWiden function.
if (out < (original_out + out_len)) out = 0;