I should apologize for the errant bug submission.  It turns out that I
was simply unaware of how to add signals.  However....

Older versions of gtkwave had a nice "add signals" button on the tool
bar.  When trying to figure out how to use this version, I had seen the
"search" options, but I didn't think they were what I wanted, because I
didn't need to search... I knew exactly which signals I wanted to add!
I don't know why the authors decided to hide such a critical option with
such a misleading name.  Considering all of the relatively less
important things on the tool bar, I think some of them could go and be
replaced by the three search options.  And the names should be changed
from "search" to "add by".  I don't "search" for signals.  I "add"
signals, where search is an implicit part of the process of finding
them.

I might also suggest embedding such a critical device in a pane to the
left of where the signal names are shown once they've been added.  And
also, removing signals should be made simpler too.  Older versions with
"add signals" and "cut signals" right there on the tool bar made a lot
more sense.

I suggest leaving this bug here and changing it to a "usability" bug.  I
posted to my mailing list (open graphics) about this, and someone else
pointed out that it had taken him also a while to figure out how to add
signals.  I'm kinda dense sometimes, but I'm not the only one who has
been confused by this program.

-- 
gtkwave shows no signals
https://launchpad.net/bugs/59706

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to