Something similar: sometimes when I do not hold down the CTRL key, TWS jumps to the class when I click somewhere near the call. I therefore do not think you are crazy.

Now when there are at least 2 of us, it encoureged me to figure out how to reproduce it. I still can not reproduce it on demand, however following scenario almost always gives me this behavior. If I have a couple of classes open (currenlty have also one debug log opened, not sure if it is relevant) and just randomly switch from class to class, there will be eventually one class where TWS behaves like I have CTRL pressed. On every hover over the ClassName for example, it will underline it and change the cursor to the hand (html anchor behavior). If I now click on any line in this class where there is a Class Name (it does not need to be click on the word itself!) he will do the "go to definition".

Exactly what I am facing. But you described it much better!

Hi guys,

Thank you for sharing this issue with us.

We will pay our additional attention to this case and we will look for a reason for this issue.

Also, I want to draw our attention that there is a hot-key assigned to the 'Go to definition' command and this hot-key is 'Cmd+D'. Can this be related to reproducing the issue?

You can change the assigned hot-key to another one and check if the issue is reproduced after this.
To change the hot-key, please use the following steps:

1. please navigate to the menu The Welkin Suite Blaze -> Preferences -> Environment -> Key Bindings;
2. find the 'Go to Definition' command using the search field;
3. in the 'Edit Binding' field at the bottom of the wizard please specify another hot-key, for example, 'Ctrl+G';
4. click Apply and Ok.

Hope this would help, however, if the issue is reproduced after this, we will continue to investigate a reason for this and we will do our best to fix this.

Regards,

Kate

Hi Kate,

No, this could not be the reason for this behaviour. As we said, it happens without touching the keyboard at all. And by the way, for me shourtcut for "Go To definition" is already customized since you introduced this functionality in early versions and it is set to "F12". However, this doesn't work for me either since at least month or two :(

Hi Tomic,

Thank you for your response and for the additional information.

We will take this into account during our investigation.

I will keep you updated on our progress for this and I hope we will find a solution for this issue soon.

Regards,

Kate

Any progress on this one? This is the most anoying bug that drives me crazy. I have just had it in couple of minutes that he jumped to another class. Don't make me go to Developer Console, please. If you have issues reproducing it I am prepared to have a screen sharing session to show you what I/we talk about.

Hi Tomic,

We are looking for the steps to reproduce this, however, we can't seem to find a way to replicate this issue on our side right for right now, so we would appreciate a lot more details on when exactly this happens to you:

• you told us that you don't click on the keyboard at the time when the issue occurs, however, do you make any click by your mouse, or do you just move a cursor?
• also, is the issue reproduced for the same files, or does it apply for random files?

As a possible workaround, you can re-install Microsoft Visual Studio Shell (Isolated), since a core for such behavior can be caused by some internal mechanisms which the IDE uses from IsoShell.
If this acceptable to you, please follow these steps:

1. please uninstall Microsoft Visual Studio Shell (Isolated);

2. after this please uninstall The Welkin Suite IDE;

3. download Microsoft Visual Studio 2013 Shell (Isolated) using this link and install it separately from the IDE;

4. re-download TWS from the site and install it again.

After this, please check if the issue is reproduced.

Looking forward to your response, and any additional information/steps/notes on this issue would be very helpful for us.

Thank you

Kate

I have bought a brand new Laptop with brand new Windows 10 Installation and brand new TWS installation. Issue is still there. In the meantime I have managed to find a way to reproduce the issue every time. It is sufficient to just make a change in the apex class, hit ctrl + B (save/build) and from that moment on TWS behaves like I am holding ctrl all the time. Please note that it does not have anything to do with my Keyboard since I tried 3 different keyboards.

It will soon be 6 months since I reported this bug and can not emphasise more how much this bug drives me crazy and destroys my productivity. I would kindly ask you to invest some more effort in solving this one. I offer you once more my assistance via web meeting or whatever you want me to do. Just please fix this one. 

Thank you

Hi Marco,

Thank you for your feedback.

We will take this into account and we will do our best to solve this.

Also, I've checked the steps which you've provided for a constant reproducing the issue and this doesn't work on our side - in other words, after the provided steps the issue isn't reproduced. So we will continue working to reproduce the issue. 

We included this investigation into the scope of our plans for the nearest several months.

Thank you for your suggestion to make a web meeting on this. I will let you know if/when we are ready for this meeting.

Meantime, may I please clarify with you if you use any Visual Studio extensions in TWS?
If yes, can you please check if the issue is reproduced when you disabled them.

Thank you,

Kate

I don't use any extensions, not that I am aware of. I do have installed Visual studio 2017 Community addition on my machine though. However, I have just installed plain VS and TWS without any additional tools.

Hi Marco,

Thank you for your response.

We are going to investigate if there VS 2017 can influence on reproducing this issue.

Also, @joachim.roesecke, if you don't mind me asking, can you please let us know if you have the installed Visual Studio 2017 Community addition (in the case if you are faced with the issue using TWS on Windows)?

We continue our investigation on this.

I will post updates here when we have any results.

Thank you,

Kate

Hi all

No, I do not have the VS2017 Community Edition installed. Regarding this issue, the situation got better for me over the last months. I cannot say, why.

Regards, Joachim

Hi Joachim,

Thank you for your response.

Also, I'm happy to hear that you can work in the IDE without facing this issue.

Marco, we will continue to reproduce and to investigate this issue and I will keep you updated on our progress on this.

Regards,

Kate

Still very dissapointed that this bug is still unresolved. I am not one of those who complaints all the time for every single little thing, but only for things that significantly deteriorate my experience and/or productivity. This one is by far the most anoying thing that I have experienced in any IDE so far. I can not imagine torturing myself with this any longer so I am forced to look for alternative IDEs on the market.

I'd like to chime in as well. 
For me it was reason to find another IDE, but I don't like those, so please fix this! 

Reproduce:
Windows with TWS, normal SF project, no extensions

• Have a project, edit apex class
• Press CTRL-B (to save it)
• Hover over or click on a class name (without touching ctrl)

You'll see that the ctrl key is stuck and you'll get the control-click behavior 'Go to definition'. Hovering underlines the method and clicking will transport you to the method location. 

Now the Ctrl-click behavior is normal and expected WHEN YOU PRESS CTRL. It is very anoying behavior to see this behavior when you do a deploy. 

It is possible that other ctrl combinations have the same result. 
Left clicking the mouse on an empty spot removes the stuck ctrl. Pressing Ctrl (or any other key combination, I checked) however does not remove this behavior. 

Hello Marco!

Sorry for this late reply, I tried to find new solutions for this issue.

The Welkin Suite for Windows-based on Visual Studio, this would be difficult for us to find a way to avoid this issue. However, we keep tracking the updates for Visual Studio Shell, and, also, we will do our best to find a way to solve this on our side. It is a known issue for Visual Studio.

At this moment, we continue looking for the fix for this issue, but it is not so simple problem to resolve. 

Best Regards,

Ihor

Did I understand it corectly that this issue is isolated on Windows machines with Visual Studio installed? Do you say that if TWS is installed on a machine without Visual Studio problem doesn't exist?

Hi Marco.

I hope you are doing well. Sorry for this late reply.

Yes, you understood me correctly. But at the same time, the uninstalling "Visual Studio" will not solve this problem. We are still looking for the solution for this know issue. I will update you if we find it.

Best Regards,

Ihor