I think it is still a real problem wich should be solved.
The fact there is a dozen posts concerning this issue means nobody considers this way of file association as correct.
You tell us, raving, that it's an apple problem, but why any other mac application do not install itself as default for all unknown file type ?
Because that's what hexedit does : I still got an hexedit icon for any unknown file. I know I could force the file association by selecting another "default application", but I can't understand why I have to do this : Hexedit is uninstalled, I'm not supposed to have any reference to this application in my system.
I just received a pps file this morning. pps were not handled by any application yet, on my mac, so the hexedit is the default pps file icon... So I have to attribute an application to change the icon : hexedit is the default icon, even if I don't use hexedit anymore... so logic. Anyway, it's not so difficult, it's just a little bit boring to feel like a stranger has invaded my system. I could also use the RCDefaultApp preference panel, but I only can modify the registered file extensions or mime type, not the unknown files.
It's more annoying when it concerns a random cache file : You cannot force the default application for a thunderbird attachement or for a partial downloaded file. The behaviour is the same as usual : hexedit is the default icon.
So please, raving, try to find a way to fix this. I suppose hexedit is registering itself for all unassociated binary file at the first launch, so I suppose it's possible to revert this register and I would be grateful to you to provide us a tool to do it.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll say it again... there is NO way for me to fix this. Other programs are assigning "unknown" files the document type for HexEdit. I realize that some people find this to be a problem and it's easy to blame HexEdit for it, but even if you never put HexEdit on your system the files will still be associated with HexEdit... the HexEdit icon just won't display if HexEdit has never been on the system.
HexEdit NEVER registers itself for any files; it simply has a finder resource that says "this is my file type and this is my document type". That's it. HexEdit NEVER takes ownership over another file or filetype; in order for a file to be associated with HexEdit one of three things must occur:
You save a new file with HexEdit
You manually change the filetype of a file to associate it with HexEdit
Another program sets the filetype of a file to the filetype of a HexEdit document.
Since HexEdit never registers itself for all unassociated binary files (can you even do this in OS X? I don't think so...) there can be no tool to "undo" the associations. And as far as I understand associations in Mac OS there is no such thing as an "unknown binary file". All files are associated with an application via a filetype or a suffix. If a file has neither or it has a filetype or suffix without an associated application, then that file is associated with no application (and thus a generic icon). If, at a later time, a program is put on the machine that can open the document filetype or suffix then the finder displays that program's document icon for the appropriate files. The FINDER does this, NOT the program.
For instance, if you never have Excel on your Mac, then .xls files are generic icons and do not open in a program automatically. If you then put Excel on your Mac then ALL .xls files are displayed with the Excel document icon and open in Excel. Excel never even has to be run for this to occur, the finder just needs to see the Excel application. HexEdit operates in exactly the same way.
Again, programs are PURPOSEFULLY saving files using HexEdit's document filetype; this associates them with HexEdit even if HexEdit is NEVER on the machine. The only "fix" for this is to cause the programs to save these files using a different document filetype.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it is still a real problem wich should be solved.
The fact there is a dozen posts concerning this issue means nobody considers this way of file association as correct.
You tell us, raving, that it's an apple problem, but why any other mac application do not install itself as default for all unknown file type ?
Because that's what hexedit does : I still got an hexedit icon for any unknown file. I know I could force the file association by selecting another "default application", but I can't understand why I have to do this : Hexedit is uninstalled, I'm not supposed to have any reference to this application in my system.
I just received a pps file this morning. pps were not handled by any application yet, on my mac, so the hexedit is the default pps file icon... So I have to attribute an application to change the icon : hexedit is the default icon, even if I don't use hexedit anymore... so logic. Anyway, it's not so difficult, it's just a little bit boring to feel like a stranger has invaded my system. I could also use the RCDefaultApp preference panel, but I only can modify the registered file extensions or mime type, not the unknown files.
It's more annoying when it concerns a random cache file : You cannot force the default application for a thunderbird attachement or for a partial downloaded file. The behaviour is the same as usual : hexedit is the default icon.
So please, raving, try to find a way to fix this. I suppose hexedit is registering itself for all unassociated binary file at the first launch, so I suppose it's possible to revert this register and I would be grateful to you to provide us a tool to do it.
Thanks
Hmmmm... So the one and only solution to remove the hexedit icon association to the unkown files is to reinstall the whole system ? Really ?
I'll say it again... there is NO way for me to fix this. Other programs are assigning "unknown" files the document type for HexEdit. I realize that some people find this to be a problem and it's easy to blame HexEdit for it, but even if you never put HexEdit on your system the files will still be associated with HexEdit... the HexEdit icon just won't display if HexEdit has never been on the system.
HexEdit NEVER registers itself for any files; it simply has a finder resource that says "this is my file type and this is my document type". That's it. HexEdit NEVER takes ownership over another file or filetype; in order for a file to be associated with HexEdit one of three things must occur:
You save a new file with HexEdit
You manually change the filetype of a file to associate it with HexEdit
Another program sets the filetype of a file to the filetype of a HexEdit document.
Since HexEdit never registers itself for all unassociated binary files (can you even do this in OS X? I don't think so...) there can be no tool to "undo" the associations. And as far as I understand associations in Mac OS there is no such thing as an "unknown binary file". All files are associated with an application via a filetype or a suffix. If a file has neither or it has a filetype or suffix without an associated application, then that file is associated with no application (and thus a generic icon). If, at a later time, a program is put on the machine that can open the document filetype or suffix then the finder displays that program's document icon for the appropriate files. The FINDER does this, NOT the program.
For instance, if you never have Excel on your Mac, then .xls files are generic icons and do not open in a program automatically. If you then put Excel on your Mac then ALL .xls files are displayed with the Excel document icon and open in Excel. Excel never even has to be run for this to occur, the finder just needs to see the Excel application. HexEdit operates in exactly the same way.
Again, programs are PURPOSEFULLY saving files using HexEdit's document filetype; this associates them with HexEdit even if HexEdit is NEVER on the machine. The only "fix" for this is to cause the programs to save these files using a different document filetype.