In CodeRush when I Ctrl+Alt+F to bring up 'jump to file' dialog, the dialog starts hopping around the screen while I type. Sometimes it disappears out of view temporarily, popping back in view as I continue to type.
Edit : the dialog stays in place if I drag it anywhere before typing, so this is my temporary workaround.
Hi Jonathan,
I tried to reproduce the issue based on your description and attached a screencast of my attempts.
Do you see the same (or similar) behavior?
It would be great if you can record a video to demonstrate the issue on your side.
Your example appears reasonably similar. I tried it on my home machine and see the same behavior as I do on my work laptop. I have attached a video recording.
Jonathan,
Thank you for the screencast. There is a setting in CodeRush that should prevent this issue. Please configure the "Jump To" window so it is centered on the screen:
Please let me know if this solution works for you.
Unfortunatelly it doesn't help. I'm able to reproduce it only on 4K monitor with 150% scale. If I setup 100% it works correctly. DPI scale bug?
Tomas, Jonathan,
We discussed this with the team, and concluded that the issue might be related to your monitor layout and settings. Please share with us the following info:
I look forward to hearing from you.
I have two 4K monitors with 150% scale. Switch main monitor (with source code) to 100% scale helps. I tried disconnect the second monitor but it doesn't help. I could make a screencast.
In others words if you switch your main monitor to 150% scale you should be able to reproduce it.
It's definitely related to DPI. If I change to 100%, it no longer hops. The 'centered' setting in CodeRush does not make a difference.
I have two screens:
(left external monitor 1) DPI scale set to 125% @ 2560x1440
(right laptop monitor 2) DPI scale set to 150% @1920 x 1080
(left monitor 1) DPI scale set to 150% @3840x2160
(right monitor 2) DPI scale set to 150% @3840x2160
Thank you guys for all the information. Please give us some time to reproduce this issue.
We reproduced this issue. We will let you know when we fix it.