#7 App-independent error message from Windows Explorer

[Aygent543]

System Details

Windows 7 Ultimate 64-bt SP1

Screenshot : https://drive.google.com/uc?id=0B_FuMGaqECLuenUxeDVJNDd5a0U

Before Installation

I was using Picasa and Windows image viewer for veiwing images including GIF but without any animation. I had to open GIFs in google Chrome to see the animations.

Installation

1. Downloaded setup file and installed.
2. Confirmed "Yes" for "Default GIF Viewer" dialog.
3. Opened an animated GIF image.
4. An error dialog/child window first opened followed by successfull launch of the app in concern.

Reproducing Bug

1. Try opening an animated GIF using Windows Explorer.
2. Set "GIF Viewer" to default GIF viewer if not set already.
3. A small error window will first popup saying "There was a problem sending the command to the program."

Screenshot : https://drive.google.com/uc?id=0B_FuMGaqECLuWVdXRXo0U1o5d28

1. The application successfully opens the image and displays it. No problem here.
2. Close the app. The error window still continues to remain.
3. Close the error window becaue otherwise it will prevent the explorer and you from opening the file again.
4. Try opening a GIF again and the same thing happens (from step 3) again.
5. The error window will appear again and again and you have to close it each time to use the explorer further.

[Luiz Fernando]

Thanks for the thorough report, and sorry for the delay- will look into what's going on.

[Luiz Fernando]

I'm pushing an update v1.7.0 that better addresses opening of .gif files when associated.

Please verify within your registry (WinKey + R, type 'regedit' and hit enter in the prompt that appears), and delete the registry entry 'HKEY_CLASSES_ROOT.gif', head down to "%AppData%..\Local\Luiz Fernando\GIF Viewer", if the folder exists, it should contain the settings of the app. Delete this folder and it should ask again to associate during startup.

I hope this fixes the issues with registry setup. If the warning continues to appear let me know, it might be something else that's going on w/ Explorer + Office's DDEExecute.

[Aygent543]

OK. I'll check that out :)