Restore scrollbar position after refreshing the namespace view in the Variable Explorer

[Chuck321123]

Problem Description

Hi, so I have about 300 objects defined in python, lets say df1 to df300, but i want to see how df200 looks like. I scroll down in the variables explorers tab and open df200. I see that something is off for that specific dataframe and go to my code to change df200 and press f9 on that specific line. Now, I update just 1 variable, but the variable explorer scrolls me all the way back up to the start, which is annoying. I now have to scroll all the way back down (or search) to get back to df200. If i want to change something again with df200, the variable explorer tab updates again and takes me all the way back to the top, in which I have to scroll all the way back down again. A suggestion would be that the explorers tab updates after a code is run, but the explorers tab doesnt scroll back to the top and leaves you where you were so I can access df200 way quicker.

What is the expected output? What do you see instead?

Expected output is that the variable explorer updates the objectives but doesnt scroll you all the way back to the top again.

Versions

• Spyder version: 5.4.5
• Python version: 3.12
• Qt version: 2.4.1
• PyQt version: 5.15.10
• Operating System name/version: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0                             :  1.4.1 (OK)
chardet >=2.0.0                                  :  5.1.0 (OK)
cloudpickle >=0.5.0                              :  2.2.1 (OK)
cookiecutter >=1.6.0                             :  2.1.1 (OK)
diff_match_patch >=20181111                      :  20230430 (OK)
intervaltree >=3.0.2                             :  3.1.0 (OK)
IPython >=7.31.1,<9.0.0,!=8.8.0,!=8.9.0,!=8.10.0 :  8.14.0 (OK)
jedi >=0.17.2,<0.19.0                            :  0.18.2 (OK)
jellyfish >=0.7                                  :  0.9.0 (OK)
jsonschema >=3.2.0                               :  4.17.3 (OK)
keyring >=17.0.0                                 :  23.13.1 (OK)
nbconvert >=4.0                                  :  7.4.0 (OK)
numpydoc >=0.6.0                                 :  1.5.0 (OK)
paramiko >=2.4.0                                 :  3.2.0 (OK)
parso >=0.7.0,<0.9.0                             :  0.8.3 (OK)
pexpect >=4.4.0                                  :  4.8.0 (OK)
pickleshare >=0.4                                :  0.7.5 (OK)
psutil >=5.3                                     :  5.9.0 (OK)
pygments >=2.0                                   :  2.15.1 (OK)
pylint >=2.5.0,<3.0                              :  2.17.4 (OK)
pylint_venv >=2.1.1                              :  3.0.1 (OK)
pyls_spyder >=0.4.0                              :  0.4.0 (OK)
pylsp >=1.7.2,<1.8.0                             :  1.7.3 (OK)
pylsp_black >=1.2.0                              :  1.3.0 (OK)
qdarkstyle >=3.0.2,<3.2.0                        :  3.1 (OK)
qstylizer >=0.2.2                                :  0.2.2 (OK)
qtawesome >=1.2.1                                :  1.2.3 (OK)
qtconsole >=5.4.2,<5.5.0                         :  5.4.3 (OK)
qtpy >=2.1.0                                     :  2.3.1 (OK)
rtree >=0.9.7                                    :  1.0.1 (OK)
setuptools >=49.6.0                              :  67.8.0 (OK)
sphinx >=0.6.6                                   :  7.0.1 (OK)
spyder_kernels >=2.4.3,<2.5.0                    :  2.4.3 (OK)
textdistance >=4.2.0                             :  4.5.0 (OK)
three_merge >=0.1.1                              :  0.1.1 (OK)
watchdog >=0.10.3                                :  3.0.0 (OK)
zmq >=22.1.0                                     :  25.0.2 (OK)

# Optional:
cython >=0.21                                    :  3.0.2 (OK)
matplotlib >=3.0.0                               :  3.7.1 (OK)
numpy >=1.7                                      :  1.24.3 (OK)
pandas >=1.1.1                                   :  2.0.2 (OK)
scipy >=0.17.0                                   :  1.10.1 (OK)
sympy >=0.7.3                                    :  None (NOK)

[ccordoba12]

Hey @Chuck321123, thanks for reporting. I think this is a very good suggestion and we'll try to implement it in a future version.

In the meantime, you can filter variables to only focus on the ones you want to explore by clicking on the find button and entering your variable's name below: