Moderators: e_phoenix13
Go
New
Find
Notify
Tools
Reply
  
-star Rating Rate It!  Login/Join 
<Jakob>
Posted
For quite a while I have had no succes showing my Viewpoint content offline on a Mac. But then I found these lines of code in the MTS3Interface-file:

----------------------------------
//Start legacy defines
//These are only here for legacy support for pages that use them in their HTML already.
//If they clash with your own definitions, delete them. we don't use them in this file.
isIE=isIE4=VET_IE<Big GrinELIMITER:>VET_Gecko
isNN=VET_NN4
isNN6=VET_NN6
isMac=VET_Mac
isWin=VET_Win
//End legacy
----------------------------------

I deleted them and now everything seems to be working like a charm. But is it safe to delete these lines and what do they do?

Thanks
 
Reply With QuoteEdit or Delete MessageReport This Post
1633947735151
Member
Picture of vpjeremy
Posted Hide Post
You don't want to delete these lines.

The code in the MTS3Interface that you deleted is to support content written to use internal MTS3Interface "sniffer" variables. We used to support this in older versions of MTS3Interface. Viewpoint no longer supports this. Viewpoint also does not support or recommend that you edit the MTS3Interface.

You'll need to check how your content is calling/building the plugin. If it suddenly works by deleteing the legacy sniffer code in MTS3Interface, you've probably got code on your HTML page that is using it to do something.

Usually when content doesn't show up on the Mac, it's because you're using windows specific URLS (back slashes), case sensitive URL's, or you're on a layer and not telling the MTS3Interface which one the content is on.

The simplest test is to run your content through Final Check. If it passes through Final Check, then your next step would be to narrow it down to your HTML page. Run the mtx file through Media Publisher to get a blank page with nothing but your content. If it works, you know it's your page at fault.

To summarize:
- run through final check
- run through media publisher
- check for back slashes in the URL's in both the MTX and HTML
- check for capitalization discrepancies (just make everything lowercase with final check if you're testing)
 
Posts: 19 | Registered: January 24, 2003Reply With QuoteEdit or Delete MessageReport This Post
Member
Posted Hide Post
Did this really sort out your problems? Fantastic.
 
Posts: 133 | Registered: January 24, 2003Reply With QuoteEdit or Delete MessageReport This Post
  Powered by Eve Community