Mail Archives: geda-user/2015/10/05/09:07:20
--001a113ed84835fd2005215b305b
Content-Type: text/plain; charset=UTF-8
Hi-
I'm a lurker on this list, so I realize that my opinions and suggestions
are probably not important to anyone. Feel free to ignore them. However, I
think that perhaps the features you are discussing here are specific
subsets of a more general feature that many users might find useful.
The feature I'm referring to is what you might call a general selection
filter. The idea is that with a filter applied, only objects matching the
filter criteria can be selected and therefore modified (at least with the
mouse, I imagine that you could still modify anything from the command
interface). With a tool like this, you could specify "silk screen objects"
and "text objects". This would restrict you to being able to modify silk
screen text. You could also specify "not text", or "tracks", or
"components"... etc. to restrict selections to those items.
This is not a feature request on my part, nor is it a request for any
action. I have no idea how hard it would be to implement, or if it's even
possible given how things are structured. It's just an idea that you might
want to consider if you're thinking about changing the features previously
mentioned.
Cheers,
--Chad
On Mon, Oct 5, 2015 at 3:25 AM, Gabriel Paubert (paubert AT iram DOT es) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Sun, Oct 04, 2015 at 03:56:23AM +0200, Kai-Martin Knaak wrote:
> > Markus Hitter wrote:
> >
> > > .. I learned that there are no less than three special modes for
> > > ignoring text, hiding text and/or ignoring anything but text exist.
> >
> > My use cases:
> >
> > 1) "lock names"
> > Many of my SMD symbols have their text placed right in the middle of
> > the silk artwork. This makes it easy to recognize which symbol the
> > text belongs to. I tend to shrink my boards as much as sensible to
> > decrease the cost of production. More often than not this results in
> > not enough open space to put refdes or value outside the footprints.
> > So text inside the footprints is the only way to go, anyway.
> > With the text inside it becomes hard to grab and move a footprint
> > rather than just its text. So I habitually always activate "only
> > names" during placement.
> >
> > BTW, the string "only names" tends to confuse new users at my place.
> > They don't automatically associate a value with a "name". What this
> > flag really is about is "text". In addition, text is not actually
> > locked in place. It will move in parallel with the footprint. The flag
> > is really more an ignore. How about "ignore text"?
> >
> > 2) "only names"
> > Once done with placement and routing I like to add some finishing
> > touches to the silk layer. At this stage I generally don't want to
> > manipulate the position of footprints. So an option to ignore
> > everything but text comes handy.
> >
> > In the same vein as above I propose to rename of this option to read
> > "only text".
> >
> > 3) "hide names"
> > Manual routing of densely populated boards benefits from as little
> > graphical distraction in the main window as possible. Since I let the
> > rats guide me, refdes strings or values are not needed and just
> > clutter the view. Deactivating the silk layer completely is an
> > inferior option because the silk artwork provides valuable hints as to
> > where components are. It would prevent me from moving footprints, too.
>
> I agree with your points but I dislike the new naming, many poor choices
> in PCB may be due to the first author being not being a native english
> speaker (element among them).
>
> In this case, I think that neither "name" nor "text" are good choices, I
> would certainly prefer "silkscreen labels". This is longer, but that's
> the best compromise between consiceness and accuracy I could find.
>
> The fact that the choice of the mode is not reflected on the GUI is also
> annoying, maybe the "only silkscreen labels" and "lock silkscreen
> labels" modes should grey out (paint with less vivid colors) the non
> selectable elements to provide a visual feedback.
>
> > In summary, I am glad all three modes exist. I'd even contemplate to
> > extend the concept. E.g, shift-click a layer button to ignore it for
> > mouse driven actions but still keep it visible.
> >
>
> Gabriel
>
--001a113ed84835fd2005215b305b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div>Hi-<br><br></div>I'm a lurker on this l=
ist, so I realize that my opinions and suggestions are probably not importa=
nt to anyone. Feel free to ignore them. However, I think that perhaps the f=
eatures you are discussing here are specific subsets of a more general feat=
ure that many users might find useful. <br><br></div>The feature I'm re=
ferring to is what you might call a general selection filter. The idea is t=
hat with a filter applied, only objects matching the filter criteria can be=
selected and therefore modified (at least with the mouse, I imagine that y=
ou could still modify anything from the command interface). With a tool lik=
e this, you could specify "silk screen objects" and "text o=
bjects". This would restrict you to being able to modify silk screen t=
ext. You could also specify "not text", or "tracks", or=
"components"... etc. to restrict selections to those items.<br><=
br></div><div>This is not a feature request on my part, nor is it a request=
for any action. I have no idea how hard it would be to implement, or if it=
's even possible given how things are structured. It's just an idea=
that you might want to consider if you're thinking about changing the =
features previously mentioned.<br><br></div><div>Cheers,<br></div><div>--Ch=
ad<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Mon, Oct 5, 2015 at 3:25 AM, Gabriel Paubert (<a href=3D"mailto:paubert=
@iram.es">paubert AT iram DOT es</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com=
">geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mailto:geda-u=
ser AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>></span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h=
5">On Sun, Oct 04, 2015 at 03:56:23AM +0200, Kai-Martin Knaak wrote:<br>
> Markus Hitter wrote:<br>
><br>
> > .. I learned that there are no less than three special modes for<=
br>
> > ignoring text, hiding text and/or ignoring anything but text exis=
t.<br>
><br>
> My use cases:<br>
><br>
> 1) "lock names"<br>
> Many of my SMD symbols have their text placed right in the middle of<b=
r>
> the silk artwork. This makes it easy to recognize which symbol the<br>
> text belongs to. I tend to shrink my boards as much as sensible to<br>
> decrease the cost of production. More often than not this results in<b=
r>
> not enough open space to put refdes or value outside the footprints.<b=
r>
> So text inside the footprints is the only way to go, anyway.<br>
> With the text inside it becomes hard to grab and move a footprint<br>
> rather than just its text. So I habitually always activate "only<=
br>
> names" during placement.<br>
><br>
> BTW, the string "only names" tends to confuse new users at m=
y place.<br>
> They don't automatically associate a value with a "name"=
. What this<br>
> flag really is about is "text". In addition, text is not act=
ually<br>
> locked in place. It will move in parallel with the footprint. The flag=
<br>
> is really more an ignore. How about "ignore text"?<br>
><br>
> 2) "only names"<br>
> Once done with placement and routing I like to add some finishing<br>
> touches to the silk layer. At this stage I generally don't want to=
<br>
> manipulate the position of footprints. So an option to ignore<br>
> everything but text comes handy.<br>
><br>
> In the same vein as above I propose to rename of this option to read<b=
r>
> "only text".<br>
><br>
> 3) "hide names"<br>
> Manual routing of densely populated boards benefits from as little<br>
> graphical distraction in the main window as possible. Since I let the<=
br>
> rats guide me, refdes strings or values are not needed and just<br>
> clutter the view. Deactivating the silk layer completely is an<br>
> inferior option because the silk artwork provides valuable hints as to=
<br>
> where components are. It would prevent me from moving footprints, too.=
<br>
<br>
</div></div>I agree with your points but I dislike the new naming, many poo=
r choices<br>
in PCB may be due to the first author being not being a native english<br>
speaker (element among them).<br>
<br>
In this case, I think that neither "name" nor "text" ar=
e good choices, I<br>
would certainly prefer "silkscreen labels". This is longer, but t=
hat's<br>
the best compromise between consiceness and accuracy I could find.<br>
<br>
The fact that the choice of the mode is not reflected on the GUI is also<br=
>
annoying, maybe the "only silkscreen labels" and "lock silks=
creen<br>
labels" modes should grey out (paint with less vivid colors) the non<b=
r>
selectable elements to provide a visual feedback.<br>
<span class=3D""><br>
> In summary, I am glad all three modes exist. I'd even contemplate =
to<br>
> extend the concept. E.g, shift-click a layer button to ignore it for<b=
r>
> mouse driven actions but still keep it visible.<br>
><br>
<br>
</span>=C2=A0 =C2=A0 Gabriel<br>
</blockquote></div><br></div>
--001a113ed84835fd2005215b305b--
- Raw text -