kicad-developers team mailing list archive

["Sergey A. Borshch" <sb-sf@xxxxxxxxxxxxxxxxxxxxx>]

On 17.01.2018 20:49, Jeff Young wrote:
> Hi Wayne,
>
> But even for 6, does this issue warrant it?  Having an expression evaluator would remove the need.
First, I vote for %R and %V to be consistent with footprints.

Secondary, it's not that simple as it seems. Sometimes I change RefDes on 
schematics by double-click on field and entering new value. If it will be a 
substituted text field, RefDes of that particular unit must change accordinary 
after tex field editing done.
> (Mind you, it would still be overkill for this issue if the expression evaluator didn’t have other uses.  That was the reason for my query.)
>
> Cheers,
> Jeff.
>
>
> > On 17 Jan 2018, at 18:31, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> >
> > Jeff,
> >
> > Adding separate field locations for each symbol unit requires a symbol
> > library file format change which is going to happen after v5 is
> > released.  Please do not change any of this code because it will just
> > get replaced when this occurs.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 1/17/2018 12:27 PM, Jeff Young wrote:
> > > There’s a bug[1] that complains that the user can’t reposition a reference or value differently for different units that might be different sizes.  (You can do this on the eeschema canvas, but not in the library, so you have to do it each time you use one of the units.)
> > >
> > > It occurred to me that one could accomplish this using existing stuff if we had a (very simple) evaluator for text fields at runtime.  They could then add a text field to their units (marked shared-between-units or not as required), and set the value to something like “%REF” or “%VALUE”.  The expression evaluator could even be as simple as doing those two replacements, or maybe looking up any field value or something.
> > >
> > > Anyway, I’m not sure this issue warrants it, but if it had other uses it might be worth doing (whereas adding separate REF and VALUE fields per unit and giving them shared-between-units flags, etc., would be more work than this bug probably warrants).
> > >
> > > Thoughts?
> > >
> > > [1] https://bugs.launchpad.net/kicad/+bug/1334502
> > > _______________________________________________
> > > 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
>
>
> _______________________________________________
> 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


--
Regards,
  Sergey A. Borshch            mailto: sb-sf@xxxxxxxxxxxxxxx
    SB ELDI ltd. Riga, Latvia