Thanks. This time it worked, but I swear that I tried all kinds of finger dance combinations, including the one you described here and the results always seemed to have some offset distance to them.
I have also noticed that RS sometimes starts behaving oddly and it needs to be closed and started again. Like one time it would render the view quickly, but when it got to the bottom-right last "box" it seemed to calculate something endlessly, even though there was no geometry there. And I am still not used to the two step file save mechanism. I am certain on more than one occasion I changed the name of the file (like from Teacup-Test-1B to Teacup-Test-1C, only to find several saves later that it seemed to never have actually taken the name change and I clobbered the last good save of 1B. It seems I have to change the name in the windows dialog box and click on "Save" in that interface, then I have to also click on "OK" in the next outer RS interface too. I guess I'm not used to having to tell programs twice to save a file before it actually does it. Also a couple times it seemed I did something and the next thing I knew is that the view of my scene was upside down. The one time the last thing I did before this happened was to create a new level (what I tend to think of as a file folder) and I am used to other programs where it automatically assumes you want to name the level/folder and I start typing a name. So maybe it took what I typed as some keyboard shortcut command (which is yet another reason I don't like keyboard shortcuts.) Sometimes when I am writing fiction and furiously typing, some other program will pop-up a box and it takes my typing as an answer to what it was asking, and it does something that I may not have wanted it to do. On 8/1/09, [email protected] <[email protected]> wrote: > Hi. I don't think anyone was upset. ;-) > > I am guessing, but I think that the point Boris was making was that > when using a software regularly, after learning to use it, the > keyboard short cuts are essential for an efficient and productive work > flow. For learning, navigating menues and toolbars could be easier > than to memorise stuff, but not necessarily - having to switch between > different toolbars for performing simple tasks such as snapping to a > point sounds very much annoying to me. > > Returning to the original topic, what is it exactly that you are > trying to do? To move a curve so that the end point is located on a > point of another curve, select the curve, start a move action using > the m-key or the move tool in the Transformation toolbar. Then hold > the comma key and left mouse button down as you drag a rectangle > around the point on the curve you want to move. Then release the left > mouse button, change view if necessary and then hold the comma key and > left mouse button down again as you drag a rectangle over the target > point. > > Regardless of how the views were aligned, the two curves should now > intersect at the last selected point. At least it does when I try it. > I currently have v6, but this has been the same at least since v4.5 if > I am not mistaken. > > -- -- Henry Tjernlund http://www.renderosity.com/mod/gallery/browse.php?username=henrytj http://www.modelmayhem.com/HenryTjernlund http://imdb.com/name/nm2519729/ http://www.myspace.com/henrytj http://henrytj.deviantart.com/
