[softwarelist] Re: OvPro and PNG

In article <jwXyVrBJDQ4HFwBN@xxxxxxxxxxxxxxxxxxx>,
   David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote:
> In message <4f82312e81dave@xxxxxxxxxxxxx>, Dave Symes 
> <dave@xxxxxxxxxxxxx> writes
> >On 17 Mar, dave@xxxxxxxxxxxxx wrote:
> >> Ovation Pro for RISC OS v6.06
> >
> >> I have a number of PNG files I want to put into frames within an OvPro
> >> document, It will not do it.
> >
> >> Window pops up with:
> >> "Inserted file is of type PNG not text.
> >> Are you sure you want to proceed?"
> >
> >> Why will it not do what I want?
> >> The OvPro TransFSI filter is seen and active.
> >
> >> CFSI has been seen by the filer during boot up.
> >
> >> As I needed to complete the document this evening, I've had to convert
> >> them all to another graphic file type. Bummer!
> >
> >> Why?
> >> Dave S
> >
> >Continuing...
> >A copy of OvPro running under VRPC will load a PNG into a frame.
> >However Win OvPro will not, presentinng the same message as above.


> The general answer is that to load PNG files you need to have a filter 
> for PNG installed.

 It is installed.

> On Windows that means the filter pack installer has to have been run. 
> There is a registry variable which is set up to point to the appropriate 
> filter. I can tell you the name if you really want to know.

It was working a short while back.

> On RISC OS, it is a bit more complicated. In that the TransFSI filter 
> can be edited to support different file types and the copy of ChangeFSI 
> it calls might support different file types.

> I would not have guessed that ChangeFSI supported PNG, but obviously if 
> it works on VRPC later versions of ChangeFSI must do so.

Mine is later it came with RO 6.06

> There has to be a system variable pointing at the filter for PNG files, 
> F12

> *show ffg*

> will show it.

> I think it comes down to looking at the !Boot and other config files in 
> TransFSI and checking that they set things up for PNG.

> Perhaps a quick fix would be to copy !TransFSI from VRPC to your RISC OS 
> computer.

I've discovered what the problem is...
A short while back it worked okay, and that was because I'd added some
entries to the !Setup file in TransFSI, one of which was PNG, however
since an update to TransFSI (Feb 2008) where the !Setup overwrote my
personally crafted !Setup (Steam now issuing from my ears).

Having dug out the backup of my installed and used that !Setup to replace
the useless one in TransFSI, I'm now back in business on RO.

I don't have the Win Pc running ATM, but when I do I'll check.

Thanks
Dave S

-- 

To unsubscribe or subscribe goto: http://www.freelists.org/list/davidpilling

Other related posts: