-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outline exporer items auto expands to follow cursor position in latest 4.x #13896
Comments
Thanks @jnsebgosselin for checking into this with the latest changes done! @ccordoba12 @andfoy what do you guys think? |
I think we can add an option to disable cursor following on the editor |
Is auto-expanding the outline explorer's item to actively follow the cursor position something that was requested by the users? |
I migrated that function since it was already on the tests and on the previous codebase |
Also, I think it makes sense to actively navigate the symbols while the editor cursor is moved |
Ah ok, so you can activate/disable it as you whish? It is just a matter of exposing it in the UI? If that is the case, that would be great then. Because the way I'm using the Outline explorer in my workflow, the new behaviour is a real deal breaker for me. |
Yes, don't worry, I can add an option on PR #13885 |
Thanks! 👍 |
Also, this is only a suggestion, but in order to preserve UX experience across the 4.x series, I would disable the auto-follow/auto-expand feature by default. Just to clarify, before the changes, the cursor position was reflected in the outline explorer down to the lowest visible item in the tree. The tree would not get auto-expended though. The animation below show the previous behaviour: |
I think we should preserve the behavior @andfoy added of automatically following the cursor (I find it more useful), but with an option to revert back to the previous behavior. |
That is ok, I think it really depends how and for what you use the outline explorer. I use it to navigate between files and class/methods within a file. So if I end up with the items expanded automatically, it becomes impossible to do that, especially if the variables and attributes are shown, since this adds a lot of clutter to the explorer. |
Ok, glad you agreed with my idea! |
I would have personally tried to preserve UX consistency in the 4.x series and introduce the new behaviour as default in spyder 5 instead, but that is not a big deal really, especially since you are adding an option. I'm happy with that. |
I agree with @jnsebgosselin , the auto-expand does not look like an improvement for me, and it makes sense not to change the UX in a minor update if it's a change that some users will like and some won't. Just to iterate what he said, the issue is not so much that the outline explorer follows the cursor, but that it expands everything. If the outline explorer would follow the cursor but not expand anything, or it would auto-collapse what it auto-expanded after you move out, it would in my opinion be much less of an issue. |
This was fixed by #13885 by adding an option that prevents following the cursor, so users need to expand the tree automatically.
Unfortunately, it seems that the Outline is broken if we leave that option deactivated (especially if there are cells in the file). So it was my decision to leave it on by default. |
What do you mean by "broken"? What is broken exactly. That would help me to know this in my testings. |
If you have at least one cell in the file, the Outline will appear with its tree collapsed by that cell and it doesn't display any other content. |
Problem Description
After PR #13109, the outline explorer is expanded automatically to follow where the cursor is in the editor. I think this is a UX regression to what was done in PR #7962.
I think that it is ok that the highlight in the Outline explorer follows the cursor position if the item is already visible, but it should not expand items automatically. That is why we have the
Go to cursor position
button.Versions
The text was updated successfully, but these errors were encountered: