eeschema: edit/update field values only updates on current page (lp:#1761234)

changed weight to 16

added eeschema prioritywishlist statusconfirmed labels

Maciej Suminski (orsonmmz) wrote:

For the moment it is impossible to create undo entries for changes
affecting multiple sheets. Modifying the update field tool to work on
multiple sheets means we need to sacrifice the undo possibility.

Victor W (vicw) wrote:

Hi,

We'd like to also request this feature. It seems like there already exists
precedent for this feature, in the "Symbol Library References" dialog
(tools->Edit Symbol Library References).

Perhaps you could add the ability to update all symbol fields across a
project in this dialog - where you already note that changes are
irreversible.

This because our workflow sees us store various component specific
information in the symbol, to be used by our prototype and production
manufacturing teams. In order to minimize lead time due to component
shortages or availability, we constantly generate BoMs to ensure most
components are already accounted for prior to the final design being
released for fabrication.

In the event that our manufacturing team realizes that a specific component
is unavailable, we need to do two things; we first update the symbol
reference mapping across the entire project, and then update all the symbol
field values across each sheet.

As it presently stands, we have to do this for each sheet, which is very
time consuming.

We also apply this workflow to avoid schematic capture from blocking
layout. In this case, we often use place holder components.

A simplistic case of this would be for a discrete filter that needs to be
repeated across the project. Once the filter topology has been selected,
and a reasonable filter order has been chosen, we specify place holder
symbols (associated with the correct/reasonable footprints) in lieu of the
actual components we will eventually need to use.

This allows us to immediately start PCB layout for the circuit, while
engineers figure out the specific components or component values required.

Maciej Suminski (orsonmmz) wrote:

The problem here is the undo buffer, which is not shared between sheets.
The field update process may run on the whole project, but then one would
not be able to undo it. There are discussions about solving the separate
undo buffers problem in v6.

Victor W (vicw) wrote:

Kicad does lend itself to git for revision control (which is what we use).

I suppose that what we're suggesting is that, in the interim, it's treated
in a manner similar to the "Symbol Library References" box, where it's made
very clear that you can't undo any changes... Perhaps you could add a
button there, that also updates all the symbol properties.

This would be helpful feature - right now, we have a really horrible macro
to accomplish this task, and the user can't undo the task anyways.

endofexclusive (endofexclusive) wrote:

I was also a bit surprised to find out that the update did not affect the
full schematic but only the current page. Was actually in the process or
preparing a feature request for this, but found out this was already
requested here.

- The feature would be a great improvement of workflow on multi-page
schematics. For example updating a parameter in a capacitor symbol on a
20-page schematic.
- The feature is typically part of a workflow step where the user knows
what he is doing and will expect global changes, and can live with the lack
of undo state. In case something went unexpected or was overlooked, it is
simply reversed with 'git checkout' of the schematic files.

A user workaround for now for simple cases such as text replace could be to
use UNIX sed on all schematic pages.

Jeff Young (jeyjey) wrote:

After 5.0 gets out the door JP and I are going to do 3 rounds in the boxing
ring over this.

We’re both old men, though, so I wouldn’t begin to predict a winner. ;)

Cheers,
Jeff.


> On 21 Jun 2018, at 16:11, endofexclusive <1761234@bugs.launchpad.net>
wrote:
>
> I was also a bit surprised to find out that the update did not affect
> the full schematic but only the current page. Was actually in the
> process or preparing a feature request for this, but found out this was
> already requested here.
>
> - The feature would be a great improvement of workflow on multi-page
schematics. For example updating a parameter in a capacitor symbol on a
20-page schematic.
> - The feature is typically part of a workflow step where the user knows
what he is doing and will expect global changes, and can live with the lack
of undo state. In case something went unexpected or was overlooked, it is
simply reversed with 'git checkout' of the schematic files.
>
> A user workaround for now for simple cases such as text replace could be
> to use UNIX sed on all schematic pages.
>
> --
> You received this bug notification because you are a member of KiCad Bug
> Squad, which is subscribed to KiCad.
> https://bugs.launchpad.net/bugs/1761234
>
> Title:
>  eeschema: edit/update field values only updates on current page
>
> Status in KiCad:
>  Triaged
>
> Bug description:
>  I lived under the impression that update field values should work on
>  the complete design.
>
>  not good, IHMO, as its no option for current page
>  no information about being current page only.
>
>
>  turns out it only works on current page
>
>  Application: kicad
>  Version: (5.0.0-rc2-dev-301-g33f795be4), release build
>  Libraries:
>      wxWidgets 3.0.3
>      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0
nghttp2/1.23.1 librtmp/2.3
>  Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64
bit, Little endian, wxMSW
>  Build Info:
>      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
>      Boost: 1.60.0
>      Curl: 7.54.1
>      Compiler: GCC 7.1.0 with C++ ABI 1011
>
>  Build settings:
>      USE_WX_GRAPHICS_CONTEXT=OFF
>      USE_WX_OVERLAY=OFF
>      KICAD_SCRIPTING=ON
>      KICAD_SCRIPTING_MODULES=ON
>      KICAD_SCRIPTING_WXPYTHON=ON
>      KICAD_SCRIPTING_ACTION_MENU=ON
>      BUILD_GITHUB_PLUGIN=ON
>      KICAD_USE_OCE=ON
>      KICAD_SPICE=ON
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1761234/+subscriptions

Victor W (vicw) wrote:

If you don't mind asking, is there a specific concern associated with
allowing a user to do this? The Symbol Library References tool - which is a
really useful tool - is almost exactly what we need, except it doesn't
actually update symbol parameters or fields across the entire design.

If the concern is that the user may accidentally make an irreversible
mistake, perhaps you could make a back up of all the schematics prior to
running the change?

Victor W (vicw) wrote:

I was wondering whether there was any update on this issue, or if there was
a chance it might move forward? I don't think it's too big of a change, and
it would save a lot of time, especially on large designs.

Jeff Young (jeyjey) wrote:

No update as yet.

Most of the concerns are around undo.  It's unclear whether most users have
a mental model of the whole schematic or each sheet when it comes to undo.

I do want to look at it again for 6.0, but I can't guarantee that JP and I
will come to a consensus. ;)

Nicholas Savenlid (nicholas-z) wrote:

This "bug" torture me almost daily

I hope you can convince JP

Victor W (vicw) wrote:

Hi,

We just experienced an issue that appears to be related to this; when
trying to update footprints, we consistently experienced failures until we
updated every single symbol in our project.

https://bugs.launchpad.net/kicad/+bug/1851574

Given that our design has over 150 sheets, this isn't a particularly good
use of time - though we did write a xmacro for it, it still takes a while
to run across the entire project.

I'm writing this in the hopes of bringing this issue to your attention
again with the hopes it might be resolved.

mentioned in issue #1778 (closed)

added to epic &17 (closed)

marked #4141 (closed) as a duplicate of this issue

marked this issue as related to #4141 (closed)

closed via commit 7340c97e

mentioned in commit benx45h/kicad@a66567f8

changed milestone to %6.0 Feature Freeze

eeschema: edit/update field values only updates on current page (lp:#1761234)

Designs

Child items ...

Activity

eeschema: edit/update field values only updates on current page (lp:#1761234)

Relates to

Activity