New documentation#215
Merged
Merged
Conversation
Collaborator
Author
|
TODO:
|
9faf8ca to
8787f1f
Compare
8787f1f to
f03fc88
Compare
f03fc88 to
8df77a5
Compare
0233298 to
4ddb0cc
Compare
|
This is a great improvement of the old, rather sparse, documentation. |
Collaborator
Author
|
@PerMalmberg Good to hear, that's exactly what I was going for. |
Collaborator
Author
|
While writing the documentation I noticed the horrible |
|
@FSMaxB I'll take functions instead of macros any day. 👍 |
465ebea to
99c669f
Compare
Collaborator
Author
|
Done! Release 1.7 will probably come tomorrow or as a new years gift. |
20f40c8 to
f2f09ea
Compare
f2f09ea to
1e95363
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this pull request is to rewrite the documentation in a more structured way that can also be somewhat used as a reference to look something up and contains all the gotchas.
Although the current style of "letter to the user" has its appeal, the kind of questions I have been getting over the time and that appeared on StackOverFlow make me think that a different approach should be taken.
Feel free to take a look at this work in progress and give some feedback.