Quote:

It wasn't ignorance on your part. RB really didn't do those things before. PG just read your mind and made it happen. They're that good!





heheheh.
"and THAT is how the legend of Robin Hood began..."

Regarding Eddie's original post:
There's probably no need to do that because one a onesy basis, when somebody requests a feature that already exists, somebody will reply with a detailed explanation of how to do what the person wanted to do.

Often people post workarounds that aren't exactly the same feature, but which get similar results.

Most of us have done the same thing as you. It's part of the learning curve. It's also due to the challenges inherent to the task of making documentation. The person who makes the docs may not describe the feature the way you do, so you don't find what you're looking for in the table of contents and therefore you assume it doesn't exist.

Some of us are lobbying for a user-updatable online manual so ALL features are fully documented, and so they are referenced by more than one keyword (do you search for "PIANO ROLL EDITING" under P or E? In a user maintained document, eventually it would be hyperlinked to both keywords.


https://www.dropbox.com/sh/ey71h8ep047758h/AAC12jNM0Hz9Q8zsh5iDeqNHa?dl=0