Storing akeyp data

DEFINE_DEVICE
dvTP=10001:1:0

DEFINE_EVENT

DATA_EVENT[dvTP] {
   STRING: {

      SELECT {
      
	 ACTIVE(FIND_STRING(DATA.TEXT,'KEYP-',1)): {
	 
	    //do what you want with the keypad data that has arrived
	    //if the user pressed 1234 then DATA.TEXT='KEYP-1234'
	    
	 }

	 ACTIVE(FIND_STRING(DATA.TEXT,'KEYB-',1)): {
	 
	    //do what you want with the keyboard data that has arrived
	    //if the user pressed ABCD then DATA.TEXT='KEYB-ABCD'
	    
	 }
	 
      }
   }
}

BUTTON_EVENT[dvTP,1] {
   PUSH: {
      SEND_COMMAND dvTP, 'AKEYP'
   }
}

BUTTON_EVENT[dvTP,2] {
   PUSH: {
      SEND_COMMAND dvTP, 'AKEYB'
   }
}

DEFINE_CONSTANT
NUM_OF_TPs = 4

DEFINE_DEVICE
dvTP_PORT1 = 10001:1:0

DEFINE_VARIABLE
nCURRENT_OP[NUM_OF_TPs] 

DEFINE_CALL 'Show Keyboard' (INTEGER TP, INTEGER OPERATION, CHAR INITIAL_TEXT[20], CHAR PROMPT[50])
{
nCURRENT_OP[TP] = OPERATION
SEND_COMMAND dvTP_PORT1[TP],"'@AKB-',INITIAL_TEXT,';',PROMPT"

// ADD Code to handle timeouts if desired
}

DEFINE_EVENT
DATA_EVENT[dvTP_PORT1[NUM_OF_TPs]]
{
STRING:
	{
    STACK_VAR INTEGER TPINDEX 
    TPINDEX = GET_LAST(dvTP_PORT1) 
		IF(FIND_STRING(DATA.TEXT,'KEYB-CANCEL',1)
		  nCURRENT_OP[TPINDEX] = 0
		ELSE
		{
			SWITCH(nCURRENT_OP[TPINDEX])
			{
				CASE 1: //store new password
				{
					IF(FIND_STRING(DATA.TEXT,'KEYB-',1))
						{
							REMOVE_STRING(DATA.TEXT,'KEYB-',1)
							
							password = DATA.TEXT
							nCURRENT_OP[TPINDEX] = 0
						}
				}
				CASE 2: //Store new room name
				{
					IF(FIND_STRING(DATA.TEXT,'KEYB-',1))
						{
							REMOVE_STRING(DATA.TEXT,'KEYB-',1)
							
							Roomname = DATA.TEXT
							nCURRENT_OP[TPINDEX] = 0
						}
				}
			}
		}
	}
}

AlexArtist wrote:

Hey marc,

In the line,
DATA_EVENT[dvPanelReal.Number:1:0]

If dvPanelReal was defined as 10001:14:1 would the DATA_EVENT above really occur for device 10001:1:1? If so, THAT"S AWESOME! I've never seen that before, That's totally COOol! What if device 10001:1:1 wasn't even defined anywhere in the code (inside or outside the mod), would this event still work?

Wow, i feel like i'm a serious pro every now and then; but then somehow, i end up learning something totally new to me. If the above DATA_EVENT works, that's coolness man. FINESSE, i tell ya!

Anyway, can't wait to get a response.
Alex

DHawthorne wrote:

I believe the caveat to that is that it won't work across masters. If you only have one master, it's fine. If your module uses port 14, to stick to the existing examples, and the panel is defined in the module's master with port 14, but is connected to a different master, your port 14 will work. But a 10001:1:2 reference won't work on master 1 unless that DEV is explicitly defined on master 1.

MODULE_NAME='MyModule'(DEV dvPanelReal,DEV vdvPanelPort14)

DEFINE_EVENT
DATA_EVENT[dvPanelReal.Number:1:dvPanelReal.System] // <== now we also have attention to the System number of the panel passed into the module
{
  STRING:
  {
    IF(FIND_STRING(DATA.TEXT,'P14KEYB-',1)) // textfield of the keyboard must be definde accordingly
    {
      SEND_STRING vdvPanelPort14,DATA.TEXT
    }
  }
}

AlexArtist wrote:

OK, since you guys have figured out some cool ways around the akeyb port1 problem, i'd like to give you another situation, just to see if there is any possiblity of solving it. (I personally don't see any easy way out on this one)

What if the real device of the module. the dvRealPanel = 10001:14:1, wasn't defined as 10001:14:1 and wasn't real, but instead was a virtual device combined with many other devices. For Example.

vdvThePanel = 36001:1:1
COMBINE_DEVICES(vdvThePanel , 10001:14:1, 10002:14:1, 10003:14:1)

DEFINE_MODULE 'TheAKeybCatcher' inst1(vdvThePanel.....

Once vdvThePanel is passed to the module, is there no way to get the port 1 akeyb data from each panel combined in the vdvThePanel?