Thanks for the feedback. I should say up front I'm not a coder. This was made using chatGPT. I'm aware of that issue, and we did spend some time trying to prevent what you describe, but with no luck. Which isn't to say it can't be done. If anyone has an idea how it might be accomplished, I'd love to hear about it. I'd revisit the matter for sure.
As it turns out, no you wont! while Vam doesn't seem to have a plugin-available method to detect when the UI is in use, a strictly geometric solution worked. Where is the UI, where is the pointing ray, do they intersect? If so, disable node selection.
Very good idea!
That's Candy, my current girl. Not the sharpest knife in the drawer, but enthusiastic, and can be talked into just about anything. She's modified from some downloaded look, but damned if I know which one. Which unfortunately means i can't share her, as I don't know the license of the look she's based off of.
D'oh! That's a pretty obvious thing for me to have missed, isn't it. Fixed, gonna update in a second. Thanks for the report.But is it possible to make it work with mouse drag as well?
If you mouse drag your target without selecting it first it uses original VAM selection.
I think you downloaded the new version, but vam was still loading the old one.I am sorry, but it is still doing the same, if there is a yellow atom selected/choosen by VAM then that atom will be dragged, not the one mouse is over
I'm guessing you're having this problem during desktop use? In the plugin UI, there are sliders for Desktop "touch angle" and "hold angle". That's what sets how close you need to be pointing to a node before it gets targeted for selection, and how far away the pointer needs to get before targeting is lost. Currently, the same setting is used for desktop and VR use, but obviously the setting needs to be much lower in desktop. Thank you for pointing this out!
