Windows file associations - shell integration

[tiwag]

since the last modifications with file associations (windows only) i got permanent errors when
i doubleclicked a CodeBlocks-project file ( *.cbp) or -workspace file ( *.workspace) in the windows-explorer.

The error message was, that the double-clicked file could not be found -  but CodeBlocks was started and opened the correct file - mysterious  :shock:

i could resolve this behaviour by deleting all ddeexec registry keys in the
regarding Codeblocks file-association registry keys like

Code

HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\open\command\ddexec
HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\open\command\ddexec

[killerbot]

I have the same error message when double clicking on a cbp file (no tried it on workspaces).

And something else I have, all the time cb asks me to become the default application for c/c++ source files. And each time I click on yes,but it does not seem to remember it, or does omeone steal it behinds it's back all the time ?? Well in the past it worked, so I suspect the cause is in the new CB builds somewhere.

[thomas]

I've seen that too, but I don't think it is an actual bug. Everything works fine if the registry contained nothing before, and it never happens again after you delete them, either.
It only seems to happen when you add one registry key to an existing set... no idea what's going on there, but it looks like Windows SNAFU.

There's another funny thing that can happen in that context, too. You can get two instances of Code::Blocks to continuously fight over who is the default application and end up having one file type open in one instance, and another in the other. I haven't figured how, when, and why that happens either. Actually it cannot happen...

[takeshimiya]

Supossedly this was fixed (I think) in Rev 1445.

[killerbot]

seems not, I used a fresh build from today's head revision.

[tiwag]

i only wanted to let you know how you can get rid of this error.

maybe it would be the correct way, that the next release of CB deletes these ddeexec subkeys when it writes the others in it , because it is most likely, that someone that had CB RC2 installed has already these ddeexec registry entries and will then get these annoying errors when updating...

[killerbot]

just checking : it is absolutely save to remove those entries ??
Just for cbp and workspace or fall all codeblocks.xxx types ?

[tiwag]

Supossedly this was fixed (I think) in Rev 1445.

Supposedly maybe ...   

( sorry - coudn't resist )

[thomas]

You can delete everything that looks like CodeBlocks.extension without breaking anything.

[killerbot]

I deleted all codeblocks.extension  as Thomas said.

Then I started my codeblocks : -> the question aout becoming default app fo c/c++ sources --> yes.
Closed CB.

Double clicked on a cbp file ==> error message is still there and CB again asked to be default app ...

Seems the registry hack does not help :-(

[killerbot]

well , it's not quit the same as tiwag said, I check the registry again, and all are back, together with that ddeexec.
New test :
Removed just that one from registry for example  cbp file ---> the error message is gone (still Cb asks to become default app ....)

[tiwag]

... still Cb asks to become default app ...

say NO one time, then edit the registry and you are healed

[killerbot]

which part of registry ??

[tiwag]

which part of registry ??

please look at the first post  only delete the ddeexec and all subsequent keys

[thomas]

I think it has to do with DDE as such... The error also appears (sometimes) when a second file is opened while the first instance of Code::Blocks is still initializing. It does not recur after you have closed Code::Blocks though (so apparently the registry is not modified).

And worse: Try doubleclicking a .cbp twice really fast (quadruple-click, so to say). If you are "lucky", you manage to launch two instances which are both unresponsive, and Explorer freezes up, too....  :shock:
Does not happen without DDE server.