> But I've encountered a minor problem that I also ran into on > my XP 64 bit machine. I can not get XP to recognize the new > version of fluid as the application assigned to open .fl > files. It seems to have the old path and filename association > stuck in the registry. Found a couple of workarounds: 1) > rename the new fltk folder to the old folder name, or 2) give > the new fluid executable a different name (I changed it from > fluidd.exe to fluid.exe). I prefer #2. Either way, by > right-clicking on a .fl file, XP will now let me associate > the new version of fluid with .fl files.
Yup - this has been reported before, and seems to be a winXX problem of some sort. Once windows "knows" what app to associate with a file extension, any attempt to assign to a different version of the app with the "same name" but a different path seems to be ignored and the old path is retained... I imagine there's some registry hack for correcting this! SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
