Nov 10 22:41:48 <vish>  nags: is hidden ctrl also included in the appmap ?
Nov 10 22:41:57 <nags>  vish: like ?
Nov 10 22:42:41 <vish>  nags: for passing values from one screen to other. i am yet to find an ex in gnome
Nov 10 22:42:47 <vish>  hidden
Nov 10 22:43:11 <nags>  vish: still I'm not clear
Nov 10 22:43:26 <vish>  say for example
Nov 10 22:43:38 <vish>  we have a display only control
Nov 10 22:44:03 <vish>  that data may not be needed to be shown in the next screen
Nov 10 22:44:15 <vish>  but we may need the value to process
Nov 10 22:44:21 <vish>  or validate
Nov 10 22:45:18 <nags>  vish: oh ya got it...
Nov 10 22:45:35 <nags>  vish: as long as the next screen info is fixed things will be available in appmap
Nov 10 22:45:37 <vish>  but still they are controls right
Nov 10 22:45:49 <vish>  nags: yes yes
Nov 10 22:45:49 <nags>  vish: sat for example open gedit->edit->preferences
Nov 10 22:45:59 <vish>  nags: ok
Nov 10 22:46:06 <nags>  in that there are multiple tabs all the controls inside them are fixed
Nov 10 22:46:18 <nags>  but there are some more scenarios too
Nov 10 22:46:18 <vish>  yes
Nov 10 22:46:27 <nags>  open evolution and create a new account
Nov 10 22:46:32 <vish>  ok
Nov 10 22:46:37 <nags>  based on the account type the next screen changes
Nov 10 22:46:40 <nags>  and they are dynamic
Nov 10 22:46:47 <vish>  yes...
Nov 10 22:46:51 <nags>  those things will be partially available in appmap
Nov 10 22:47:04 <nags>  in such a situation you can just have initial appmap
Nov 10 22:47:19 <nags>  and whenever req you just use remap and undoremap
Nov 10 22:47:24 <vish>  that acc no may be needed in the screen to follow.. but no display
Nov 10 22:47:38 <nags>  as specified in the API Reference page
Nov 10 22:47:54 <vish>  still they are avail in the new screen map right
Nov 10 22:48:27 <nags>  vish: yes
Nov 10 22:48:32 <vish>  nags: ok
Nov 10 22:48:34 <nags>  vish: have a look at this script
Nov 10 22:48:36 <nags>  vish: http://cvs.freedesktop.org/ldtp/pyautosuite/evolution/account-setup.py?rev=1.1&view=markup
Nov 10 22:48:50 <vish>  nags: ye
Nov 10 22:48:52 <vish>  nags: yes
Nov 10 22:52:24 <--     prav33n has quit (Remote closed the connection)
Nov 10 22:53:05 <--     varadhan has quit (http://beagle-project.org)
Nov 10 22:53:21 <vish>  nags: in the scripts we call  methods specific to the tool right..
Nov 10 22:53:35 <nags>  vish: don't get you
Nov 10 22:53:36 <vish>  i mean relavent to UI
Nov 10 22:53:48 <vish>  like ex. open new file
Nov 10 22:54:07 <vish>  for that file->new
Nov 10 22:54:44 <nags>  vish: right
Nov 10 22:54:55 <vish>  nags: ex. click
Nov 10 22:54:57 <vish>  ok
Nov 10 22:55:23 <vish>  their par varies according to the task. is that correct
Nov 10 22:55:31 <vish>  s/par/parameter
Nov 10 22:56:16 <vish>  because they may take n no. of args to perform the func. is that decided by app map gen ?
Nov 10 22:56:53 <nags>  vish no
Nov 10 22:56:59 <nags>  vish: its based on functionality
Nov 10 22:57:05 <vish>  nags: oh.. they are fixed ?
Nov 10 22:57:08 <nags>  vish: the functions that are exported
Nov 10 22:57:17 <nags>  will have all the list of args that a function takes
Nov 10 22:57:23 <nags>  vish: so you can use only them
Nov 10 22:57:30 <nags>  I mean they are fixed
Nov 10 22:57:37 <vish>  nags: yes yes
Nov 10 22:57:41 <nags>  I don't think we need a variable one...
Nov 10 22:57:49 <vish>  true
Nov 10 22:58:00 <vish>  yes. all the controls are fixed
Nov 10 22:58:03 <nags>  I will be back in 2 minutes
Nov 10 22:58:06 <nags>  vish: ya right
Nov 10 22:58:34 <vish>  nags:  am leaving for sleep
Nov 10 22:59:06 <vish>  nags: will try to get ldtp workin in my m/c positively by tomm night.