Increasingly (multiple times an hour), I am seeing more of my tool-clicks result in Deep Selection transformation of the mouse pointer. It doesn't matter on what tool I press.

I also am increasingly seeing multiple times a day a"Feature not yet implemented" notice in the tools area when I click on tools.

Also, sometimes, the backtick key doesn't release the last used tool back to the select mode. So, I end up neurotically back-ticking when I realize that I've been dropping multiple lines or circles or whatever was last selected. At this point, i realize that shift and control do not work and hence the wrong tools are being selected since my shortcuts using uppercase letters fail to work.

[[[Tim, if ever there is an example of why we need multi-letter shortcuts, this is one that feels like a fid or spike through my heart. I have GOT to have multi-letter shortcuts. They are much more intuitive. I could be able to assign a shortcut a letter from the beginning of each word in a command if it is a multi-workd command, or the first few letters of a single-word command. It is becoming more painful to take my eyes off the geometry to find a tool that is pretty to look at but difficult to recall by a single letter. It worsens when I cannot assign a logical memory-jog to a command and am out of keys and have to delete keys and mentally un-map them when I know someday I'll regrete unassigning that key in order to reassign a letter to a tool I'm using frequently for a period. Shortcuts in upper case should only be called upon if somehow someone has managed to deplete all the permutations of letters (excluding non-spoken symbols) in a 3- or 4-letter shortcut.]]]

I previously thought it might be VCP alone or a combination of VCP and VirtualBox and system or app calls getting miscommunicated. What is frustrating is that while intently focusing on geometry, i can miss these two errors. I end up clicking on geometry expecting that my pointer is doing to select, and when it doesn't I fly off the handle. I don't know what it is. I don't suspect worms or trojans or such since I don't let windows 7 touch the Internet (well, one or two times, but months ago, and only for maybe 1 minute or two), and I've disabled the VBox networking/bridge features so windows can only see local shares.

Sometimes, the only way to get out of the frozen lower-case/frozen last-command-used state is to pull down the VBox menu and then dismiss it. I don't know why that works and why it is necessary other than to say it was not a problem before VCP 7 as far as I recall. I previously commented that I had to menu-jaunt back into Linux, but I was mistaken. Now, it's only necessary to expose and dismiss any VirtualBox menu.

Hmmm...

This problem resumed this weekend, but not just with the "Deep Select" feature. It also happened with several other tools on the first click when it happens. It's getting to be enough incidents that I am double-clicking the tool I want just to make sure IT activates rather than seeing "Sorry, this feature not yet implemented" showing up.

When it is not Deep Select, it sometimes is one of the lines tools. When that happens, the pointer disappears and VC7P is apparently less responsive because the cursor is not in a mode that a visible tool appears. It delays zooming for some reason, maybe because the cursor mode "gravity" effect is thrown off.

Also, it annoyingly turns out that when this happens, the tool last selected or invoked and used no longer is so, and the two opposed arrows appear if I press the mouse wheel. It appears as if the tool mode switches as if I want to zoom in and inspect some geometry immediately after releasing that tool last used. I *****ABSOLUTELY****** do not want the app "thinking" that I find it useful to go into a zoom mode at random. I will invoke it myself.

(I got so angry I slammed my fist into my desk and numbed my hand because in one aftertoon it had become enough, that and the 10 hours I spent fixing 3 twisted or non-compliant curves that didn't import behaved like the some 300 other lines that were behaved. That issued was that swept surfaces would not thicken unless I segmented the sweep path curve. Mind-bogglingly depressing that I spent SO much time. Not faulting VC7P, since it might have been how I created the line in Delftship and Freeship. But it would be nice if VC/Shark would do a deep analysis of lines/curves to immediatly re-color those that definitely will fail a sweep/extrude thickness test. It would save users enormous amounts of time. And, avert a swollen fish.)