representing connections with a dot in VISIO

[Eric Anderson]

Is there any EASY way to show a schematic in Visio with a wire
connecting with a dot and not connecting by just passing over the wire?

I have used Visio for drawing schematics many times in the past. I
have always been frustrated with the Visio way of drawing single wire
connections. The convention Visio uses is like the old schematics from
the middle of the 20th century. That is, all wires NOT connected are
shown with the wire jumping (bridging/hopping) over the wire. A
connection is shown when the wire crosses straight over the wire. Is
there any EASY way to show a schematic with a wire connecting with a
dot and not connecting by just passing over the wire as a real modern
schematic is generated? I once "created" a dot to put on a connected
intersection, but I felt that it complicated my effort.

Note that I draw schematics about once a year or so, so I don't need a
cad package.

 

[Joe Soap]

Is there any EASY way to show a schematic in Visio with a wire
connecting with a dot and not connecting by just passing over the wire?

I have used Visio for drawing schematics many times in the past. I
have always been frustrated with the Visio way of drawing single wire
connections. The convention Visio uses is like the old schematics from
the middle of the 20th century. That is, all wires NOT connected are
shown with the wire jumping (bridging/hopping) over the wire. A
connection is shown when the wire crosses straight over the wire. Is
there any EASY way to show a schematic with a wire connecting with a
dot and not connecting by just passing over the wire as a real modern
schematic is generated? I once "created" a dot to put on a connected
intersection, but I felt that it complicated my effort.

Note that I draw schematics about once a year or so, so I don't need a
cad package.

Properly drawn circuit diagrams do not need dots on junctions, crosspoints
should never be linked. Offset the junctions as recommended by published
drawing standards, and the problem goes away.

 

[Nico Coesel]

Is there any EASY way to show a schematic in Visio with a wire
connecting with a dot and not connecting by just passing over the wire?

I have used Visio for drawing schematics many times in the past. I
have always been frustrated with the Visio way of drawing single wire
connections. The convention Visio uses is like the old schematics from
the middle of the 20th century. That is, all wires NOT connected are
shown with the wire jumping (bridging/hopping) over the wire. A
connection is shown when the wire crosses straight over the wire. Is
there any EASY way to show a schematic with a wire connecting with a
dot and not connecting by just passing over the wire as a real modern
schematic is generated? I once "created" a dot to put on a connected
intersection, but I felt that it complicated my effort.

Note that I draw schematics about once a year or so, so I don't need a
cad package.

I always use the circular line end (under the pull-down menu with the
arrows) as a dot.

 

[Jim Thompson]

I always use the circular line end (under the pull-down menu with the
arrows) as a dot.

What's the point of drawing a schematic with a graphics program if you
can't netlist it?

...Jim Thompson

 

[Eric Anderson]

That looks like it will work. Don't know why it never ocurred to me.
If I have a question, I will get back.

Thanks,
Eric

 

[Nico Coesel]

What's the point of drawing a schematic with a graphics program if you
can't netlist it?

I use Visio to draw diagrams for documentation purposes. The output
from Visio just looks prettier than the output from most CAD packages
especially when imported into a Word document.

 

[mc]

I made my own Visio schematic package.

For the connecting dot, I think what you want is a circle centered on two
INVISIBLE crossed lines. As I recall, lines can be invisible. Store this
as a Visio shape, and you're done.

 

[mc]

What's the point of drawing a schematic with a graphics program if you

can't netlist it?

Better visual appearance for publication.

 

[Eric Anderson]

mc,

Your idea seems interesting about using the crossed invisible lines
with a dot at the intersection. I am just getting into Viseo in depth,
so please bare with me. I assume that the lines are used to "glue" the
dot to the intersections of another line intersection. I am not sure
how that works unless you set the glue option to "glue to the shape
geometry". How do you set that option? Can you explain the concept
you are using to make the dot stay with the line intersection you set
it on?

 

[JeffM]

Please don't top-post
http://66.102.9.104/search?q=cache:...+remove-*-*-*-irrelevant+STOP+zz-zz+qq+BOTTOM

