Take the 595: You can immediately see that there are two 8-bit registers (1D and 2D), bit-connected in parallel, but each with their own control logic (box with narrowed foot on top of each register). Once you know how the IEC symbology works, you don't really need the data sheet any more. The left one is a 74595 serial to parallel latch and the right one is one version of a 74165 parallel to serial one. I attached a couple of often used symbols of mine, familiar to most of you. Or then it is too difficult to bother - easier to just draw a blank box. Its almost like nobody ever heard of IEC and the symbol presentation standard. Elementary gates are shovelheads and all else is blank boxes with nothing whatsoever to indicate the inner workings of the chip. Another pet frustration of mine is the habit of some people in drawing logic components. I tend to have multiple symbols for parts like these, and pick the one that seems most appropriate for the case. Or some other scheme based on what you want to highlight in the schematic. power inputs as one part and each I/O bank into separate parts. You could separate the component into e.g. While there might not be a single right answer for every occasion, some kind of structured approach will beat a mass of undifferentiated pins every time. Is there a way to globally change this to just show the IC as 1 part on my layout? i hope im making sense if not i can probably upload some photos when i get back in the lab to further explain

ie it shows 1 Dip package as three separate 'parts' or what not in the schematic editor. however in Diptrace it places 2 different sections to the IC as well as a separate power and ground section. in eagle's schematic layout when i add a DIP package for say TL072 it actually placed a dip package with all the pins, i prefer it this way. ive only been fiddling around with diptrace the last day or so and it seems to be pretty good however theres one thing that is annoying me. anyway after doing my head in trying to work out eagles ridiculous upgrade paths not to mention the cost i decided to give diptrace a go. Ive been using eagle for a little while and although im able to make layouts etc pretty well i recently found that i was running into problems due to board size (pin count was fine but i just wanted to spread things over a larger area for enclosures and so forth).

Diptrace ru