Problems with grab handles in 2018

I have a recurring but intermittent issue with grab handles not functioning correctly, particularly on callouts with a pointer - see image below:

The problem seems to most frequent with the handles marked 1 and 3, which should allow you to resize the base width of the pointer, but also occurs with handle 1 which should allow you to move the tip of the pointe. Mostly that's what happens but often, no matter how careful I am about correctly selecting the grab handle, they fail to perform as expected. Instead, all three act as if the crosshair tool was active, and the entire callout moves. I am forced to give up and accept the base width and tip placement as they are.

"I have seen issues myself off and on. What happens when I encounter it is that the mouse pointer needs to be some distance offset from where I am trying to grab."

﻿YES! Exactly. I thought I was going mad.Have you also had the one where the cursor is offset from the text position, so you backspace and the 2nd character back disappears instead of the last one? And when you type you have a similar offset?

I did some testing based on Paul's image and memories of past issues using these callouts.

In Paul's image. # 1 places the top pointer control directly over a callout boundary control handle.

Here's something that created a lot of the problems when I tried to grab a callouts Pointer Handles and the Outside Boundaries of the callout. I'll let the image do the talking.

It might tie into the cursor sensing slightly outside of the cursor
tip as well. Grabbing things it shouldn't.I've seen that behavior as
well. I haven't used this style of callout since Version 12.That's when I witnessed the problem. I did not notice it today.

If you see the cursor behave that way again. I would try making sure the resolution of the image is set to 100%. If it isn't, change it. See if that resolves it.

I generally won't install updates from TechSmith when there first released.Maintenance releases scare me.They usually introduce more bugs.I keep my eyes on the forum to see if I can deal with the new ones. Most my editing is done is Photoshop so it's capture and share bugs that concern me.

I just created this Panorama looking out my window.It's a great view, click to enlarge and pan around.The original image was 21,316 x 3,696 pixels after cropping in RAW format "430mb". I scaled it down 7,000 x 1214 jpeg so I could upload it here. The Adirondacks are the mountains in the distance, the Green mountains are behind me. I live in the valley. Thank goodness.It's colder in the mountains. I'm a stones throw from Lake Champlain and Ive never seen Champ the Lake Monster. I don't believe in him either.

Yeah, started out in the burbs of Detroit. Been in Calif, Texas and now here. I miss the warm States during the coldest months. Overall the warm months around here are hard to beat, not much happens after 9PM. It's a good thing I'm not a kid anymore.

Out of curiosity, is the issue that the cursor doesn't change to the directional cursor, allowing you to deform the sides, or is it that the cursor changes and behaves as expected, but the location of the cursor is off kilter (e.g. you go to grab an anchor and the cursor does not change, but if you move the cursor around the area, it eventually changes, but in the wrong location)? I myself have had similar issues to that and I found it most common when working on images imported into Snagit, though I did see it with the occasional Snag. It often happened on large images (2k x 2k or larger), though I experienced it on smaller files as well; are you working with large images, or, in your experience, has this happened with images of any size?

For me, updating my video drivers helped alleviate the issue (almost reducing the issue completely), as did running Snagit as an admin, but even then I experience on the rare occasion (mostly with very large images) and as we continue to develop Snagit, a shrinking problem. I've spoken with our Senior Tech on the subject at length in the past, and passed the necessary files / videos to development, so they are aware of the behavior.

The problem is that having selected the grab handle with visual accuracy, the cursor does not change as expected and in the case of the call out arrow, I can't find a hot spot that does. When it happens again, I will video it.

There's w hole bunch of weird stuff that goes on, Did you see my comment about teh offset when editing text? That may have a common cause.

And then there's the random freezing and discarding the current image being worked on.