> I would actually like that to be <kbd>Ctrl</kbd>+Click, to match the behavior of Visual Studio and ScriptLab, to name a few.

"Go to definition" was not implemented in Rubberduck, mainly because the functionality is already present in the VBE (<kbd>Shift</kbd>+<kbd>F2</kbd>), but that wasn't taking mouse-based navigation into account... and then there's the technical aspect, too: the VBE's code panes aren't ours, and the IDE is hardly telling us anything about what's going on in there.

Wo

> retailcoder,

Thanks for a timely reply.

CTRL + Click is perhaps a better option. However, I didn't even know this jump (SHIFT + F2) was even possible until you mentioned it, which makes this post entirely worth posting! I'm glad you mentioned that. My life should be easier now...

A mouse based solution would definitely be more intuitive and really look forward to that feature if you guys do end up going down that path.

Thanks again, keep up the great work.

Regards,

> I'm confused by how you "could simulate SHIFT + F2 to another key in Windows to jump faster". Would hitting `F2` be "faster" than `Shift-F2`? Is that what you're after? (Note, remapping `Shift-F2` to just `F2` would be bad, since `F2` is already used to bring up the Object Browser.)

Once you get used to using `Shift-F2` is becomes very quick and natural, and you'll wonder how you ever got along without it.

As a follow up note, if `Shift-F2` takes you to a different code pane (another mo

> We'd really love for you to be able to use Rubberduck, too! Having a copy of Rubberduck's log file would be extremely helpful in helping us identify the issue - it could be a compile error in your code, or there could be an issue with the duck.

To that end, please look at the **Logfile** section of your original post to see the instructions on how to upload the log - i.e., ensure that logging is on and that it's set to TRACE. Recreate the problem, then _edit_ your original post to include t