I am just getting into Viseo

Is that produced by the folks who produce Visio?

so please bare with me

I'm pretty sure Michael isn't into that.
(He might be willing to BEAR with you.)

I have never seen a program
more poorly suited to making electrical diagrams than Visio.

 

[Paul Hovnanian P.E.]

[snip]

I have never seen a program
more poorly suited to making electrical diagrams than Visio.

That can't be true! I always see engineering job descriptions requiring
Word/PowerPoint/Visio experience.

 

[Michael A. Terrell]

[snip]

I have never seen a program
more poorly suited to making electrical diagrams than Visio.

That can't be true! I always see engineering job descriptions requiring
Word/PowerPoint/Visio experience.

Gee, the head of engineering at Microdyne asked me that question when
I was inteviewing for an opening as a component engineer, not long
before he was fired for being a total screwup.


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida

 

[Eric Anderson]

Well folks, sorry about the english. I was about to be out of the door
and rushed it a bit.

It may be that Visio is not the best solution, but it is a compromise
since it is a general tool (sort of like Excel being used for a
database). A Cad program takes some time to learn and an engineer may
be responsible for the design, sketching, documentation, testing,
releasing, production startup, and product support. I have found that
the average design cycle (for stuff I have done) is about 18 months
(some 3 yrs, some 8 months). It is hard to be an expert in a Cad
program that you use intensely for about 3 to 6 weeks out of 18 months.
That is why I always thought you should have a designer do the Cad
stuff. He is much more of an expert than the engineer because he lives
with it every day.

So-o-o-o. I like Visio since it is a nice general tool in my toolbox
(like Word, Project, Excel, Photoshop, Micrografix Designer, Outlook,
and several others). I don't need a netlist (it might be nice and I
understand that earlier versions had one of sorts), but it is really a
sketchpad. Thirty years ago I used an engineering pad and a set of
small drafting tools. Visio is that for me today.

[snip]

I have never seen a program
more poorly suited to making electrical diagrams than Visio.

That can't be true! I always see engineering job descriptions requiring
Word/PowerPoint/Visio experience.

Gee, the head of engineering at Microdyne asked me that question when
I was inteviewing for an opening as a component engineer, not long
before he was fired for being a total screwup.


--
Service to my country? Been there, Done that, and I've got my DD214 to
prove it.
Member of DAV #85.

Michael A. Terrell
Central Florida

 

[JeffM]

Eric Anderson TOP-POSTED:

It may be that Visio is not the best solution...

Again, PLEASE DON'T TOP-POST.
http://66.102.9.104/search?q=cache:...+remove-*-*-*-irrelevant+STOP+zz-zz+qq+BOTTOM

 

[Paul Hovnanian P.E.]

Well folks, sorry about the english. I was about to be out of the door
and rushed it a bit.

It may be that Visio is not the best solution, but it is a compromise
since it is a general tool (sort of like Excel being used for a
database). A Cad program takes some time to learn and an engineer may
be responsible for the design, sketching, documentation, testing,
releasing, production startup, and product support. I have found that
the average design cycle (for stuff I have done) is about 18 months
(some 3 yrs, some 8 months). It is hard to be an expert in a Cad
program that you use intensely for about 3 to 6 weeks out of 18 months.
That is why I always thought you should have a designer do the Cad
stuff. He is much more of an expert than the engineer because he lives
with it every day.

So-o-o-o. I like Visio since it is a nice general tool in my toolbox
(like Word, Project, Excel, Photoshop, Micrografix Designer, Outlook,
and several others). I don't need a netlist (it might be nice and I
understand that earlier versions had one of sorts), but it is really a
sketchpad. Thirty years ago I used an engineering pad and a set of
small drafting tools. Visio is that for me today.

I still use a pad of paper for sketches.

This thread is a classic example of people getting sucked into the
feature-itis of most applications. How do you draw a dot at the
intersection of two lines? If that's not trivially easy to figure out
from the menus or help system, too much time is being wasted on a non
domain specific application. Time probably better spent learning an app.
specific to ones profession.