kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #38402
Re: Has the handling of the datasheet field changed again?
Fixes have been pushed. Let me know if they don’t solve the issue….
Cheers,
Jeff.
> On 22 Nov 2018, at 18:09, Jeff Young <jeff@xxxxxxxxx> wrote:
>
> “Just saving in .dcm file” was how I meant it to work, but it is indeed buggy. Fixes on the way….
>
>> On 21 Nov 2018, at 18:46, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>
>> On 11/21/2018 1:17 PM, Rene Pöschl wrote:
>>> On 21/11/2018 18:38, Jeff Young wrote:
>>>>> Version 5.0.x (and version 4.0.x) gave us the option to store the
>>>>> datasheets for both
>>>>> aliases and main symbols in the dcm file.
>>>> Right; that hasn’t changed. What’s changed (or should have changed)
>>>> is that the above is the *only* option.
>>>>
>>>> So is it not OK for that to be the only option, or is it just not
>>>> working that way?
>>>>
>>>> (Sorry for not testing it myself, but I’m knee-deep in the
>>>> paste-symbol-twice-revert crash bug.)
>>>
>>> We just need a way to set the datasheet stuff in the dcm file for non
>>> aliases. Right now there is only one input field that stores it in the
>>> lib file.
>>>
>>> One option that comes to mind is that the current layout of one entry
>>> field is kept. But that there is some setting that controls if it is
>>> stored in the dcm or lib file. (If we simply say that the current entry
>>> field saves to the dcm file someone who currently uses only the lib file
>>> field will be unhappy.)
>>>
>>
>> This is the subtle issue here. If you created a symbol with no aliases,
>> no root description, and no root keywords then it might be prudent to
>> save the datasheet text in the datasheet field in the library file which
>> would result in an empty dcm file. Any other condition should result in
>> the root symbol datasheet text being saved in the dcm file. My
>> preference would be to just save it in the dcm file since this will be
>> the only option when the new symbol file format is implemented.
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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
References
-
Has the handling of the datasheet field changed again?
From: Rene Pöschl, 2018-11-20
-
Re: Has the handling of the datasheet field changed again?
From: Wayne Stambaugh, 2018-11-20
-
Re: Has the handling of the datasheet field changed again?
From: Jeff Young, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Wayne Stambaugh, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Jeff Young, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Rene Pöschl, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Jeff Young, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Rene Pöschl, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Wayne Stambaugh, 2018-11-21
-
Re: Has the handling of the datasheet field changed again?
From: Jeff Young, 2018-11-22