Blender Add-on --- View3D Navigation Buttons

View3D Navigation Buttons is a Blender add-on that puts buttons on the View 3D's header bar to simplify viewport view changing (e.g. "top" view, "front view", etc.). Specifically, the "blue buttons on the far right are added.

This add-on adds efficiency

• On most laptops, there is no number pad, changing views is cumbersome, usually involving holding down two or more keyboard keys
• On a laptop, I find that most of the time, my left hand is used only for hitting ctrl, alt and shift and escape. Changing views is used a lot, and this add-on provides quick, one-click access to view changes.
• Moving more towards a mouse-only creative methodology is much more practical and realistic

Features

• Top, Front, Right and Camera views are available. Bottom, Left and Back are not common in typical development, so space was saved, not adding buttons for those
• Lock Camera to View is a togglable button
• Set Camera to Active View is a button. This is highly beneficial, since it's functionality has the worst shortcut key combination, ctl-alt-numpad0

Screenshots

See the User Configs section of the wiki for more

Installation

Grab the latest release from GitHub. Or pull this git repository (specifically under /view3d_nav_buttons) Install the add-on, via Blender -> User Preferences -> Add-ons section and click "Install Add-on from File"

Activate the buttons, by going to View -> Navigation Buttons

Documentation

The GitHub Wiki can serve as a central hub for all of documentation, if there is a demand for this add-on, or if such is requested by the public. This has not been done at this time, since Blender has an add-on section on it's website (which might be used). Possible Quick links:

• Install
• Configure
• User Configs
• Frequently Asked Questions

License

This add-on is licensed under the terms of the GPLv3 and BSD licenses.

Contributing

To submit code changes, please open pull requests against the GitHub repository. Patches submitted in issues, email, or elsewhere will likely be ignored. Here's some general guidelines when submitting PRs:

• In your pull request, please:
  • Describe the changes, why they were necessary, etc
  • Describe how the changes affect existing behaviour
  • Describe how you tested and validated your changes
  • Include any relevant screenshots/evidence demonstrating that the changes work and have been tested
• Any new source files should include a GPLv3 license header
• Any contributed code must be GPLv3 licensed