List of issues still present in Snagit 13.1.2

  • 1
  • Problem
  • Updated 2 years ago
@Chris Larson

I've jotted down a list of issues that comes to mind, that are not resolved as of the current version of Snagit, version 13.1.2. Many of these already have their own corresponding forum discussions and/or support tickets but I thought it'd be convenient to list them all together. Can you confirm that these are being tracked on your side to be fixed in a maintenance release for Snagit 13?


1) Between sessions the Editor window doesn't remember its maximized state, if it was last left in a maximized state.

2) When the Editor window is maximized, the tooltip on the 'Restore Down' control/button says 'Maximize' instead of 'Restore Down'.

3) When the Editor window is maximized, the Close control/button is not right up against the infinite edge.

4) The installer creates and leaves behind two identical copies of itself.

5) The library view inside the Editor doesn't automatically refresh anywhere near as often as it should. One example I often encounter is where a capture will have been automatically opened in the Editor, so I'll click on the 'Library' button to switch to the library view, only to find that that new capture is not even visible there. Not until I press F5. Another example is when the Editor is open, sorted by Date, and new captures get added in the wrong position. Only when you press F5 do the images move into the correct Date-ordered position. Ideally the library should be refreshing itself anytime you change views, and anytime a new capture gets added.

6) The numbers in the left pane of the library view don't always match up with the numbers of images visible in the corresponding view in the right pane. Also, the numbers in the left pane don't refresh when they should, and there is no way to manually refresh them either. For example, if you delete a file from outside of Snagit, the number shown in the left pane in Snagit will not decrease to reflect the deletion of that image, even though it is no longer even present/visible in the right pane.

7) The expansion state of the 'Advanced' dropdown within each tool is not saved between sessions.

8) "Preview in Editor" set to Off still opens the latest capture in the Editor.

9) Snagit doesn't correctly handle a restart of the Windows shell (explorer.exe).

10) Automatic scrolling capture (initiated from an All-In-One capture, for example) doesn't work as well as it does in other screen capture programs. Snagit positions itself as a premier screen capture tool, yet even other free programs can do better than it in this area of functionality. For example, Snagit can't do an automatic scrolling capture in the Opera web browser (TechSmith simply consider it "unsupported" yet my point still stands that if other programs can do it, why can't Snagit?).

11) Scrolling performance is very slow in the Editor, when scrolling an image using the scrollbar.

12) When capturing from the bottom of the screen, by dragging upwards to mark a capture area, the bottom row of pixels is missed (this bug goes back many years).

13) When opening the capture window for the first time (after a reboot, for example), the user gets to see the herky-jerky animation as the window/form resizes itself to the last state it was left in (if you last left it on the Image or Video tab where the window is bigger and more options are shown). Ideally, Snagit should first calculate the dimensions of its form, resize itself appropriately while the form is still hidden, and then display itself, so that the user doesn't see any of the herky-jerkiness of the window adjusting itself.
Photo of Neville

Neville

  • 73 Posts
  • 20 Reply Likes

Posted 2 years ago

  • 1
Photo of JL1

JL1

  • 201 Posts
  • 91 Reply Likes
Thanks for summing this up.
Photo of Neville

Neville

  • 73 Posts
  • 20 Reply Likes
@Chris Larson

Did you see my post?
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
I had not. Thank you for the heads up! I'll look at these and get you a response. :)
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
Thank you for providing a comprehensive list. :)We can’t commit to dates or releases for fixes because there are plenty of opportunities for Windows or other unforeseen issues to pop up that will need our attention. But I can let you know where each of these stand.

Being tracked
2) When the Editor window is maximized, the tooltip on the 'Restore Down' control/button says 'Maximize' instead of 'Restore Down'.

5) The library view inside the Editor doesn't automatically refresh enough

6) The numbers in the left pane of the library view don't always match up with the numbers of images visible in the corresponding view in the right pane
  • This one wasn’t written up as clearly on our end, thank you

7) The expansion state of the 'Advanced' dropdown within each tool is not saved between sessions.

8) "Preview in Editor" set to Off still opens the latest capture in the Editor.
  • As I’ve stated before, this is something that likely will be a while before being addressed. The work that’s been done so far has gotten this into a good state for good majority of the people we’ve tested with.

10) Automatic scrolling capture (initiated from an All-In-One capture, for example) doesn't work as well as it does in other screen capture programs. 
  • We continue to work to support a majority of the use cases. Panoramic capture is amazing for the use cases where auto-scrolling doesn’t work as expected.

12) When capturing from the bottom of the screen, the bottom row of pixels is missed 

Known issue
3) When the Editor window is maximized, the Close control/button is not right up against the infinite edge.
  • Hopefully will get fixed by a different change down the road

9) Snagit doesn't correctly handle a restart of the Windows shell (explorer.exe).

Needs more information
1) Editor window doesn't remember its maximized state between sessions
  • I’m using 13.1.2 and if I close Snagit completely (even killing the process), Snagit comes back maximized. Am I missing a step?

4) The installer creates and leaves behind two identical copies of itself.
  • What folder is the installer being left behind for you?

11) Scrolling performance is very slow in the Editor, when scrolling an image using the scrollbar.
  • Have to filed a support ticket on this one? I’d be curious to see what kind of system specs you have and if it’s hardware specific. But it require a more hands on investigation than GetSat would be good for.

13) When opening the capture window for the first time (after a reboot, for example), the user gets to see the herky-jerky animation as the window/form resizes itself to the last state it was left in.
  • Same as above. The toggles changing state on initial load is a known issue but the animation lag you’re describing may have something to do with your system.
