kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

I don't know what revision, but Jean-Pierre committed my patch for
fixing this on / around 22nd August. Email copies below:

Brian Sidebotham a écrit :
- Hide quoted text -

    Hi Guys,

    Just a really quick patch to fix a libedit regression.

    To repeat:

    Select a component (CMPA) Which will be the basis of a new component.
    Select the edit fields dialog, and edit the value field to effectively
    create a new part (CMPB)
    Save the new edited component, and eeschema will inform you that CMPA
    exists in the library, do you want to modify it?

    The problem stems from not propogating the value field change to the
    name of the component, and the save function uses the name of the
    component instead of the value.

    It's a bit of a grey area I think, but at the moment we need to keep
    the name and value in sync until they are properly separated.

    Attached is a very quick patch to solve the problem, though it might
    be better to do this patch in the OnOk method of the edit fields
    dialog instead.

Thanks.
Fixed, in OnOk method.

-- 
Jean-Pierre CHARRAS


On 21 November 2010 21:49, Marco Mattila <marcom99@xxxxxxxxx> wrote:
> This was changed in revision 2559. The reason was "Fix bug that
> prevented component from being replaced in library when the component
> root name was changed." I don't quite get the point, though. What
> exactly was the bug? Value != component name? Is there something that
> could be done to enable copying components the way Karl described it?
> Or is there another way? Maybe Wayne Stambaugh has some comments?
>
> marco
>
> On Mon, Nov 15, 2010 at 4:43 AM, Karl Schmidt <karl@xxxxxxxxxxxx> wrote:
>> If I go into libedit - open a part and change the Value field - it will
>> Change the value of Value, but won't let me me create it as a new part.
>>
>> It also appears that the cache gets messed up - I see the old name - select
>> it, but get the newly modified lib part. Closing and opening eeschema fixes
>> the cache problem.
>>
>> There used to be a way to modify an existing part and save as a new part.
>> Not sure when this crept in -- 20100909 or earlier?
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>