I'd like to get there, I tried. But gitlab escalated "confirmations" of
my identity beyond all acceptable limits. I'm not going to waste more of
my time for that.
So this is not my choice anymore. Irrespective of "benefits" I will not
get dragged into organizations I despise. In this case it's the gitlab.
-R
On 16.06.2025 23:21, 'Seth Hillbrand' via KiCad Developers wrote:
Thanks but without a GitLab report we will be unable to address this.
Please consider that if everyone submitted an issue this way, the team
would be unable to handle any of them.
You may find end users willing to help you with understanding how to use
multi channel tool better at the forum (https://forum.kicad.info
<https://forum.kicad.info>) if you do not wish to register with GitLab.
Seth
KiCad Services Corporation Logo
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.com <https://www.kipro-pcb.com/> [email protected]
<mailto:[email protected]>
On Mon, Jun 16, 2025 at 2:01 PM Rafał Pietrak <[email protected]
<mailto:[email protected]>> wrote:
Hi,
https://www.electric-
sheep.eu/0WPPnXhN8uAVGNnNzGBaIISw6z7U84p7srSE411BTQ.mkv <https://
www.electric-sheep.eu/0WPPnXhN8uAVGNnNzGBaIISw6z7U84p7srSE411BTQ.mkv>.
It's 16MB and I'll leave it there for a couple of days. Regrettably
gitlab refused my registration, so I cannot use proper channel to hand
it over to you. I don't mind handing over the project files, too. Just
tell me it'll help.
no audio there, so pls follow the mouse moves.
I didn't mean "exclude from multi=channel", quite the opposite. My
intention was to suggest "here multi-channel starts" marker at
schematic/sub-schematic level. This comes from the fact, that currently
implemented generation of zones based on sub-schematic creates areas,
which reflect "currently" (that is "random") placement of components -
because it's done before placement replication action. So in my work I
had to re-generate zones after every attempt to replicate their
configuration. Having a single flag at schematic level fixes that.
-R
On 16.06.2025 19:22, 'Seth Hillbrand' via KiCad Developers wrote:
> Hi Rafał,
>
> If there is a case where sub sheets can't find their matches in the
> multichannel tool, this sounds like it might be a bug. Can you
post a
> minimal example to a bug report?
>
> It is not quite clear to me what additional benefit comes from
> specialized markers for 'exclude from multi-channel'. When
creating the
> multi-channel design, you can already pick and choose which rules
areas
> and/or subsheets are included. However, if you could post a
video of
> your process along with what you are trying to achieve to the bug
> tracker, this would be helpful in either fixing the tool or
fixing the
> documentation
>
> Seth
>
> KiCad Services Corporation Logo
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483
> Long Beach, CA
> www.kipro-pcb.com <http://www.kipro-pcb.com> <https://www.kipro-
pcb.com/ <https://www.kipro-pcb.com/>> [email protected]
<mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]>>
>
>
>
> On Sat, Jun 14, 2025 at 10:40 PM Rafał Pietrak <solver@electric-
sheep.eu <mailto:[email protected]>
> <mailto:[email protected] <mailto:solver@electric-
sheep.eu>>> wrote:
>
> Hi all,
>
> For some time now I'm using-and-testing the multichannel
tool. During
> that time I've stumbled upon cases where zone mapping of
identical
> copied of sub-schematics fail to find isomorphism complaining of
> "topological missmatch". But those sub-shcematics ARE identical.
>
> So I was wondering, it it would be prudent and along the
design roadmap
> if the "rules zones" based on subschematics were indicated as
sub-sheet
> marker/flag available just like "exclude from simulation" or
"exclude
> from board" are. An additional flag would be something like: "pin
> rule-zone to schematic" (or "schematic also defines role
zone") and
> replace the "generate rule zone" step of defining area to
replicate.
> Currently this becomes possible, as an option to indicate one
part
> withing sub-sheet, that will "govern the placement and
orientation" of
> replicated zones.
>
> I still haven't worked out how exactly and where in the kicad
code the
> "Generate zone" maps the identity of parts involved in the
bug/failure
> resulting in topological mismatches I've experienced during
> replication.
> I'd appreciate a helping hand in understanding the code.
>
> Regards,
>
> -R
>
> --
> You received this message because you are subscribed to the
Google
> Groups "KiCad Developers" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to [email protected]
<mailto:devlist%[email protected]>
> <mailto:devlist%[email protected]
<mailto:devlist%[email protected]>>.
> To view this discussion visit https://groups.google.com/a/
kicad.org/ <https://groups.google.com/a/kicad.org/>
> d/msgid/devlist/b78ce4e8-6f6a-419a-bcde-948fc9f6ed6b%40electric-
> sheep.eu <http://sheep.eu> <https://groups.google.com/a/
kicad.org/d/msgid/devlist/ <https://groups.google.com/a/kicad.org/d/
msgid/devlist/>
> b78ce4e8-6f6a-419a-bcde-948fc9f6ed6b%40electric-sheep.eu
<http://40electric-sheep.eu>>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "KiCad Developers" group.
> To unsubscribe from this group and stop receiving emails from it,
send
> an email to [email protected]
<mailto:devlist%[email protected]>
> <mailto:[email protected]
<mailto:devlist%[email protected]>>.
> To view this discussion visit https://groups.google.com/a/
kicad.org/d/ <https://groups.google.com/a/kicad.org/d/>
> msgid/devlist/CAFdeG-osU9g9xNdF8Eqjb-gP-
> xDDGSbfWsBYUcnTj82BV5AugA%40mail.gmail.com
<http://40mail.gmail.com> <https://groups.google.com/a/ <https://
groups.google.com/a/>
> kicad.org/d/msgid/devlist/CAFdeG-osU9g9xNdF8Eqjb-gP- <http://
kicad.org/d/msgid/devlist/CAFdeG-osU9g9xNdF8Eqjb-gP->
> xDDGSbfWsBYUcnTj82BV5AugA%40mail.gmail.com
<http://40mail.gmail.com>?
> utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:devlist%[email protected]>.
To view this discussion visit https://groups.google.com/a/kicad.org/
d/msgid/devlist/931a9545-bdca-4c3c-bfb3-d67ad1d84b70%40electric-
sheep.eu <https://groups.google.com/a/kicad.org/d/msgid/
devlist/931a9545-bdca-4c3c-bfb3-d67ad1d84b70%40electric-sheep.eu>.
--
You received this message because you are subscribed to the Google
Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/a/kicad.org/d/
msgid/devlist/CAFdeG-
odPUoQgkgPtshRVe_J1h49msuiV5TEOrrizS9mSfFBig%40mail.gmail.com <https://
groups.google.com/a/kicad.org/d/msgid/devlist/CAFdeG-
odPUoQgkgPtshRVe_J1h49msuiV5TEOrrizS9mSfFBig%40mail.gmail.com?
utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/5bef921d-9ac8-4a71-8324-73daf22f2368%40electric-sheep.eu.
