Author Topic: sandila timing diagram stencil  (Read 10037 times)

0 Members and 1 Guest are viewing this topic.


  • Hero Member
  • *****
  • Posts: 1670
sandila timing diagram stencil
« on: May 30, 2014, 08:21:19 AM »
So Paul...just curious ;-) , but

Why wouldn't you make a universal shape to cover most if not all the timing diagram shapes

I.e. something like

Props.pattern = <0000,0011,1100, 1111, etc>

Geometries for all transitions

Gemoetry 1 <sharp low to high>
Geometry 2 <shapr high to low>
Geometry 3 <gradual low to high>
Geometry 4 <gradual high to low>
Geometry 5 <low>
Geometry 6 <high>

user.selectgeo1 = if (props.pattern = 0011, 1,0)
user.selectgeo2 = if (props.pattern = 1100, 1, 0)

Geometry1.noshow = !selectgeo1
Geometry2.noshow = !selectgeo2

Then if somebody wanted write some VBA to create a timing diagram, it would be
   -lay the shapes out
   -plug in the right code per shape

So then could even think about import bit vectors (or modify imported bit vectors) to turn into drawings.

Just curious ;-)

Paul Herber

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3281
    • Paul Herber's website
Re: sandila timing diagram stencil
« Reply #1 on: May 30, 2014, 08:37:37 AM »
Hi Vojo, interesting question. However, I can't see many users wanting to write VBA, and for most timing diagrams the exact location of rising/falling edges is important, well, at least, the relation between rising/falling edges and other events is important.
The shapes I have just click together, then you extend them with the mouse to the required length.
« Last Edit: December 12, 2014, 06:46:56 AM by Paul Herber »
Electronic and Electrical engineering, business and software stencils and applications for Visio -


  • Hero Member
  • *****
  • Posts: 1670
Re: sandila timing diagram stencil
« Reply #2 on: May 30, 2014, 01:08:57 PM »

understand your approach...really more of artist approach (manually making drawings) vs eng approach (foundation for tool chain)

was just curious