Silly resistor values

Yes, John, you usually are just that. In this instance absolutely so.

When you print ANY pdf, the print job is a fully rendered bit map type print job. No fonts are passed, no fonts are referenced. The entire print job is a bit mapped graphic, and when you view it, it is as well.

That is why it supports zooming up to 4500%. Not that an idiot like you could ever figure out that continued zooming on non-bit mapped renderings results in jpeg jaggies. That will NEVER happen on a zoom of a PDF. Yet one more reason why they are better for so many things document related.

Even if they stop Reader from crashing, it's still pig-slow spyware.

And CutePDF generates PDF files so fast that, at first, you think it's not working. It is.

I do use Adobe Reader, maybe a couple of times a year, when I have to fill out a PDF form that Foxit doesn't like. But it's too big a dog for everyday use.

John

I have a lot of stuff that CutePDF won't print. I've found that PDFCreator is much better. I too use Foxit, but it is ugly.

I'll be happy with the price. There are only two of us doing any hardware design and I know *I* won't be using a '741. ;-)

Sure, that's obvious but it still doesn't solve the schematic problem. They want schematics for service to use[*]. We're experimenting with "graying" (yellow, actually) out sections not implemented but it's manual and quite labor intensive. The other problem we ran into was that to select any component under the "fill" it has to be removed. The fill will be selected first. [*] I'm fighting this one.

As long as the layout tool doesn't barf on the '.' why would care about the reference designator? It's just used for humans.

What about more than 100 components? We already have numbers as high as 12xx, since we use the first two characters to signify schematic page (and some pages already have more than 100 resistors and capacitors, so get two).

I prefer paper for reference. The tube often is used for searching the layout though.

etc.,

faster

they're

At that point back-annotating loses it's importance. We don't back annotate reference designators; not sure why.

switches

understand

how to

question

of

up the

drawn so

as if it

the

That's how

major

No

to

block

or

(pcie,

You do it now, or does the connector exist on all 16 sheets?

Yes.

If you hold down the tab key while you click, Capture will cycle through overlapping objects?

What would you prefer your services guys to use, out of curiosity? (Since you said you were fighting the effort for them to have schematics like this?)

---Joel

No good reason, just some PCB layout guys (mainly the older ones...) seem to freak out if you want to start doing something that they haven't been exposed to previously. :-)

Not sure, but I'll try it. I've had this trouble before with notes.

They have all the documentation and there are already assembly drawings for every SKU. Some features just aren't on some units. The schematic represents the "max" implementation, though that never gets built (conflicting components).

That's what netlists are for.

Not so. If the original artwork was vector graphics, it's in the .pdf as vector. Witness the ease with which pdftoedit will pull .dxf out of .pdfs containing original vector material.

Example: Jim Thompson's .pdf drawings ;-)

Makes sense, too. Much smaller files.

Yep. Marginally smaller file size than PNG, significantly smaller than GIF or JPG, MUCH better readability.

...Jim Thompson

s/pdftoedit/pstoedit

-- "Electricity is of two kinds, positive and negative. The difference is, I presume, that one comes a little more expensive, but is more durable; the other is a cheaper thing, but the moths get into it." (Stephen Leacock)

Theoretically infinite scalability - just math.

Only as long as the source material is all vector.

...Jim Thompson

True.

The print jobs are bit mapped graphics, just like I said. That is how it is compiled, and sent to the printer.

I think that's (partially) up to the printer driver? -- Since a Windows app is still calling DrawLine/DrawEllipse/etc. when it's printing (as well as DrawBitmap), the printer driver can just forward the vector graphics information onto the printer if the printer knows how to rasterize ("rip") vector graphics itself... and I'm under the impression that many "high end" (office) printers do it this way.