Oops, sorry - hit send by mistake...

Here's what I meant to say:

> problem. I can not get Windows to open .fl files with fluid. 
> I'd like to be able to double-click on a .fl file and have it 
> opened by fluid. Windows won't let me associate fluid with 
> .fl files. I've tried by using 'Open With' or by changing the 
> file properties. In both cases a browser comes up which is 
> supposed to let me navigate around till I find the app I want 
> to associate with .fl extensions. I select fluidd.exe, but 
> it's ignored? It forces me to use Photoshop to open the .fl 
> file. The only way I can open a .fl file with fluid right now 
> is to start fluid up explicitly, then browse thru my folders 
> to the .fl file. Ideas anyone?

Yes. My idea is that Windows is a bit s*** and in this case presents
several overlapping (and seemingly incompatible) ways to do the same
thing.
I had this same problem before, on WinXP, here's what I did to make it
work.

In Explorer, select Tools > Folder Options

On the Folder Options dialog select the File Types tab.

Wait while the dialog is populated with the details of all the file
types it knows.

Scroll down this list until you find the entry for FL (assuming one
exists - there was one on all my machines, and it was "wrong", hence the
problem... I assume it had been set by some other random tool...)

Now edit the properties (via the "Change..." button) to make it point at
fluid correctly.

Now, this is where it got tricky... On at least one box, .fl files had
previously been (successfully) associated with the fluid from 1.1.9. The
1.1.9 install had since been removed and replaced with the 1.3 install
(at a different path.)

When I updated the mapping to point to the new fluid, it seemed to
"take" but it became immediately obvious that the stupid windows
mechanism was seeing the "fluid.exe" part, and going "Oh! I know what
that is" and pointing it back to the now non-existent 1.1.9 fluid... So
attempts to open the files all failed.
What I did there was copied the fluid.exe to "new-fluid.exe" and that
worked - but that's a bit of a rubbish workaround so there must be a
better way - probably some nasty registry hack. Or sticking the new
fluid at the path the old one used to be, or something.
In any case, it should not be this hard!









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
fltk@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to