Set external links to open with target="_blank" for benefit of chm

* Without this, the chm viewer attempts to open the external link in its
  own windows. With some ancient IE6 monstrosity. Ouch.
This commit is contained in:
baldurk
2016-05-16 20:01:17 +02:00
parent e8f76b35c0
commit 8890233fe0
9 changed files with 161 additions and 35 deletions
+11 -3
View File
@@ -27,7 +27,11 @@ All of the good names were taken :-(.
Who can I contact about bugs, feature requests, other queries?
--------------------------------------------------------------
At the moment there's just me at the wheel - feel free to `contact me <mailto:baldurk@baldurk.org?subject=RenderDoc%20feedback>`__ if you have anything you'd like to ask or suggest. I use a `github repository <https://github.com/baldurk/renderdoc>`__ for tracking bugs and feature requests so that's the best place to file an issue.
.. |github_link| raw:: html
<a href="https://github.com/baldurk/renderdoc" target="_blank">github repository</a>
At the moment there's just me at the wheel - feel free to `contact me <mailto:baldurk@baldurk.org?subject=RenderDoc%20feedback>`__ if you have anything you'd like to ask or suggest. I use a |github_link| for tracking bugs and feature requests so that's the best place to file an issue.
I work on RenderDoc in my spare time but I am happy to help with anything and work with you if you have any issues that need attention.
@@ -74,7 +78,7 @@ RenderDoc also uses TCP and UDP ports ``39920`` for remote replay connections, f
Where can I get the source to RenderDoc?
----------------------------------------
RenderDoc is licensed under the MIT license and the source is available on `github <https://github.com/baldurk/renderdoc>`__.
RenderDoc is licensed under the MIT license and the source is available on |github_link|.
What are the requirements for RenderDoc?
----------------------------------------
@@ -174,7 +178,11 @@ In addition to those:
Querying an ``ID3D11Device`` for UUID ``{A7AA6116-9C8D-4BBA-9083-B4D816B71B78}`` will return an ``IUnknown*`` and ``S_OK`` when RenderDoc is present.
`GL_EXT_debug_tool <https://renderdoc.org/debug_tool.txt>`_ is implemented on RenderDoc, which is an extension I've proposed for this purpose (identifying when and which tool is injected in your program). It allows you to query for the presence name and type of a debug tool that's currently hooked. At the time of writing only RenderDoc implements this as I've only just proposed the extension publicly, but in future you can use the queries described in that spec.
.. |debug_tool_link| raw:: html
<a href="https://renderdoc.org/debug_tool.txt" target="_blank">GL_EXT_debug_tool</a>
|debug_tool_link| is implemented on RenderDoc, which is an extension I've proposed for this purpose (identifying when and which tool is injected in your program). It allows you to query for the presence name and type of a debug tool that's currently hooked. At the time of writing only RenderDoc implements this as I've only just proposed the extension publicly, but in future you can use the queries described in that spec.
.. note::