Re: [foxboro] FoxView (Displays Can't be Viewed Under Windows Xp)
- From: <Jack.Easley@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 30 Jul 2007 09:57:58 -0500
A caution on using the command line display converter, instead of the
GUI to convert display manager UNIX displays to Foxview 10.1 displays.
We used the command line version of the display converter originally and
had problems with both the previous display button working on the
Windows Foxview displays, as well as all overlays being converted as
regular displays.
If you are converting display manager displays to Foxview displays (.fdf
files) on a UNIX box, then converting these to .g files on the same box.
Then copying the .g files to the Windows box where you convert the .g
files back to .fdf files, always use the Foxdraw GUI for all conversions
on both the UNIX and Windows boxes, or you will have repeat the process.
These symptoms occurred converting Version 6.12 UNIX display manager
displays to Foxview 10.1 displays. I do not know if these symptoms occur
for Version 7.x displays or Foxview conversions.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin Fitzgerrell
Sent: Sunday, July 29, 2007 9:17 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView (Displays Can't be Viewed Under Windows
Xp)
No, I can't elaborate.... Apparently I shouldn't post in the morning
before coffee....
OK, if you're using pdf_fdf (converting DM to FV graphics) you have to
be careful about the options or command line parameters. These can
make a big difference in how your converted displays look -- however,
that has nothing to do with the question the original poster asked.
I'm not aware of any parameters you can use for the fdf_g or g_fdf
commands.
If you're using fdf_g or g_fdf there have been problems over the last
few versions but I believe they're mostly (if not completely)
corrected by 9.0.2 (although I haven't tried a conversion to confirm
this). My biggest problems at 9.0.1 converting from Solaris to
Windows was the behavior of some display commands for opening and
closing overlays which worked fine on Solaris FV but didn't work the
same way on Windows after the fdf_g and g_fdf. These displays had
originally been converted from DM.
Kevin FitzGerrell
On 7/30/07, Jeremy Milum <jmilum@xxxxxxxxx> wrote:
> On 7/29/07, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx> wrote:
> > Also, while doing the conversions (especially command prompt) pay
> > attention to the function of the different parameters or options -
> > they make a big difference in how the resulting Windows displays
look!
>
> oooh, can you elaborate?
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
