#Scheme 1.7
2 messages in this thread
Barry – no – We stay out of Eplex entirely, currently. Very soon there will
be a change in situation where that will change. in the meantime, my activity
is confined to the forum without any exceptions. Let me address some of your
concerns… (and thanks for bringing them up here…. I like it – there are
so many good thinkers on here it can't do anything but help)
I see that the document is not clear, as you say – I will change it. However,
I would also point out that it does NOT describe moving an object br dragging
it – it says "To drag an object, point at it, etc… In order to sucessfully
move or copy an object using the drag technique, you must be sure that the
object is NOT selected when using drag." (page 14) And on page 5, it says
that copy, move, etc work on marked objects. Drag is a means of marking AND
positioning and object. Forest thru the trees problem, for me – I'll change
it. Thanks.
2- a logic system for overlapping; sure, that would be nice. Do you want to
wait longer for screen re-draws? wires are all dynamically figured at re-draw
time – they don't really exist as items, only endpoints. I don't think it's
practical.
3- same problem, though not unsolvable. Into the 'wish list it goes.
4- copies _do_ deselect, I think; the source stays selected, but the 'copy'
is unselected. 4b- no can do.
5- that could be awful… how about, a requester that says: "Objetcs
off-screen are selected – abort or continue?" But only once? <continued>
An idea! Instead of a requestor that pops up every time an off screen
object would be manipulated by Scheme (oh, boy could that get tedious fast)
use one of the unused boxes in the palette and have it change if an off
screen item is selected. That way the user would know at a glance wether any
surprises lie ahead.
As for wires overlapping and crossing nodes they're not connected
to-well, the way I see it, those are big problems-they affect the clarity and
quality of the Schematic. If the problem with making wires not cross one
another (unless necessary) and avoid nodes is not practical due to the amount
of time needed to calculate with every screen redraw, how about a selective
one? Click a palette option and it does the operation. It would only have to
be done once before plot time, or whenever there was some confusion about
what was done previously.
Another couple of things that you might put on the "wish list" involves
the plot driver. A "wait" command would be nice to stop a plot without
canceling it. Also optional "change pen" commands so wires could be a
different color from the rest of the drawing (ends the, "Is that a loom or a
wire confusion?", in a dense drawing) could prove invaluable. Oh, I made a
.pcnf file to run my MP2000 (it uses HPGL but wouldn't run with the supplied
file-I don't know wether other HPGL plotters have the same problem. I
uploaded the file a while back-if you want to include it on your release disk
feel free to do so.)
I wish I'd known that you hadn't found that bug yet. I would have tried
to document what happened. As I remember it involved making multiple copies
of pads, connecting them with wires, and then moving the pads. I tried last
night and couldn't get it to repeat. Sorry.
Barry
P.S. What kind of monitor do you use? I've done my best to come up with a
"low flicker" color combination but I still need the bottle of Tylenol next
to me if I use it for a couple of hours.