Thanks for your honest review. Can you explain more about not being able to set the editor font? My tests show that as working. Make sure to "Save Configuration..." to make things permanent.
Also, for the "show variable value on hover", I'll test it.
Can you (or others) create an issue on my github page for any bugs or feature requests?
Hmm, that is a very long time to suffer the side effects. The information leaflets often say to discontinue much sooner.
Well, if your doctor was okay with it, then who are internet strangers to judge? If you had the usual non-tolerance GI problems (more frequent than in 1 in 10 patients), I can only admire the perseverance. It takes a lot of self-care from keeping close to a toilet to hydration.
My wife had this problem when she started metformin. After 2 weeks of diarrhea she tried a different approach, she purposely skipped her medication every other day for a week. The she gradually started taking it every day. The problems went away over night. Her doctor was baffled which is…funny.
I think some drugs are more easily tolerated by the body if they are gradually introduced.
Seer has the concept of 'projects'. A project can hold many settings, including breakpoints, watchpoints, etc... It is a manual thing so save a project and load a project. Not sure what you mean by 'automatically load'.
Seer has a visualizer to view a struct and expand it, updating after each step/next.
A recent change (in the project's github "main") now has struct visualization in the Variable Logger, Tracker, and Local Variables views. All expandable.
The StructVisualizer can follow *pointers. The default method is to view the struct/class that is pointed at in the same visualizer.
You can RMB click on the pointer in the StructVisualizer to open a second visualizer for that pointer.
I know this is a bit aways from how DDD worked. DDD has a nice way of "graphing" the struct/class tree, including any referenced struct/class that come from pointers.
Not sure HN is the best forum for debugging such issues, but nevertheless, here goes:
# lsb_release -a
Ubuntu 20.04.5 LTS
# qmake --version
QMake version 3.1
Using Qt version 5.12.8 in /usr/lib/x86_64-linux-gnu
# qmake-qt5 --version
qmake-qt5: command not found
# apt-file search qmake-qt5
qt5-qmake-bin: /usr/share/man/man1/qmake-qt5.1.gz
# /usr/lib/qt5/bin/qmake --version
QMake version 3.1
Using Qt version 5.12.8 in /usr/lib/x86_64-linux-gnu
I don't recall doing anything special to install Qt on my box, likely something along the lines of:
# apt-get install qt5-default
So in all likelihood, I have the standard Qt5 that comes with Ubuntu 20.04.5, still a somewhat popular and widely used Ubuntu version.
In other news, I tried compiling it on a server that runs a recent version of Ubuntu (22.04) and it does compile and seem to compile and link against Qt 5.15.3
Standard and traditional Qt type headaches, where between many different major versions and deprecated stuff and newly introduced APIs between minor versions, compiling and linking software that relies on Qt is a complete crapshoot.
Also, since you don't provide statically linked binary releases or a flatpak or an appimage, you might want to consider making the source dependencies of your software explicit in the Readme (like e.g. the minimum version of Qt5 required, or the qt5Charts dev libs, definitely not something everyone has installed on their computer).
