CompuServe Messages

#Scheme 1.7

    03-Jun-88 01:22:30
Sb: #127717-#Scheme 1.7
Fm: Ben Blish 72667,1341
To: Barry Massoni 73260,1413
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>