Home AMX Forum AMX Control Products
Options

TPD5 Password Protected Page

Hi all,
Does anybody had application to password protect page flips on TPD5. I know on TPD4 there is an option to password protect page flips.

Comments

  • HARMAN_ChrisHARMAN_Chris Harman Professional University
    This feature is not currently available in TPD5.
  • edgelitocedgelitoc Junior Member
    AMX_Chris wrote: »
    This feature is not currently available in TPD5.

    is there a way to password protect page flips on TPD5
  • GregGGregG Just some guy...
    Popup a keypad from the button and then use netlinx code to verify the password and send_command the page flip if it passes.
  • edgelitocedgelitoc Junior Member
    GregG wrote: »
    Popup a keypad from the button and then use netlinx code to verify the password and send_command the page flip if it passes.

    how would you have a feedback from the system keypad as tpd5 does not support it yet, in TPD4 I can make a button to pop up a keypad without involving netlinx code... thanks for your response,,,,
  • GregGGregG Just some guy...
    Why not use netlinx code? I've often found it much quicker to finish a job using a workaround then spend time encouraging AMX to add new features to their firmware.
    DEFINE_CONSTANT
    Integer nKeypadButtons[] =
    {
    	100,	//	KP 0
    	101,	//	KP 1
    	102,	//	KP 2
    	103,	//	KP 3
    	104,	//	KP 4
    	105,	//	KP 5
    	106,	//	KP 6
    	107,	//	KP 7
    	108,	//	KP 8
    	109	//	KP 9
    }
    DEFINE_EVENT
    Button_Event[dvPanel,nKeypadButtons]
    {
    	Push: cPasswordString = Right_String("cPasswordString,Itoa(Get_Last(nKeypadButtons)-1)",4)
    }
    Button_Event[dvPanel,110] // Password keypad enter
    {
    	Push: If(cPasswordString='1234') Send_Command dvPanel,'^PPN-Whatever'
    }
    
  • edgelitocedgelitoc Junior Member
    GregG wrote: »
    Why not use netlinx code? I've often found it much quicker to finish a job using a workaround then spend time encouraging AMX to add new features to their firmware.
    DEFINE_CONSTANT
    Integer nKeypadButtons[] =
    {
    	100,	//	KP 0
    	101,	//	KP 1
    	102,	//	KP 2
    	103,	//	KP 3
    	104,	//	KP 4
    	105,	//	KP 5
    	106,	//	KP 6
    	107,	//	KP 7
    	108,	//	KP 8
    	109	//	KP 9
    }
    DEFINE_EVENT
    Button_Event[dvPanel,nKeypadButtons]
    {
    	Push: cPasswordString = Right_String("cPasswordString,Itoa(Get_Last(nKeypadButtons)-1)",4)
    }
    Button_Event[dvPanel,110] // Password keypad enter
    {
    	Push: If(cPasswordString='1234') Send_Command dvPanel,'^PPN-Whatever'
    }
    

    thanks Greg for the sample programming,, this is for a fixed password right.. how about if customer wants to make his own password... thanks again....
  • GregGGregG Just some guy...
    That was just a conceptual example.

    The actual implementation would fall into the category of "AMX programming" which our sales team would be happy to quote for you. ;-)
  • edgelitocedgelitoc Junior Member
    GregG wrote: »
    That was just a conceptual example.

    The actual implementation would fall into the category of "AMX programming" which our sales team would be happy to quote for you. ;-)

    Oh that was fun... I just check if you already have a sample for it,, thanks anyways for your great help...
  • gsmithgsmith Ex AMX Engineering
    We have an upcoming G5 firmware and TPD5 release targeted for the end of the year. This feature has been added back in.
  • JMussetterJMussetter Junior Member
    gsmith wrote: »
    We have an upcoming G5 firmware and TPD5 release targeted for the end of the year. This feature has been added back in.

    That is good to hear, that was always a major benefit of TP4 having built-in password handling. I know you can work around this with code and all, but if the customer wants a password that is changeable, then the code gets more complex, and the UI pages to handle setting a new password start to eat up time.
Sign In or Register to comment.