GTKWave

I just tried running 2.24.33 (using LD_LIBRARY_PATH tricks verified by ldd) on Linux/X11 and didn't see any problems.  It sounds either rendering back end or platform-specfic. -Tony On Tuesday, February...

It's still effectively going to be invisible if the timescale is set to ps and the sim clock is in ns, etc because nobody is ever going to zoom in...

Extending the range shouldn't have any negative effects.  Values maintain their value until changed and we're a long way away from the max time value. -Tony Message ID: ***@***.***>

You can put changes for fontname_signals/waves in your .gtkwaverc file or do it at the command line like this: 534:/home/bybell/gtkwave/code/gtkwave3-gtk3/src> gtkwave ../examples/des.gtkw --rcvar 'fontname_signals Monospace 12' --rcvar 'fontname_waves Monospace 12'...

3.3.68 is almost 5 years old. Is that from a distribution or just a download you have on your computer? I'll look at dynamic font size changes at some point....

You can try something like this using rc vars: gtkwave des.gtkw --rcvar 'fontname_signals Monospace 8' --rcvar 'fontname_waves Monospace 8' -Tony On Saturday, November 14, 2020, 01:09:27 AM EST, Jose Tejada...

What system are you on? (OS, gtk version, X11 vs wayland, etc) The same size for both should work fine. It's been that way since 1998 so I can curious...

That's weird. I wonder if Pango on your system has different attributes for the ascent/descent line for whatever font it maps to Monospace. See attached screen grabs from my system....

See if you can experiment with size numbers like this: gtkwave whatever.vcd --rcvar 'fontname_signals Monospace 20' --rcvar 'fontname_waves Monospace 18' -Tony On Thursday, September 8, 2022, 10:41:23 AM EDT, Vasant...

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND       2822 bybell    20   0 3431056   2.5g  35676 S   0.0 16.4   0:40.82 gtkwave                      ...that's what I see on my...