tscircuit community
← Back to community index
# support·Active

astrimid - Can anyone else reproduce this?imp...

Can anyone else reproduce this? code sample As I understand connecting two nets via netlabel is kinda invalid, but shouldn't it complete with error rather than being stuck in SimulationSpiceEngineRender? Took me a while to find an offending line, no errors were shown in error lis

Started by astrimidJul 13, 20265 messages

Discussion

Last active 2 months ago · plain text
astrimidoriginal post
Can anyone else reproduce this? ``` import React from "react" export const TestSources = () => ( <board routingDisabled schMaxTraceDistance={1}> <netlabel net="DC_IN" connection="net.A" anchorSide="left" /> </board> ) ``` As I understand connecting two nets via netlabel is kinda invalid, but shouldn't it complete with error rather than being stuck in `SimulationSpiceEngineRender`? Took me a while to find an offending line, no errors were shown in error list. Only a warning: ``` <trace#3(from:net.A to:net.DC_IN) /> is missing a name. Add a name prop to make the trace easier to identify. ```
image.pngimage.png
Seve
yea we're going to throw on this- i actually "fixed it" but i think it'd be unclear if we allowed connections to be made that way
astrimid
This is what I'd expect when you connect two nets: So it's like a netlabel attached to the network that connects to a trace between two components. So I'm injecting/drawing current from a network to another named network. Currently I see either the label or it hangs.
image.pngimage.pngimage.pngimage.png
astrimid
another way to label a a network, but this more for labeling the current stretch, as I understand, or the continuation on the other page if page number is provided
image.pngimage.png
Seve
we might introduce a `<nettie />` but i don't think that what's youre talking about here

Want to add to the conversation?

Reply in Discord so your notes stay connected to the source.
Continue in Discord ↗