|
Sounds like you've got a bad UI problem there.
?
Andy
|
Raise your hand if you feel changing hotkeys was anything short of a dumb idea.
?
It's been said before too.
?
Andy
|
IMO, it is odd that Stretching the rectangle's corner marker is ineffective.? It must involve drawing a lasso around it first, or nothing happens.? That is not intuitive.? Consider improving this.
?
Andy
|
Well, the message seems to be an executive
order, not to be disobeyed. Perhaps it could be re-worded, like
'If your question is about a specific schematic, it can't be
answered unless you upload the schematic (.ASC file) for
examination. If it is not about a specific schematic, press POST
again'
On 2025-03-10 18:07, mstokowski via
groups.io wrote:
On Mon, Mar 10, 2025 at 06:12 AM, John Woodgate wrote:
So I tried. You can't use
the word 'schematic' in a question without uploading a
schematic! This is not sensible. I worked round it by
writing 'circuit diagram' instead. Three cheers for
British English!
On 2025-03-10 12:56, John
Woodgate wrote:
Thanks, Tony. I will
try.
On 2025-03-10 12:50, Tony Casey
wrote:
You have to
start a discussion and title it "Feature Request, or
similar.
--
Regards,Tony
?
?
As
someone who has to often ask for schematics, I wish that this
was the case. :-) Actually, when you create any Engineer Zone
post with LTspice as the product, as soon as you click Post, a
pop-up appears asking for any related files — i.e. schematics,
symbols, etc — since the vase majority of cases require one
for debugging. Obviously, feature requests like this, do not.
When you close that pop-up, it does not reappear, assuming you
got the message. It is only a message, not a hard stop, though
it looks like one. You do not need to remove instances of
“schematic”, simply click Post again. Essentially, that is
what you did, but you also changed your post to read “circuit
diagram”.
?
mike
-
Michael Stokowski
LTspice Team
Analog Devices Inc.
--
OOO - Own Opinions only
If something is true:
* as far as we know - it's science
*for certain - it's mathematics
*unquestionably - it's religion
|
On Mon, Mar 10, 2025 at 05:00 AM, John Woodgate wrote:
.... I have to print to .JPG, ...
I don't have a Windows driver to print to JPG.? I can print to PDF, and can go from there to a JPG or GIF or PNG but it's cumbersome.
?
I forgot to mention that I always use a white background on my LTspice screen (light grey for the schematic screen).? I never liked the default black background for waveforms, so it is the first thing I change whenever installing LTspice.
?
Andy
?
|
I wrote:
Sounds like you've got a bad UI problem there.
Sorry, I forgot to provide context.? I was referring to the UI of ADI's Engineer Zone, making it appear as if a new message post could not be completed without a schematic.? Requiring to click "post" after clicking "post" seems counter-intuitive.
?
Andy
?
|
Now I have it the other way round, white for
schematics (so they print out that way), and light grey for
waveforms to get better colour contrast. I'd like the default
colours to nearly follow the resistor colour code, but with
black as 10, pink as 11 and cyan as 12, so I've set it up that
way.
On 2025-03-10 18:49, Andy I via
groups.io wrote:
On Mon, Mar 10, 2025 at 05:00 AM, John Woodgate wrote:
.... I have to print to
.JPG, ...
I don't have a Windows driver to print to JPG.? I can print to
PDF, and can go from there to a JPG or GIF or PNG but it's
cumbersome.
?
I forgot to mention that I always use a white background on
my LTspice screen (light grey for the schematic screen).? I
never liked the default black background for waveforms, so it is
the first thing I change whenever installing LTspice.
?
Andy
?
--
OOO - Own Opinions only
If something is true:
* as far as we know - it's science
*for certain - it's mathematics
*unquestionably - it's religion
|
On Mon, Mar 10, 2025 at 03:01 PM, John Woodgate wrote:
I'd like the default colours to nearly follow the resistor colour code, ...
That is essentially what I used too.? But I diverged somewhat from the resistor colour code sequence to make them more visible.??It is interesting that you use a light grey background for better contrast.? I should try that.? Thanks for the tip.
?
but with black as 10, pink as 11 and cyan as 12, so I've set it up that way.
Does this mean you re-use black?? Or are they different shades for 1 and 10?
?
?
|
On Mon, Mar 10, 2025 at 11:57 AM, Andy I wrote:
Sounds like you've got a bad UI problem there.
Sorry, I forgot to provide context.? I was referring to the UI of ADI's Engineer Zone, making it appear as if a new message post could not be completed without a schematic.? Requiring to click "post" after clicking "post" seems counter-intuitive.
?
Andy
?
Agreed. Apparently, hard to do it “the right way” because EZ has to serve 1000s of products that are not software, and those not-software products steer the ship. Believe me, I've tried to improve the Q&A posting interface to accommodate LTspice. Not giving up.
--
Michael Stokowski
LTspice Team
Analog Devices Inc.
|
On Mon, Mar 10, 2025 at 11:25 AM, Andy I wrote:
IMO, it is odd that Stretching the rectangle's corner marker is ineffective.? It must involve drawing a lasso around it first, or nothing happens.? That is not intuitive.? Consider improving this.
?
Andy
Considered and done! Actually, no change needed, you can already do this by clicking an anchor, or node, or component—no lasso required.
?
Apologies for this oversight in my instructions.
?
mike
--
Michael Stokowski
LTspice Team
Analog Devices Inc.
|
On Mon, Mar 10, 2025 at 03:36 PM, mstokowski wrote:
On Mon, Mar 10, 2025 at 11:25 AM, Andy I wrote:
IMO, it is odd that Stretching the rectangle's corner marker is ineffective.? It must involve drawing a lasso around it first, or nothing happens.? That is not intuitive.? Consider improving this.
?
Andy
Considered and done! Actually, no change needed, you can already do this by clicking an anchor, or node, or component—no lasso required.
On older versions, that did not work.? Attempting to "Drag" (old name for "Stretch") the exact corner without drawing the lasso first,?would Move the whole rectangle.
?
Andy
?
|
IIRC, Black represents 0 on resistors. (Colour blind, but not
_that_ colour blind!)
My favourite R was Brn-Blk-Orn
Donald.
On 3/10/25 15:17, Andy I via groups.io
wrote:
toggle quoted message
Show quoted text
On Mon, Mar 10, 2025 at 03:01 PM, John Woodgate wrote:
I'd like the default
colours to nearly follow the resistor colour code, ...
That is essentially what I used too.? But I diverged somewhat
from the resistor colour code sequence to make them more
visible.??It is interesting that you use a light grey background
for better contrast.? I should try that.? Thanks for the tip.
?
but with black as 10,
pink as 11 and cyan as 12, so I've set it up that way.
Does this mean you re-use black?? Or are they different shades
for 1 and 10?
?
?
|
Yes, that's why I wrote 'near'. For colouring
traces, there is no use for '0', so it comes in useful for '10',
and the other two colours are fairly easy to generate in the
Settings.
On 2025-03-10 20:25, Donald H Locker
via groups.io wrote:
IIRC, Black represents 0 on resistors. (Colour blind, but not
_that_ colour blind!)
My favourite R was Brn-Blk-Orn
Donald.
On 3/10/25 15:17, Andy I via
groups.io wrote:
On Mon, Mar 10, 2025 at 03:01 PM, John Woodgate wrote:
I'd like the default
colours to nearly follow the resistor colour code, ...
That is essentially what I used too.? But I diverged
somewhat from the resistor colour code sequence to make them
more visible.??It is interesting that you use a light grey
background for better contrast.? I should try that.? Thanks
for the tip.
?
but with black as 10,
pink as 11 and cyan as 12, so I've set it up that way.
Does this mean you re-use black?? Or are they different shades
for 1 and 10?
?
?
--
OOO - Own Opinions only
If something is true:
* as far as we know - it's science
*for certain - it's mathematics
*unquestionably - it's religion
|
I am sorry.? In my waveform colour scheme, I used the resistor colour codes, but offset by 1.? Thus "Trace V(1)" was Black, "Trace V(2)" Brown, etc.? I had become completely accustomed to Black being the first waveform, the same way that it was the first resistor colour, even though 0 ≠ 1.? I didn't mind that the numbers were offset, as much as just having them in sequence.? Maybe I should reconsider that.
?
More important than that - to me, anyway - is getting enough contrast to be visible.
?
Andy
?
|
A few days ago, John Woodgate wrote:
2. Drawing a wire with CTRL held down doesn't allow the wire to start and end off-grid. It's the same if I draw lines instead of wires. I can't find a 'Snap to grid' check box to untick.
After some thought, I think that you never could use the CTRL key, nor anything else, to make a wire not snap-to-grid.? I think wires and components can only snap-to-grid.
?
Reading the Help instructions:
The graphical annotations to the schematic; lines, rectangles, circles, and arcs; snap by default to the same grid as the used for electrical contacts of wires and pins. Hold down the control key while positioning these to defeat this snap.
This is the only place I found where it talks about not snapping-to-grid, and note that it applies ONLY to lines, rectangles, circles, and arcs.? It does not apply to Wires. ?Note the distinction between Wires and Lines.? Lines (right-click < Draw > Line) are non-functional, whereas Wires (F3, or the "Wire" toolbar button) make electrical connections. ?I think the conclusion is that holding down CTRL never worked for drawing wires off-grid.? For wires, CTRL only toggles whether they can be drawn at an angle.
?
It makes sense to me that Wires could never be made off-grid, because it could be challenging to connect anything to the off-grid end of a wire.? The schematic editor uses integers for location, and grid points are every 16 integer values - which means there are 15 chances to get it wrong and miss the end of a wire that is not on-grid.
?
You can hand-edit your .asc schematic file and move a wire's starting or ending points, making them off-grid.? It works.? Once in the schematic file, LTspice accepts it and leaves it off-grid when saved again.
?
|
That's a good clarification. Thanks. Andy.
On 2025-03-10 20:55, Andy I via
groups.io wrote:
A few days ago, John Woodgate wrote:
2. Drawing a wire with
CTRL held down doesn't allow the wire to start and end
off-grid. It's the same if I draw lines instead of wires.
I can't find a 'Snap to grid' check box to untick.
After some thought, I think that you never could use the CTRL
key, nor anything else, to make a wire not snap-to-grid.? I
think wires and components can only snap-to-grid.
?
Reading the Help instructions:
The graphical
annotations to the schematic; lines, rectangles,
circles, and arcs; snap by default to the same grid as
the used for electrical contacts of wires and pins. Hold
down the control key while positioning these to defeat
this snap.
This is the only place I
found where it talks about not snapping-to-grid, and note
that it applies ONLY to lines, rectangles,
circles, and arcs.? It does not apply to Wires.
?Note the distinction between Wires
and Lines.? Lines
(right-click < Draw > Line) are non-functional,
whereas Wires (F3, or the "Wire" toolbar button) make electrical connections. ?I think the conclusion is that holding
down CTRL never worked for drawing wires off-grid.? For
wires, CTRL only toggles whether they can be drawn at an
angle.
?
It makes sense to me that Wires could never be made off-grid,
because it could be challenging to connect anything to the
off-grid end of a wire.? The schematic editor uses integers for
location, and grid points are every 16 integer values - which
means there are 15 chances to get it wrong and miss the end of a
wire that is not on-grid.
?
You can hand-edit your .asc schematic file and move a wire's
starting or ending points, making them off-grid.? It works.?
Once in the schematic file, LTspice accepts it and leaves it
off-grid when saved again.
?
--
OOO - Own Opinions only
If something is true:
* as far as we know - it's science
*for certain - it's mathematics
*unquestionably - it's religion
|
On Mon, Mar 10, 2025 at 01:36 PM, mstokowski wrote:
Considered and done! Actually, no change needed, you can already do this by clicking an anchor, or node, or component—no lasso required.
?
Yes, a click on a rectangles corner anchor does allow stretching directly, but the click target is so very small that often the user clicks on one of the sides instead and then the operation becomes a move rather than a stretch, or the click isn't recognized at all.
?
Clicking on a side of the rectangle displays two anchor circles on opposite corners of the rectangle. It seems to me that any click inside the radius of those circles should act like a click on the corner of the rectangle and begin the stretch operation.?
?
As it is now, it is too finicky to be reliable so users have started to use the lasso operation to select the corner instead of a click. Hence all the reports saying this is required.
|
I don't know if this was brought up...but I still can't see a schematic grid.
I haven't been able to view the grid for many versions of LTspice.
I use a light grey background but it doesn't seem to matter.
Basically, the grid switch and color does nothing.
?
I'm sometimes use a 4K 65" sony TV as monitor.
|
On Tue, Mar 11, 2025 at 08:46 AM, Dennis wrote:
Yes, a click on a rectangles corner anchor does allow stretching directly, but the click target is so very small that often the user clicks on one of the sides instead and then the operation becomes a move rather than a stretch, or the click isn't recognized at all.
?
Clicking on a side of the rectangle displays two anchor circles on opposite corners of the rectangle. It seems to me that any click inside the radius of those circles should act like a click on the corner of the rectangle and begin the stretch operation.?
?
As it is now, it is too finicky to be reliable so users have started to use the lasso operation to select the corner instead of a click. Hence all the reports saying this is required.
?
That might be the problem.
A drag operation shouldn't turn into a move operation.
If a drag operation has been selected, a click anywhere on the edge of a rectangle should drag the edge of the rectangle and its intersecting edges..
If a drag operation has been selected, a lasso should be required to drag intersecting edges of a rectangle.
?
Just my opinion.
?
|
On Tue, Mar 11, 2025 at 09:11 AM, eetech00 wrote:
On Tue, Mar 11, 2025 at 08:46 AM, Dennis wrote:
Yes, a click on a rectangles corner anchor does allow stretching directly, but the click target is so very small that often the user clicks on one of the sides instead and then the operation becomes a move rather than a stretch, or the click isn't recognized at all.
?
Clicking on a side of the rectangle displays two anchor circles on opposite corners of the rectangle. It seems to me that any click inside the radius of those circles should act like a click on the corner of the rectangle and begin the stretch operation.?
?
As it is now, it is too finicky to be reliable so users have started to use the lasso operation to select the corner instead of a click. Hence all the reports saying this is required.
?
That might be the problem.
A drag operation shouldn't turn into a move operation.
If a drag operation has been selected, a click anywhere on the edge of a rectangle should drag the edge of the rectangle and its intersecting edges..
If a drag operation has been selected, a lasso should be required to drag intersecting edges of a rectangle.
?
Just my opinion.
?
?
By the way, I'm referring to the operation in LTspice 24.1.5
?
|
John Woodgate