I fixed the application bundle, and now HexEdit icons behave the way they should. (The main problem was that you had type *** assigned and you should have used type .) I also hooked up the document icons the way they ought to be hooked up. I also polished up the icons. HexEdit icons will only be assigned to proper types of binary or text files now. Other unknown types of files will not ever get HexEdit's icons or "open with" stamped on them anymore.
If you delete all previous installations of HexEdit (you must also empty the trash), and THEN unstuff this archive, it should repair the association problems automatically. It may also help to restart if the problems persist.
PLEASE include my new bundle and my 3 new icons in HexEdit! They fix the problems everyone is complaining about.
Remember, you must delete all compiled HexEdit applications first to fix the problem. Developer: You can incorporate the bundle and icons into your build and it should work from then on. All you have to do is have ONE old compiled version of HexEdit on any drive and the problem will still be there.
I understand that it is a strange thing for me to ask you to remove all other versions of HexEdit from your system, so ask some other people to do it first for you if you want to make sure I know what I'm talking about.
I look forward to seeing your work, although the link you provide results in a file that stuffit will not open. Can you give it another shot?
I would like to point out that the file association with '****' is the proper way to associate any file to be OPENED by an application. This does NOT associate those files with the app, only indicates that they can be opened. Maybe this has changed, but I'm not aware that it has.
That being the case, HexEdit is ONLY associated with ONE file type, and that type is the HexEdit data file (hDmp if I recall correctly). In order for a file to be associated with HexEdit without user intervention another program has to assign a file a filetype of 'hDmp'. Many download programs, including Safari, IE and most FTP programs actually assign unknown files the HexEdit filetype, and changing what files HexEdit CAN open will NOT change what files get associated with HexEdit.
Note that users can cause any filetype to be associated with HexEdit by saying "Open With" and using the "all files" option.
PS: this is not to say that your fix does not work, hopefully it does because it would make everyone's life much easier. Once you can provide a link to a good archive with source I'll grab it and start testing.
Finally, THANKS for taking the time to look into this and then share your findings and solution. I personally appreciate it :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The .sit file opens fine for me with The Unarchiver. It appears Ben changed the associations to extension based with some MIME type definitions. See the diff below.
I fixed the application bundle, and now HexEdit icons behave the way they should. (The main problem was that you had type *** assigned and you should have used type .) I also hooked up the document icons the way they ought to be hooked up. I also polished up the icons. HexEdit icons will only be assigned to proper types of binary or text files now. Other unknown types of files will not ever get HexEdit's icons or "open with" stamped on them anymore.
If you delete all previous installations of HexEdit (you must also empty the trash), and THEN unstuff this archive, it should repair the association problems automatically. It may also help to restart if the problems persist.
PLEASE include my new bundle and my 3 new icons in HexEdit! They fix the problems everyone is complaining about.
Remember, you must delete all compiled HexEdit applications first to fix the problem. Developer: You can incorporate the bundle and icons into your build and it should work from then on. All you have to do is have ONE old compiled version of HexEdit on any drive and the problem will still be there.
I understand that it is a strange thing for me to ask you to remove all other versions of HexEdit from your system, so ask some other people to do it first for you if you want to make sure I know what I'm talking about.
Thank you!
Ben Boldt
http://www.d.umn.edu/~bold0070/HexEdit.app.sit
I look forward to seeing your work, although the link you provide results in a file that stuffit will not open. Can you give it another shot?
I would like to point out that the file association with '****' is the proper way to associate any file to be OPENED by an application. This does NOT associate those files with the app, only indicates that they can be opened. Maybe this has changed, but I'm not aware that it has.
That being the case, HexEdit is ONLY associated with ONE file type, and that type is the HexEdit data file (hDmp if I recall correctly). In order for a file to be associated with HexEdit without user intervention another program has to assign a file a filetype of 'hDmp'. Many download programs, including Safari, IE and most FTP programs actually assign unknown files the HexEdit filetype, and changing what files HexEdit CAN open will NOT change what files get associated with HexEdit.
Note that users can cause any filetype to be associated with HexEdit by saying "Open With" and using the "all files" option.
PS: this is not to say that your fix does not work, hopefully it does because it would make everyone's life much easier. Once you can provide a link to a good archive with source I'll grab it and start testing.
Finally, THANKS for taking the time to look into this and then share your findings and solution. I personally appreciate it :)
The .sit file opens fine for me with The Unarchiver. It appears Ben changed the associations to extension based with some MIME type definitions. See the diff below.
--- HexEdit.app/Contents/Info.plist 2007-08-02 22:40:07.000000000 -0700
+++ HexEdit.app/Contents/Info.plist 2006-02-15 15:17:05.000000000 -0800
@@ -7,10 +7,40 @@
<key>CFBundleDocumentTypes</key>
<array>
<dict>
<array>
</array>
</dict>
</array>
<key>CFBundleExecutable</key>