Font Issues with iPort Module

Is this the Netlinx module or the Duet module and which version of the module is in use?

I've recently used the latest version of the Netlinx iPort module and I changed the font for all of the text fields (to Dungeon because customer wanted the Blue Steel layout).

Didn't have any issues with font changes being lost. I was using MVP 8400's not 500i's.

You may have a corrupt panel file but I would try "remove all user pages" from the 500i's setup screen and do a full clean transfer to see if that fixes the problem.

Also there was a recent post about a similar issue and the fix was to use a font size slightly different than what the poster wanted originally. I don't remember the specifics but say for example you are trying to use the font set to size 10 well then try 11 instead even though there probably isn't an 11 in the drop down list, just go ahead and type it in.

Hopefully one of these things will fix it. I've had to start over from scratch before when a file became corrupted and it sucked!

remeolb wrote: »

I just tried doing a "remove user pages" and then re-transferring the files to the touch panel. This did not fix the issue. I think this code in the user interface module for the iPort has something to do with my problem but I don't really understand what the code is doing.

DEFINE_FUNCTION SEND_VTEXT (INTEGER nCHAN, CHAR strMSG[]) //All variable text to panel is sent thru this function
{
    STACK_VAR WIDECHAR strSTRING1[600]
    STACK_VAR CHAR strSTRING2[600]
    STACK_VAR INTEGER iTEXT
       
    strSTRING1 = WC_DECODE(strMSG,WC_FORMAT_UTF8,1) // Used to Decode 
    strSTRING2 = WC_ENCODE(strSTRING1,WC_FORMAT_TP,1)
    
    
    FOR(itext = 1;iTEXT <= nDEV_LENGTH;iTEXT++) //Check to see if G3 or G4 panel to send correct text command
    {
	//SEND_STRING 0,"'R4 Device_ID = ',ITOA(DEVICE_ID(dvTP[3]))" //R4 Device is 322
	IF(DEVICE_ID(dvTP[iTEXT]) < 256) //Is it a G3 Panel in the array?
	{
	    IF(nON_IPORT_PAGE[iTEXT] = 1) // Is the Panel currently on the iPort page?
	    {
		SEND_COMMAND dvTP[iTEXT], "'TEXT',ITOA(nCHAN),'-',strMSG"        //G3 Panels without Unicode Support
	    }							     		//NOTE: Unicode not supported on G3 panels
	}
	ELSE //It must be a Modero Panel and not a G3 panel
	{
	    IF(nON_IPORT_PAGE[iTEXT] = 1) // Is the Panel currently on the iPort page?
	    {
		IF(DEVICE_ID(dvTP[iTEXT]) = 322) //Is it an R4 Remote in the array?
		{
		    //Send Nothing - Use Virtual R4 in Main.axs in DEV array for iPort UI devices
		}
		ELSE
		{
		    SEND_COMMAND dvTP[iTEXT], "'^UNI-',ITOA(nCHAN),',0,',strSTRING2"   //Unicode Modero Panels
		    //SEND_COMMAND dvTP,"'^TXT-',ITOA(nCHAN),',1&2,',strMSG"      // G4 panels without Unicode
		}
	    }
	}
    }
}

I don't get all the unicode stuff.

Well unicode is an extension of the ascii character set and I believe is encoded differently. The function that you posted is there to make sure that nonstandard ascii characters are properly sent to the UI. This function should not be changing fonts or font sizes just the character encoding.

You can test this by commenting out the module definition in your code and seeing if the text is still changed when the module is disabled.