search

epasveer / seer

Seer - a gui frontend to gdb
GNU General Public License v3.0
2.09k stars 66 forks source link

UI shows infinite spinner which is slightly distracting (possibly a bug?) #154

Closed ell1e closed 10 months ago

ell1e commented 11 months ago

For me, the seer UI shows infinite spinner which is slightly distracting (possibly a bug?):

Screenshot from 2023-09-27 19-23-23

It works fine otherwise, it just won't stop showing that spinner. This is with seergdb 2.2 on OpenSUSE Leap.

epasveer commented 11 months ago

Looks like you may have highlighted some text in the editor. It would attempt show the vaue of the so called "variable". If the variable name isn;t valid, it may just spin. I'll take a look.

ell1e commented 11 months ago

Looks like you may have highlighted some text

I don't think I was at the time, certainly clearing the selection which I tested just now doesn't fix it. But that's super interesting, that this one and #153 are actually related :blush:

Additional note: since I built from source and via the actual git repo via tag (rather than tarball), if you want me to try some fix attempt during the next days, let me know the branch and/or commit and I can do that if that helps. No rush, though.

ell1e commented 11 months ago

For what it's worth, after restarting Seer entirely the spinner went away, but the variables hover still doesn't work. I can enter names manually and press enter into the "Logger", and "Locals" works as well, just the hover in the source code view doesn't at all. Selecting a variable as text causes it to show up in the "Logger" with its value which is a nice workaround I guess, except when I ever even once select some longer text that one blows up the "Name" column of the "Logger" tab so much that I can't see any values anymore. So in overall, looking at values more interactively seems to be somewhat grumpy and is resisting me a little, even though it's sort-of trying its best to work.

ell1e commented 10 months ago

I actually haven't managed to make this happen again with the latest development version, so maybe it was fixed. Maybe it makes the most sense that I close this for now?

epasveer commented 10 months ago

Sure. No problem. It can always be reopened :^)