OpenSesame 3.3.1 file icon, and association of .osexp file type

fotisfotiadis

Hi

I installed OS 3.3.1 in both a windows 7 and in a windows 10 pc.

In both cases there was no OS icon for my files, and instead a generic default icon (win 10) or a system icon (win 7, see picture)

was used.

So, I edited the registry in my win7 pc, and in the location

computer\HKEY_CLASSES_ROOT\OpenSesame experiment\DefaultIcon, I replaced the default value that was

C:\Program Files (x86)\OpenSesame\opensesame.exe,0

with

C:\Program Files (x86)\OpenSesame\share\icons\opensesame.ico

My osexp files now are ok.

I am only posting this here in case someone finds it interesting.

I do have a question though. By playing around, I believe i changed the default association of the osexp file.

In control panel the osexp files are associated with opensesame.bat

What is the correct default association?

Thank you for your time,

Fotis

sebastiaan

Hi Fotis,

Thanks for bringing this up and also pointing out a solution! I will fix this in the Windows packages.

What is the correct default association?

It's opensesame.bat . The opensesame.exe was just a thin wrapper that basically did the same thing as this batch file, but less efficiently, and so I replaced it in OpenSesame 3.3. The downside is that opensesame.bat is (under some conditions) opened in a console window, which looks a bit ugly.

Cheers!

Sebastiaan

bluelook

Hi Fotis,

i have the same issue, unfortunately i haven't found this entry in the registry (maybe it's different in win 10). I noticed, it happens after installing any new version on top of the existing.. maybe the right solution is to uninstall first.

Lena

sebastiaan

Just for my understanding: It's just a visual problem right, a missing icon? Other than that things work fine?

bluelook

in the previous version i couldn't open the icon with double click, this time it's just a visual problem..

fotisfotiadis

Sebastian, it's a visual problem in 3.3.1, indeed. Other than that everything seems to work fine.

Here is an osexp file on my win10 machine:

In 3.3.0, as @bluelook mentioned previously (and as I also posted in a previous post), the double click on a file didn't work.

sebastiaan

@fotisfotiadis Thanks for this! Based on your suggestion with setting the registry key, I've managed to fix this in the installer for 3.3.2.