[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Hierarchy viewer and database proposal

To: geda-user@seul.org
Subject: Re: gEDA-user: Hierarchy viewer and database proposal
From: Bill Cox <bill@viasic.com>
Date: Wed, 22 Oct 2003 10:18:52 -0400
Delivered-to: archiver@seul.org
Delivered-to: geda-user-outgoing@seul.org
Delivered-to: geda-user@seul.org
Delivery-date: Wed, 22 Oct 2003 10:19:39 -0400
In-reply-to: <1066831781.749.168.camel@otilio>
References: <Pine.GSO.4.21.0310211739150.9360-100000@benz.mit.edu> <1066831781.749.168.camel@otilio>
Reply-to: geda-user@seul.org
Sender: owner-geda-user@seul.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

A mixed solution could be that gschem defines "slot" and "numslots"
attributes ONLY for multislotted parts. Then, the DRC backend could
assume (and it could do it only because that definition is automatic)
that parts without those attributes are non-multislotted parts.

This sounds good to me.

Bill

References:
- Re: gEDA-user: Hierarchy viewer and database proposal
  - From: John Doty <jpd@space.mit.edu>
- Re: gEDA-user: Hierarchy viewer and database proposal
  - From: Carlos Nieves Onega <cnieves@iespana.es>

Prev by Author: gEDA-user: Hierarchy question
Next by Author: Re: gEDA-user: Hierarchy question
Previous by thread: Re: gEDA-user: Hierarchy viewer and database proposal
Next by thread: Re: gEDA-user: Hierarchy viewer and database proposal
Index(es):
- Author
- Thread