title: IntelliJ IDEA back/forward with mouse
body: <p>I want to move back/forward between editor tabs, using the two additional ("virtual") mouse buttons I have (<a href="http://www.razerzone.com/gaming-mice/razer-deathadder-black/">RAZER DEATHADDER BLACK</a>).</p>
  
  <p>In Eclipse it's possible by default.</p>
  
  <p>In IDEA I go to <code>File</code>-><code>Settings</code>-><code>Keymap</code>-><code>Main menu</code>-><code>Window</code>-><code>Editor Tabs</code>.<br/>
  There I have <code>Select Next Tab</code> with the deault <code>Alt+Right</code> shortcut.</p>
  
  <p>Then I open the <code>Add Mouse Shortcut</code>.<br/>
  In that dialog I try to assign the <code>back</code> button of my mouse but without success. <strong>It doesn't react at all.</strong></p>
  
  <p>Anyway, googling a bit I've found <a href="http://youtrack.jetbrains.com/issue/IDEA-76787">this</a> thread. I quote <code>Alexey Gopachenko</code> which seems to be an employee of IntelliJ:</p>
  
  <blockquote>
    <p>As stated above - we can't support buttons if JDK on your platform
    does not support them - and obviously it does not.</p>
  </blockquote>
  
  <p>Anyway, that is totally wrong. My platform does support these keys - I actually work with them, on the same platform, on Eclipse and any other app, so it's IDEA who ignores them.</p>
  
  <p>I'd appriciate a solution - how do I assign these back/forward mouse buttons?</p>
  
  <p><strong>UPDATE #1</strong>
  I've found out that <strong>IDEA uses its own JAVA distribution</strong> (<code>C:\Program Files (x86)\JetBrains\IntelliJ IDEA 11.1.4\jre</code> on Windows 7), instead of the system's one - WHY?!<br/>
  I'm almost SURE that is the reason I cannot use extended mouse buttons.<br/>
  I've tried to trick IDEA by creating a custom Windows shortcut. Didn't work. I've also tried to create a SYMLINK in windows to my other, system-wide JRE distribution. Didn't work as well.<br/>
  If someone come up with an idea on how to make it work with the system's JRE instead of its own - I think that'd solve the issue.</p>
  
  <p><strong>UPDATE #2</strong>
  The above update #1 is not the issue.</p>