On 11/24/2016 11:37 AM, TJoseph Powderly wrote > i find myself zooming and panning between different areas a lot > and opting to use an intermediate value of zoom where the text is barely > legible, just so i get a larger scope This is an issue with this type of schematic. It is a balancing act of making the component and text large enough that it is legible and small enough that it does not take up a full sheet with one component. The current PDF that I sent is meant to be an 11x 17 page size. When printed it is legible however pin names are pretty small and may not be readable by those with older eyes ( I am quickly joining this group). > i ran into the same problem using gEDA , you may be using something > easier to scale than a pdf, maybe SVG. The pan and zoom facilities in the application work pretty well when using a scroll wheel mouse making it easy to navigate the design layout pretty quickly. > I'd like beziers for edges/nets too (like Gene) but more important is > the ability to convey an idea I found the beziers on rockhopper to be more confusing that the horizontal and vertical lines I am used to on P&ID's and electrical schematics. That is why I decided to go with this type of signal routing. YMMV. > there are some ways around the scope/scale issue that you allude to, the > use of sheets/pages > are you thinking along those lines? Yes I plan on using separate design sheets in a future release of this application. Esentially this design layout has the entire configuration on one sheet. With the future version it will split the design based on the individual signal to pin connections used in the individual hal files. So there will be as many sheets as there are hal files. > are these component objects automatically drawn or from a palette/library? The component object are automatically drawn and component definition includes the pins that are listed for the component by the halcmd show command. All of the pins are included in the component however, only the connected pins are drawn.
Thanks, Jim ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
