Strange Effects

MarkJ · Post by **MarkJ** » Thu May 03, 2018 6:51 am

For some strange reason I am getting overlapped text (see below)

Has anyone experienced this before and is there a known cure.

(I'm sorry for bombarding the forum with questions)

ChoccieMuffin · Post by **ChoccieMuffin** » Thu May 03, 2018 9:46 am

Can you post the code from one of those sections please? We might be able to spot something.

Post by **doc_guy** » Thu May 03, 2018 9:57 am

This looks to me like a style issue, so when you post the code from the topics, can you also post the styles used -- specifically the code for the styles that apply to the WallControl10 Server and the WallControl10 Client content.

MarkJ · Post by **MarkJ** » Fri May 04, 2018 12:15 am

Thanks for your time, much appreciated.

Here you go:

<?xml version="1.0" encoding="utf-8"?>
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:lastBlockDepth="6" MadCap:lastHeight="3720" MadCap:lastWidth="1317">
<head>
</head>
<body>
<h1>
<MadCap:keyword term="Introduction" />Introduction</h1>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> offers real time management of small, medium and large scale display walls. <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> also enables you to create multiple walls which can all be controlled by a single wall controller system.</p>
<p>You can place any element of content from a <MadCap:variable name="Variables.OEM_NAME" /> capture card, an IP stream via the PC's processor an <MadCap:variable name="Variables.OEM_ACTIVESQX" /> card or any other local media anywhere on your display wall.</p>
<p>The <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> help files will guide you through the <MadCap:keyword term="functionality of the application" />functionality of the application.</p>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> has a number of elements that contribute to controlling and creating your display wall:</p>
<h2>
<MadCap:keyword term="The Server" />The Server</h2>
<p>The Server is the machine containing the hardware that captures and displays the sources, for example, IP/<MadCap:variable name="Variables.OEM_VISION_TAG" /> windows. A server can be located locally or via a network. Each server can run multiple display walls.</p>
<p>The Server must be started first to allow the Client to locate available servers. To start the server, go to S<b>tart/Programs/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Server</b>. Start the client by going to <b>Start/Programs/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Client</b>. When the client runs it will automatically seek out and display all servers available to you.</p>
<p style="font-weight: bold;">Note:</p>
<p style="font-weight: bold;">Only use the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> software licence dongle in your system. Problems may occur if third party dongles are installed at the same time.</p>
<p>The Client will display all available servers on the application home page; you can then connect to any of the available <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Servers by clicking on the corresponding <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Server button</p>
<h2>
<MadCap:keyword term="The Client" />The Client</h2>
<p>The client (the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> application) should be installed on the system that has been identified to control a display wall. This could be any system on the network including the one driving the display wall i.e. the Server.</p>
<h2>The Client User Interface</h2>
<p>To open the Client user interface go to <b>Start/Programs/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />/<MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Client</b></p>
<h3>
<MadCap:keyword term="Server Properites" />Server Properties</h3>
<p>Clicking on the server name within the Client application populates the Server Properties panel.</p>
<p>The Server Properties panel displays information about the selected server, from how many walls the server is running, to how many of them you have permission to connect to. It also displays the name given to it during its creation. </p>
<h3>
<MadCap:keyword term="Display Walls" />Display Walls</h3>
<p>A display wall is a monitor or multi-monitors tiled together to form one large Windows® desktop. Display walls are represented in the user interface below each server. </p>
<p>The master wall is referred to as the "Blueprint".</p>
<h3>
<MadCap:keyword term="Sources" />Sources, <MadCap:keyword term="Layouts" />Layouts and <MadCap:keyword term="Templates" />Templates</h3>
<p>The Sources, Layouts and Templates are used to create, organise and display the content for your wall. </p>
<p>Templates can assist in the design of your wall, allowing you to use a grid system for the precise placement of sources; custom templates can be created in addition to the default designs available.</p>
<p>Once your content is created and placed on your wall the layouts can be used to save a particular configuration of windows to be recalled when required. </p>
<p>Sources can be <MadCap:variable name="Variables.OEM_VISION_TAG" /> captures, IP streams (from cameras or video files local or on the network), Media files (local to your computer), <MadCap:conditionalText MadCap:conditions="Default.Quant">shared <MadCap:keyword term="Quant sources" MadCap:conditions="Default.Quant" />Quant sources,</MadCap:conditionalText> Applications or Internet browser sources.</p>
<h3>
<MadCap:keyword term="Desktop Tools" />Desktop Tools</h3>
<p>The “Desktop Tools” located to the right of the display wall representation; enable you to carry out functions associated with the selected display wall.</p>
<h3>
<MadCap:keyword term="Window Tools" />Window Tools</h3>
<p>The “Window Tools” become active when a source is dragged onto the wall; the tools are located on the status bar.</p>
<h3>
<MadCap:keyword term="User Settings" />User Settings</h3>
<p>The “User Settings” are located in the application header and consist of:<br /><br /></p>
<ul>
<li>
<MadCap:keyword term="Themes" />Themes - Users may change the application theme colours.</li>
<li>Help - Quick access to the application help files.</li>
<li>
<MadCap:keyword term="User Settings Panel" />User Settings Panel - Allows the user to view and make changes to the application user settings.</li>
</ul>
<h2>
<MadCap:keyword term="Adding Sources to the Global and Wall Source Libraries" />Adding Sources to the Global and Wall Source Libraries</h2>
<p>Users are required to manually add media sources to both the Global and Wall Source Libraries.</p>
<p>A <MadCap:keyword term="Global Source Library" />“Global Source Library” is a repository for media sources that can be used by any wall on the server. A <MadCap:keyword term="Wall Source Library" />“Wall Source Library” is a repository for sources that are only available to a specific wall.</p>
<p>Icons are located in the System Tray for each wall on the server. To select the library, click on the relevant wall icon in the System Tray and select the library you wish to add your media files to. An “Explorer Window” is displayed containing the relevant folders.</p>
<h3>Global Source Library</h3>
<blockquote>
<p>ImageMedia – Photographs/images (.jpg, .bmp. and ,png)</p>
</blockquote>
<blockquote>
<p>Office - .docx files</p>
</blockquote>
<blockquote>
<p>PDFMedia - .pdf files</p>
</blockquote>
<blockquote>
<p>VideoMedia - Video Files (AVI, MP4, WMV and MPG)</p>
</blockquote>
<p>Once your media has been copied in to the relevant folders, it automatically becomes available as a source to use on any wall associated with the server.</p>
<h3>
<MadCap:keyword term="Wall Source Library" />Wall Source Library</h3>
<blockquote>
<p>ImageMedia – Photographs/images (.jpg, .bmp. and ,png)</p>
<p>Office - .docx files</p>
<p>PDFMedia - .pdf files</p>
<p>VideoMedia - Video Files (AVI, MP4, WMV and MPG)</p>
</blockquote>
<p>Once your media has been placed in the folders, it will automatically become available as a source on the specified wall.</p>
<h2>Adding New File Extensions to the Source Libraries</h2>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> has a default set of file types configured for use in the Wall and Global Source Libraries.</p>
<p>Users are able to add new file types to suit requirements.</p>
<p>To add a new file type the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> server must first be stopped and the relevant configuration file updated. The configuration files are stored with the Source Library folders:<br /><br /></p>
<ul>
<li>Global Source Library</li>
</ul>
<blockquote>
<p> C:\ProgramData\<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />\Server<br /><br /></p>
</blockquote>
<ul>
<li>Wall Source Library</li>
</ul>
<p style="text-indent: 0.5in;">C:\ProgramData\<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />\[Wall name]</p>
<p>For example; to <MadCap:keyword term="add a .tif file extension" />add a .tif file extension to the ImageMedia folder in the Global Source Library:<br /><br /></p>
<ul>
<li>Close the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Server by selecting “CloseServer” from the Server System Tray menu.<br /><br /></li>
<li>Open the Image.config in Notepad:</li>
</ul>
<p style="text-indent: 0.5in;">C:\ProgramData\<MadCap:variable name="Variables.OEM_APPLICATION_TAG" />\Server\Image.config<br /><br /></p>
<ul>
<li>Add *.tif to the file extension filter:</li>
</ul>
<p style="text-indent: 0.5in;"><FileExtensionFilters> *.jpg;*.png;*.gif;<span style="color: #000000; font-weight: normal;">*</span>.tif</FileExtensionFilters><br /><br /></p>
<ul>
<li>Save the Image.config file and restart the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Server</li>
</ul>
<p>The new .tif file extension can now be used and images can be placed in the ImageMedia folder as described in the “Adding Sources to the Global and Wall Source Libraries” section above.</p>
<p>It should be noted that URL based sources are subject to input validation. For example <MadCap:variable name="Variables.OEM_ACTIVESQX" /> source can be rtsp://, udp://, http://, https:// and sdp://.
<p>Internet sources can only be http:// and https://.
<h2><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> <MadCap:keyword term="64-Bit" />64-Bit</h2>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> is supported on the Windows® 7 and Windows® 10 64-Bit Operating Systems.</p>
<p>The requirements are as follows:</p>
<h3><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Server</h3>
<ul>
<li>Driver Install version 4.2.4 or later</li>
<li>Windows® 7 64-Bit, or</li>
<li>Windows® 10 64-Bit</li>
</ul>
<h3><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> Client</h3>
<ul>
<li>Windows® 7 64-Bit, or</li>
<li>Windows® 10 64-Bit</li>
</ul>
<h2> <MadCap:keyword term="Antivirus Software" />Antivirus Software</h2>
<p>In order for <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> to operate effectively, it is suggested that users add the <MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> executable directories and media directories into your antivirus white lists.</p>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> executable directories can be found at <b>c:\Program Files (x86)\<<MadCap:variable name="Variables.OEM_NAME" />></b></p>
<p><MadCap:variable name="Variables.OEM_APPLICATION_TAG" /> media directories can be found at <b>c:\ProgramData\<<MadCap:variable name="Variables.OEM_NAME" />></b></p>
<p>It is also suggest that by default you include TCP and UDP traffic for ports <b>8081</b> and <b>8099</b> to your (allowed) firewall rules. As new multi-walls are created, you may need to add those to your firewall (allowed) list. Multi-Wall port numbers are automatically generated when the next available port number is found.</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
</body>
</html>

ChoccieMuffin · Post by **ChoccieMuffin** » Fri May 04, 2018 3:03 am

Mark, that doesn't look like the same topic (searched for WallControl and found nothing).

In that pile of code you're missing </p> at the end of lines 110 and 111.

Are you using a stylesheet at all, or mainly inline styling?

Can you post the code from your stylesheet for your list styles (ul, ol, li).

MarkJ · Post by **MarkJ** » Fri May 04, 2018 3:43 am

Wall Control is a Variable. Its variable tag is OEM_APPLICATION_TAG.

I have created a page break layout and linked it to my first topic after the cover page as instructed and this seems to have cured the problem.

Thanks.

ChoccieMuffin · Post by **ChoccieMuffin** » Fri May 04, 2018 7:55 am

Very glad you found a solution.

Post by **doc_guy** » Mon May 07, 2018 12:31 pm

Make sure that there aren't multiple body frames on your print page layout pages. I wonder if that was the root cause of this issue.

MadCap Software Forums

Strange Effects

Strange Effects

Re: Strange Effects

Re: Strange Effects

Re: Strange Effects

Re: Strange Effects

Re: Strange Effects

Re: Strange Effects

Re: Strange Effects