Hi Flowgun,

re:
> * nothing else is selected during creation: no issues - just select the newly created one. this
> doesn't interfere with other cases at all.

But the problem is that it does interfere with things in subtle ways.

Here's a simple scenario - you want to draw in a line with the intention of using it as the cutting object in boolean difference.

But boolean difference doesn't just work on a single selection, it needs 2 separate selections, one for the base objects and then a second selection step where you give it the cutting objects.

If a newly drawn line was selected automatically you now need to do an extra step to deselect it before you can run boolean difference because it needs to be selected as a cutting object not as a base object.

It's just not the case that it would universally be helpful to alter the selection like that.

- Michael

Thank you for the quick reply. this is exactly what I was looking for.

For exiting with selection when nothing is selected, you are right. I didn't think it through well enough.
Boolean difference between a curve and a surface/solid would provide a similar result as a boolean merge. maybe MoI can smartly differentiate between that, or maybe, even better and easier, invert the operations to select the cutter first and then the target object (Blender-Style)? wouldn't that save the sea turtles from snorting all the disregarded mouses due to the extra clicks? I think this can be a bit more streamlined in one way or another, but I guess lots of complexity may arise with multiple objects and so on, so I don't know. I trust your judgment.

I will experiment with both methods and see. I feel that clicking anywhere in the 3d space to deselect and proceed would be faster and more care-free than having to precisely click the created object for selection. This would certainly be faster after arraying on a big surface (better than having to ctrl+shift+click and drag left to right from the right angle).

Thank you for that line of code.

Happy Weekend =)

Hi Flowgun, I'm glad that line of script was helpful!

re:
> or maybe, even better and easier, invert the operations to select the cutter first
> and then the target object (Blender-Style)? wouldn't that save the sea turtles from
> snorting all the disregarded mouses due to the extra clicks?

No, the sea turtles would be upset at that because it would violate one of their design
goals of prioritizing MoI to be easy to use and quick to learn.

One element of that is having commands operate in a consistent manner. In MoI
this is applied by this design rule - commands that modify objects select the object to
be modified first and any supplementary stages after that.

- Michael

UPDATE:

I was able to set up my hotkeys with Autohotkey to be "Spring-loaded", as Adobe calls them.
For me, H is rectangle, J is circle, K is polygon, and L is line (across most Software that I use).
Pressing the key just sends it once. Holding it for more than 200 milliseconds keeps it waiting, and once I release it, it sends the hotkey associated with "Select Last Created Object" Script.

This way, I get the best of both worlds.

It can be done with "Extrude" too. If it's kept held, then it'll send "Delete" after the release, removing the original curves.

The possibilities are endless. It's a matter of preference at this point.

Hope this helps. Cheers.