Worth noting that, in most modern production, the "stepped object"
is the reticle field, and that is what's architected out of the "die
payload". Then you step -that-. The foundry usually (and always,
when multiproject) create…
I haven't seen much from Tracy since he got a "straight
job" quite a while back. I think he may pop in sparsely.
Sending him a message here might percolate at least
a notification to his "home" email.
My involvement with this …
I do notice that on my layouts, a text will "drive" the display
extent (so probably all computed extents) but will only do
so as far as the origin sits. Not the displayed width of the text.
Everything outboard of the origin (subject to dis…
Another suggestion which might work, is that I've seen that
the "Shapes Library" has a TEXT primitive PCell. I have not
really dug into that, but since it's probably all Python-y in
its guts perhaps it plays nice with scripting and could b…
Just on the off chance that you haven't jumped up to humor
me just yet, here is another stab at "masked selection" (sorta)
which might solve the "stuff gets moved for being selected by
mistake".
That is, in the instance propert…
Not sure about DRC, but there is "a thing" about the default text
font not scaling (the others all do). You might want to look at
asserting one of the other fonts, as a start?
I made my own layertables from paper sources, to
save as .lyp - this is essential in any case, if you mean
to keep working in a consistent environment. There you
can add the human readable names if you like.
I use the Technology just to make them e…
OK, that's understandable I guess.
Let me suggest some things.
Seems to me that whatever sits there looking at
keyboard & mouse, could be told to yip something
out to a logfile every time it finds a "terminator"
(valid command is …
That's what I was thinking, but the question was how to, in Python.
Did you find that command-series? Or just did it interactive?
I'll repeat a recent question, which is: "Is there a logfile which shows
applied commands in sequence, perhaps ev…
I imagine the first step is to see what the foundry would put
out from a "colored" layout that went all the way to mask fab.
What you find in that GDS / OASIS file ought to inform you
of the end outcome desired, how it's represented.
But …
How about
1) Make a deck that fails everything, but reports every fail's
measured number and coords to a log file
2) clean and sort that log file by the measurement value
3) inspect the little end.
Somewhere in the Settings, there are options for what is
shown in the layer window.
You might also want to look at "Technologies" to make
the layers config you like, "stick".
Bindkey would be fine - I'm habituated to 'a' (add@point), 'shift-a'
(area-drag), 'ctrl-a' (deselect@point). Still not used to there being
alt- option to key bindings but that would be a fine place to start
(and maybe build out some of the other no…
I have had another thought regarding the selection / selectability
problem where multiple candidates exist at a location.
How about generating a list of "all presently-selectable-@"
and pop a checkbox-form, only in the case of multiple
…
Worth asking the OP, whether they are set up with a
touchpad or other input device, that recognizes
"taps" / "strokes" / "gestures", one of which might be
called as "right-click" by the device driver - all …
Another "how to skin it" notion - could there be a scheme where DRC
markers can be wholesale put into a top-level instance (like DRC_Err)
placed properly in relation to the topcell (maybe the two, are placed in
a holding view independen…
I think the interest (which I share) was to find a "location -> list_entry"
method, complementary to the "list_entry -> location" (pan-to).
Because sometimes you just want to know "what's THAT?".
Now here's ano…
Perhaps this is more a job for the DRC deck-creator, to add
"switches" which enable / disable "classes" of DRC (like,
I might see latchup rules enabled separately from plain
polygon width / space / nest / avoid, and so on).
It …
I sometimes see "unintended selection" on hover and never
know why, how to not, or whether to expect. Not unique to
this application.
But I'd suggest that if this is a known behavior, there must be
known triggers and maybe a known "h…
Does the error browser let you pick the error and see (and/or
pan-to, zoom-to) the specific error?
Is there an independent "zoom to" menu or key-binding, that
would accept a copy-paste coords pair from said browser
window?
Is there a fa…
Not based on any knowledge, but wonder whether a marker shape
has a property associated, that points back to something? Do you
see anything besides coords, if you select and "q"?
This makes me think that a "mapping" of every menu-tree button
to a Python and a Ruby code-snippet (one line maybe, for native?)
would be a valuable resource. Or maybe it exists already and is
not as obvious as could be.
I am also observing that with a 1.0u snap grid I am still
getting placements of box and polygon vertices on 0.05 grid.
Subsequent modifications snap -by- grid but not -to- grid.
It would be preferable (to me) for vertices to obey main grid.
If thi…
(Quote)
I wonder if there's a way to make an instance, with a text underneath, that takes its size and value from instance properties? Yeah, more instance select-collisions. But at least full-extent-selectable. Too bad I know nothing about how (say)…
(Quote)
If you are busy creating layout art, infix bindkeys are -much- more efficient than leaving the active window to traverse menus and then find your way back to where you wanted to be and do the additional coords-click. I'd say about 4:1 best c…
(Quote)
Yes, the proiblem is unintentional point-selection, or too many options from one point. That is what I used to use the instance-box for in all my own layouts. It creates the "handle" just where I say, and I can ensure that there is…