News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

"File associations"?

Started by henriko, December 04, 2005, 01:35:29 PM

Previous topic - Next topic

henriko

First time when i clicked on an .ico and an .rc , in the projects workspace tree, I was asked by Code::Blocks what to do.

The choices was if I would like to open the file within the Code::Block text editor, or in a external program of my choice.

Now I can't find a way to get this question once more. (I have looked in menus, in the registry, and I have serached for ini-files.)

How do one change theese buiit in file associations ?

Urxae

Settings -> Plugins -> Default MIME handler

miggl

LOL, I had the EXACT same question. Thanks for asking it, henriko :). Thanks for the answer Urxae.

miggl

Quote from: Urxae on December 04, 2005, 01:41:24 PM
Settings -> Plugins -> Default MIME handler
That helped! Thanks, now the file opens in my resource editor. However, I still get the following error message:
QuoteERROR:

Could not open file '[resource file here]'.
No handler registered for this type of file.

Any ideas? Again, thanks for your help :)

Mike

henriko


takeshimiya

Perhaps 'Default MIME handler' name isn't very intuitive, it isn't?

Something like 'Registered File Types' or 'File Open Actions'?

The 'Default' part lends to think that there would be other MIME handler plugins.
Wouldn't be better (from a end-user standpoint) having only one MIME plugin, and other plugins requering for extensions (ie. wxSmith) just calling the MIME plugin with the extension?

mandrav

Quote from: Takeshi Miya on December 04, 2005, 08:20:22 PM
Perhaps 'Default MIME handler' name isn't very intuitive, it isn't?

Something like 'Registered File Types' or 'File Open Actions'?

That's the name of the plugin...

Quote from: Takeshi Miya on December 04, 2005, 08:20:22 PM
The 'Default' part lends to think that there would be other MIME handler plugins.
Wouldn't be better (from a end-user standpoint) having only one MIME plugin, and other plugins requering for extensions (ie. wxSmith) just calling the MIME plugin with the extension?

This plugin provides the "default" implementation by associating file extensions with C::B or external programs.
Allowing many MIME plugins, makes C::B more open to extension.
For example, wxSmith could register its own MIME plugin to handle *.wxs files so on double-clicking them, they would open in the designer for editing.
Be patient!
This bug will be fixed soon...

mandrav

Quote from: mandrav on December 04, 2005, 09:45:12 PM
This plugin provides the "default" implementation by associating file extensions with C::B or external programs.
Allowing many MIME plugins, makes C::B more open to extension.
For example, wxSmith could register its own MIME plugin to handle *.wxs files so on double-clicking them, they would open in the designer for editing.

As a matter of fact, I just noticed wxSmith already provides a MIME plugin for this :)
Byo didn't waste any time. Since I enabled multiple plugins residing in the same DLL, he made it work already :D.
Be patient!
This bug will be fixed soon...

takeshimiya

Quote from: mandrav on December 04, 2005, 09:45:12 PM
That's the name of the plugin...

And that's what I was suggesting to change :)
Not that it's a problem for me, but it seems to be not very intuitive for those who don't know what a MIME is.