View Single Post
  #7 (permalink)  
Old 06-05-2008, 02:52 PM
Posts: n/a
Default Re: ANNOUNCE:-- TimingAnalyzer Free Version -- Draw timing diagrams

On Jun 4, 3:44 pm, rickman <[email protected]> wrote:
> On Jun 2, 8:58 am, timinganalyzer <[email protected]> wrote:

> > Hello All,

> > The TimingAnalyzer can be used to quickly and easily draw timing
> > diagrams.
> > Signals, clocks, buses, delays, constraints, and states are easily
> > added
> > from the GUI.

> > It can also be used to quickly do a timing analysis and check for
> > timing faults. Minimum, typical, and worst case analysis can be
> > performed.
> > Delays and constraints are easily specified and changed to see if
> > faster
> > clocks or slower parts can be used without any timing faults.

> > There are 3 editions planned. The Free Edition(FE), the Standard
> > Edition(SE),
> > and the Professional Edition(PE).

> > You can download the Free Edition now and read all about the
> > TimingAnalyzer at:

> >

> > Comments and feedback are welcome at

> > [email protected]

> I spent about 5 minutes working with this program before I gave up.
> My reason is not the problem posted below, but because of the user
> interface decisions made. I don't know why every new program has to
> reinvent something about the user interface. There is a standard call
> Common User Interface (CUI) that is even documented by Microsoft,
> The one big difference that hit me up side my head was the way the
> Cntl key is used counter-intuitively with mouse clicks for
> selections. If you click on one item it is selected. If you click on
> an second item, it is *added* to the selections. To deselect
> something you have to either press the Cntl key while clicking on it
> or you have to use the ESC key. I have *never* seen a program use
> this sort of selection mechanism. I have seen variations on how you
> select multiple, but every other program I have ever worked with, the
> default action of clicking a new thing while an old thing was selected
> was to deselect the first thing and to select the new thing.
> It was more than once that I tried to move some things and ended up
> with a mess because extra moves kept happening. Combine this with the
> lack of a working undo feature and I ended up rather frustrated and
> gave up. I was looking for something that would save me time over a
> program like Visio.
> I suggest that the author get some references on CUI or better yet,
> use some other programs with graphical interfaces and go with the
> flow. It is so much more productive than trying to retrain the
> world... if you don't believe me, just look down at your keyboard. Do
> you think the keyboard layout we all use was a good idea? It's just
> easier to continue to use it than it is to retrain everyone that is
> using it now.
> Rick

Hello Rick,

The goal is to make drawing timing diagrams as easy as possible, and
I do agree about sticking to standard GUI practices, and that should
done for each OS.

The program is in beta testing and I know it's not perfect but don't
forget to look at the big picture. Not only can you draw timing
you can do timing analysis and show margins and find faults in
you can write scripts that automatically draw the diagrams so complex
diagrams can be made with one command, or test vectors or testbenches
be generated with one command. If you need to document simulation
it can read VCD formated files, then you can make annotated timing
diagrams from
simulations and include them in design documentation. With actual
functions you can simulate gates, registers, counters, shift
registers, and
other logic functions which can help when deciding if the logic if
enough or the clocks are to fast.

So, keeping all that in mind, if beta users make valid and
constructive suggestions
for improvements and new features, they will incorporated into the
program. Most all
of them will be added before the final release 1.0.


Reply With Quote