At 02:17 PM 7/03/02 +1100, you wrote:
>For example, I just wrote a query that selected:
>all pads with holes = 32thou AND
>all components with comment = 4u7 AND
>all fills on the Top Overlay layer.
>(Not useful but it demonstrates my point)
>
>Hit APPLY and all three object types are s
holes that "get away".
> -Original Message-
> From: Dennis Saputelli [mailto:[EMAIL PROTECTED]]
> Sent: 07 March 2002 04:50
> To: Protel EDA Forum
> Subject: Re: [PEDA] Query MAnager
>
>
> this is news to me, thanks for pointing that out
> i will play with it some
this is news to me, thanks for pointing that out
i will play with it some more, but clearly this is a feature which is
more bells than whistles
it reminds me of something dvorak quipped in the recent PC mag:
two old ladies at a restaurant, one said 'this food is inedible' and the
other said 'yes
In Mr. Doyle's example, the "AND" is not acting as a "logical" AND -- it's
an OR, that is, the result is the addition (union) of the selections, not
the intersection.
HOWEVER, I then tried using the same "object type" in multiple selections,
and in that case, it WAS a boolean AND. For example:
gt;
To: Protel EDA Forum <[EMAIL PROTECTED]>
Date: Thursday, 7 March 2002 02:59
Subject: Re: [PEDA] Query MAnager
>On 02:17 PM 3/7/2002 +1100, Linden Doyle wrote:
>
>>Hi All,
>>
>> >
>> >IMHO it would be MUCH more useful if it offered true LOGICAL AND
&
that's right the difference between the common English usage of AND and
the 'logical AND' can be confusing
the common english usage is closer to this 'OR' this etc. just as you
have described
in the case of the query manager the logical OR (plain English AND) is
easy to achieve by other means, a
Hi All,
>
>IMHO it would be MUCH more useful if it offered true LOGICAL AND
>functions instead of the LOGICAL OR functions that it uses
>
Maybe I've got hold of the wrong end of the stick here, but I thought it
already did an "AND" function.
For example, I just wrote a query that selected:
On Wed, 6 Mar 2002, Dwight Harm wrote:
> I've used it occassionally. One thing it can do that global edit can't is
> select by "less than" or "greater than" comparisons,
I also use it to select all nets of a bus, since the sch -> PCB exporter
assigns each bus into a handy class.
> Certainly t
I've used it occassionally. One thing it can do that global edit can't is
select by "less than" or "greater than" comparisons, e.g., for track width
or hole size. Also, the ability to save/name the selection criteria is
handy sometimes. Note, however, that the queries aren't stored with the PCB;
anyone use the query manager/wizard in PCB?
(and found it to be good for anything?)
it doesn't seem to do anything that you can't do just as readily with
global edits
IMHO it would be MUCH more useful if it offered true LOGICAL AND
functions instead of the LOGICAL OR functions that it uses
Denn
11 matches
Mail list logo