Photo of Neville

Neville

  • 73 Posts
  • 20 Reply Likes
#9
We've discussed this previously, so I guess that's why you've listed it under Known. But it's not being tracked?

#1
Are you sure? Try maximizing an application such as Microsoft Word. Quit the application. Re-launch it. Notice that you have a restore-down button at the top right of the window because the window state is maximized. Repeat the test for Snagit Editor. Notice that after re-launching it the window takes up the whole screen, but it is not in a properly maximized state, i.e. you will see a maximize button present, not a restore-down button. And this will be especially obvious if you, like me, have another monitor to the right because the non-maximized window will be casting a shadow on the second monitor because it isn't in a correctly maximized state. I logged a ticket on your system long ago for this (ticket 239177) so I'm surprised to not see this on your list of items being tracked to be fixed.

#4
There's a more detailed discussion here:
https://feedback.techsmith.com/techsmith/topics/snagit-13-installer-leaves-leaves-behind-several-cop...
This is very easy to spot if you use a tool like WizTree to scan your filesystem and list files by size. Look at this screenshot where I can easily see the same setup package left behind in 2 locations:


#11
I'm not the only person to mention this here in the forums. I run Snagit on very high-end, high-spec machines. Scrolling an image in the Snagit Editor is slow compared to scrolling anything else in any other Windows application. It's not unworkable, it's just sluggish.

#13
We may be talking about the same thing. What Snagit is not doing is getting its user interface sized correctly before showing the UI to the user for the first time. It's an issue concerning things being done in the wrong order in the source code. If we're talking about something different, and you can't see a slight stuttering effect when showing that window for the first time, let me know and maybe I can shoot a video of it.

#8
I actually thought we were in agreement on this following our last discussion on this topic, and that it would be fixed sometime soon.
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
#9
Correct, like we discussed before, given the abnormal OS workflow, this is not something that we support doing.

#1
Yeah, strange that you're seeing some other behavior.
This is what I'm seeing: https://www.screencast.com/t/lCB18ztsK2

#4
Ok, thanks for the info. I know the installer needs to be left around for proper uninstall, but I'm not sure where Windows stores those files. We can look into it.

#11
It would still be helpful to have more information about the number of captures, composition of those captures, location of the data Store, system specs, and the like. So a support ticket would be ideal.

#13
Yeah, we totally may be talking past each other here. A video would be great. :)

#8
I get where you're coming from on this one, I do. That said, we have have this working in a good state. Editor stays out of the task bar. It doesn't foreground. But we have the Editor switching to Editor view instead of Library. It's not prioritized high at this point though given other things we need to address.
Photo of Neville

Neville

  • 73 Posts
  • 20 Reply Likes
Hi Chris

#1
OK, I see what the missing step is. Quitting and restarting immediately remembers the state. But if you reboot it will not remember the state. It's at the beginning of each work day that (after booting up) that I find Snagit Editor has not remembered the maximized state that it was last left in. With Snagit set to run at startup, with the Editor running always in the background, try maximizing the window, then closing the window so it goes to the system tray, then reboot your machine, and then open the Editor. I bet you will see then that the maximized state has not been remembered. Can you confirm? This is a long-standing one that I would love to see fixed soon.

#13
I'll try to record a video at some point. It'll be necessary to use a different program as the recording will need to start from before Snagit is running.

#9
I guess I will have to give up on pursuing this. Sure, it's not a "workflow", but it usually either involves another program doing something disruptive, or that particular Windows process crashing from time to time. Other programs do the correct thing and recover successfully, Snagit cannot. It sounds like we need to leave it there.

#10
As this one is also a dead-end, I'll have to use Snagit for most captures, and PicPick for the others that Snagit has trouble with.
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 557 Posts
  • 283 Reply Likes
#1
Ah! Gotcha, I'll try that and track it.

#13
Much appreciated :)
Photo of patt_thomasson

patt_thomasson

  • 28 Posts
  • 8 Reply Likes
Can I add an item to this list? I noticed that the SnagIt 13 entry that appears in my Startup folder, (enabled via an option) sports a non-localized value, TSC_SI_13, rather than the friendly name, SnagIt 13.

Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 555 Posts
  • 283 Reply Likes
That was an intentional change because we have reports of customers searching for "Snagit" through the Start menu and then "Snagit 13" showing up from both the Startup folder and from the normal "TechSmith" folder. Which sounds okay, but... the startup folder entry has a flag on it so that Snagit will start minimized (because most folks don't want to have to minimize the capture window after every restart). But that led to issues of people being confused because Snagit wouldn't pop up after selecting the entry in the Startup folder. So we changed the name to something that wouldn't pop up in a normal search. If you have a suggestion for a more friendly name that still meets that criteria, let me know for sure. The underscores definitely don't make it match the neighbors in that folder, agreed.
Photo of patt_thomasson

patt_thomasson

  • 28 Posts
  • 8 Reply Likes
Do you need to include the version number?

I'd suggest you consider following the pattern that DirectoryOpus uses, that has startup parameters that are different than if you invoke it from the Program Folder (see my pic). So it would be:

- Snagit (minimized on Startup)
or
- Snagit (Startup)

I assume you can understand my assuming that the label you used looks like unlocalized text... ;-)
Photo of Chris Larson

Chris Larson, Snagit Technical Product Manager

  • 555 Posts
  • 283 Reply Likes
That's helpful. :) Thank you.