Author Topic: Windows file associations - shell integration  (Read 20590 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5494
Re: Windows file associations - shell integration
« Reply #15 on: December 07, 2005, 05:42:51 pm »
I know, but dos it help also for default app ??

Well, I have now deleted all those ddexec's, and somehow they all came back. Seems it's best not to do it for all extension, probably just the cbp and ???

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5494
Re: Windows file associations - shell integration
« Reply #16 on: December 07, 2005, 05:45:39 pm »
and I also have it with cpp files :-( :-(

almighty Yiannis please fix this ....

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Windows file associations - shell integration
« Reply #17 on: December 07, 2005, 05:46:44 pm »
... I have now deleted all those ddexec's, and somehow they all came back. Seems it's best not to do it for all extension, probably just the cbp and ???

sorry, then i don't know - i have deleted all of them too and they didn't come back on my WinXP system and i get no more errors  :D :D :D

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: Windows file associations - shell integration
« Reply #18 on: December 07, 2005, 06:01:44 pm »
I deleted all these:


and from that point, it all worked fine. It is safe to delete these, Code::Blocks writes them out if you click on "Set Now".
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5494
Re: Windows file associations - shell integration
« Reply #19 on: December 07, 2005, 06:31:27 pm »
Just to make sure, there's no conflict with my also installed RC2, I removed RC2, and let's it remove all settings from the registry (probably the old stuff in the regisrty), since the stuff we are talkin about here remains, then I deleted them manually again.
On a previous run i answered no to the default app question.
So now, nothing is linkde to CB, not even the cbp files.

Open CB, Environment settings : set now. (keeping the Check&set file associations (windows only) unchecked).
Close CB.

Double click on a cpp file, CB opens it, but the error message is back :-(  :cry:
I am going nuts.


Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Windows file associations - shell integration
« Reply #20 on: December 07, 2005, 06:49:56 pm »
@ killerbot

check, if you have the dde server extension registered at the base class registry entry of the extension

i.e.
Code
HKEY_CLASSES_ROOT\.cbp

there should be only the standard entry

Code
@="CodeBlocks.cbp"

maybe you've registered the dde-server extension there too.

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5494
Re: Windows file associations - shell integration
« Reply #21 on: December 07, 2005, 07:50:41 pm »
I only have the default entry at that point, so that seems ok.

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Windows file associations - shell integration
« Reply #22 on: January 04, 2006, 06:01:47 pm »
in the meantime i found out more information about this issue and will give a summary of the necessary steps in order to get rid of these dde "file not found" error under windoze OS.

1.) start codeblocks, go to Settings->Environment->General and
check "Run DDE server"
check "Check & set file associations"
press the button "Set now"
uncheck "Check & set file associations"
close codeblocks

2.) go to the registry entries
HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\open\command\ddexec
HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\open\command\ddexec
...(and their companions)...

delete all ddexec keys with their subkeys.

3.) never ever (until this bug is fixed by some windoze spezialists)  allow CodeBlocks to check "Check & set file associations" again
 you get asked every time when you create a new profile, always say NO

now you should be able to doublecklick on any *.cbp, *.workspace, ...  file and it opens with CB fine.

HTH  :)


[edit]
sample of registry for *.cbp and *.workspace files
how it looks when it's work(around)ing

Windows Registry Editor Version 5.00


[HKEY_CLASSES_ROOT\CodeBlocks.cbp]
@="Code::Blocks project file"

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\DefaultIcon]
@="D:\\Programme\\CodeBlocks\\codeblocks.exe,1"

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell]

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\Build]

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\Build\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" -na -nd -ns --batch-build-notify --build \"%1\""

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\open]

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\open\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" \"%1\""

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\Rebuild (clean)]

[HKEY_CLASSES_ROOT\CodeBlocks.cbp\shell\Rebuild (clean)\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" -na -nd -ns --batch-build-notify --rebuild \"%1\""




[HKEY_CLASSES_ROOT\CodeBlocks.workspace]
@="Code::Blocksworkspace file"

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\DefaultIcon]
@="D:\\Programme\\CodeBlocks\\codeblocks.exe,1"

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell]

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\Build]

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\Build\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" -na -nd -ns --batch-build-notify --build \"%1\""

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\open]

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\open\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" \"%1\""

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\Rebuild (clean)]

[HKEY_CLASSES_ROOT\CodeBlocks.workspace\shell\Rebuild (clean)\command]
@="\"D:\\Programme\\CodeBlocks\\codeblocks.exe\" -na -nd -ns --batch-build-notify --rebuild \"%1\""



« Last Edit: January 04, 2006, 06:28:38 pm by tiwag »

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5494
Re: Windows file associations - shell integration
« Reply #23 on: January 05, 2006, 02:56:35 pm »
uninstalled RC2 on my work machine (== pc @ work), and put there the latest nightly build.
CB wants to associate with cpp/other files -> do it.

cbp file is registered (double clicking on them even without the error message box, well well, some work others don't), but CPP files remain in the hands of ............DEV-CPP (even if CB is aalready open or not).

Hmm, this is really haunting me, this is Freddy 15, Jason 21, Halloween 78, Night of the living file types, ....

Yiannis, did you put some special trick in dev-cpp in the days, so no one could get the file association away from it ;-)
(though, on the other systems I also have dev-cpp).

Note , on my work pc I already had the problem with RC2.

[EDIT] it was able to take the headers

Lieven
« Last Edit: January 05, 2006, 02:58:06 pm by killerbot »

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: Windows file associations - shell integration
« Reply #24 on: January 05, 2006, 03:10:19 pm »
Look in
Code
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.c\OpenWithList]

On my machine, I find Dev-CPP everywhere in there, even though it is gone for many months now, and it is the default handler for some types (.c for example).

Maybe we need to write an UnDevCPPizer tool that deletes all these keys...
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: Windows file associations - shell integration
« Reply #25 on: January 05, 2006, 06:21:26 pm »
I second! :) After all, if the user chooses to register the filetypes, it means he got rid of dev. And if he wants to go back to dev (which i doubt  8) ), dev will restore its filetypes.