<br><br><div class="gmail_quote">On Sun, Sep 26, 2010 at 9:11 AM, Sean P. DeNigris <span dir="ltr"><<a href="mailto:sean@clipperadams.com">sean@clipperadams.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
Hi,<br>
<br>
When I download Cog 5.8b6, after opening a cog image, it gets associated<br>
with all .image files even if I never requested it to. Then, when I try to<br>
open one of many non-cog images, I get an Apple error report. If I open a<br>
Finder information dialog on a .image file and set the non-Cog VM to open<br>
all .image files, it doesn't work. I'm using Mac OS 10.6.4.<br>
<br>
Has anyone else experienced this? How can this be fixed?<br></blockquote><div><br></div><div>It can't be "fixed" as it's part of the Mac architecture that the most recent application that associates itself with a particular filetype becomes the system default. To work around it do a Get Properties on an image file, then use the Open With dropdown to select a different VM and click Change All.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Sean<br>
<font color="#888888">--<br>
View this message in context: <a href="http://forum.world.st/Cog-takes-over-image-files-on-Mac-tp2714466p2714466.html" target="_blank">http://forum.world.st/Cog-takes-over-image-files-on-Mac-tp2714466p2714466.html</a><br>
Sent from the Squeak - VM mailing list archive at Nabble.com.<br>
</font></blockquote></div><br>