You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Gaku. On Windows 10, I use the FastStone app as a viewer for jpeg, png, etc. images. After installing the “Tooltip preview” add-on in Tablacus Explorer, I cannot rotate 90º some images in FastStone.
When trying to rotate them, a window appears in FastStone saying “The image is being processed”, and after a few seconds another window appears saying that the file “Maybe it is read-only or in use by another program”. This happened to me with several images, and none of them were read-only. The other functions in FastStone do not present problems, there is only a conflict in the rotation.
I did this test:
I disabled “Tooltip preview” in Tablacus and images can be rotated 90º in FastStones.
I reactivated “Tooltip preview” in Tablacus, and images can no longer be rotated 90º in FastStones.
That's where I discovered the conflict. This happens with some images (jpeg, png) of different sizes, not all of them. I hope there is a solution for this problem. Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hello Gaku. On Windows 10, I use the FastStone app as a viewer for jpeg, png, etc. images. After installing the “Tooltip preview” add-on in Tablacus Explorer, I cannot rotate 90º some images in FastStone.
When trying to rotate them, a window appears in FastStone saying “The image is being processed”, and after a few seconds another window appears saying that the file “Maybe it is read-only or in use by another program”. This happened to me with several images, and none of them were read-only. The other functions in FastStone do not present problems, there is only a conflict in the rotation.
I did this test:
That's where I discovered the conflict. This happens with some images (jpeg, png) of different sizes, not all of them. I hope there is a solution for this problem. Thanks a lot!
The text was updated successfully, but these errors were encountered: