kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #05574
Re: exploiting human readability
On 10/07/2010 08:23 AM, Dick Hollenbeck wrote:
> On 10/07/2010 08:12 AM, Marco Serantoni wrote:
>
>> On Thu, Oct 7, 2010 at 3:40 AM, Dick Hollenbeck <dick@xxxxxxxxxxx
>> <mailto:dick@xxxxxxxxxxx>> wrote:
>>
>>
>> It occurs to me that if you had the assignment operator in place for
>> COMPONENT or copy constructor, you could simply assign to the
>> containing
>> component when seeing an "inherit" token using the base component.
>>
>> (component A
>> (inherit component B GUID)
>> (pin 12 ...)
>> (property NAME VALUE (offset X Y) (orientation 0)(font
>> FONT)(visible NO))
>> )
>>
>> Dick to avoid problems i think we should overload the pins and
>> attributes only and make the graphic part of the component immutable.
>> --
>> Marco
>>
>>
>
> I hadn't found a way to modify inherited graphics in the extending
> component, and no examples have been offered that do so.
>
> It is not an area that I personally am thinking more about, but if
> somebody thinks of one, we may have to come back for your opinion at
> that time.
>
>
> Thanks Marco,
>
> Dick
>
Oops, sorry. I misunderstood you. Are you saying we should not allow
even *additions* ?
If so, why?
References
-
exploiting human readability
From: Dick Hollenbeck, 2010-10-05
-
Re: exploiting human readability
From: Wayne Stambaugh, 2010-10-06
-
Re: exploiting human readability
From: Dick Hollenbeck, 2010-10-06
-
Re: exploiting human readability
From: Wayne Stambaugh, 2010-10-06
-
Re: exploiting human readability
From: Dick Hollenbeck, 2010-10-06
-
Re: exploiting human readability
From: Wayne Stambaugh, 2010-10-06
-
Re: exploiting human readability
From: Dick Hollenbeck, 2010-10-07
-
Re: exploiting human readability
From: Dick Hollenbeck, 2010-10-07
-
Re: exploiting human readability
From: Marco Serantoni, 2010-10-07
-
Re: exploiting human readability
From: Dick Hollenbeck, 2010-10-07