synce_info_new(3) [debian man page]

SYNCE_INFO_NEW(3)					       http://www.synce.org/						 SYNCE_INFO_NEW(3)

NAME

       synce_info_new - allocate a new SynceInfo struct

SYNOPSIS

       #include <synce.h>

       SynceInfo *synce_info_new(const char *device_name);

       void synce_info_destroy(SynceInfo *info);

       const char *synce_info_get_name(SynceInfo *info);
       bool synce_info_get_os_version(SynceInfo *info, int os_major, int os_minor);
       int synce_info_get_build_number(SynceInfo *info);
       int synce_info_get_processor_type(SynceInfo *info);
       const char *synce_info_get_os_name(SynceInfo *info);
       const char *synce_info_get_model(SynceInfo *info);
       const char *synce_info_get_device_ip(SynceInfo *info);
       const char *synce_info_get_local_ip(SynceInfo *info);
       int synce_info_get_partner_id_1(SynceInfo *info);
       int synce_info_get_partner_id_2(SynceInfo *info);
       const char *synce_info_get_object_path(SynceInfo *info);
       pid_t synce_info_get_dccm_pid(SynceInfo *info);
       const char *synce_info_get_transport(SynceInfo *info);
       const char *synce_info_get_password(SynceInfo *info);
       int synce_info_get_key(SynceInfo *info);

DESCRIPTION

       The synce_info_new() function returns a pointer to a newly allocated and populated SynceInfo struct for a mobile device.

       If device_name is non-NULL, the returned struct relates to a mobile device with that name, or NULL if no device of that name is connected.

       If  device_name	is NULL, the exact behaviour depends on the flavour of dccm daemon in use.  When using vdccm(1) or the deprecated dccm(1),
       the current active device is selected. This is usually the last device connected, specifically that described in the active_connection file
       which  is  by default in the ~/.synce/ directory. With odccm(1) the first device connected will be returned. With synce-hal this depends on
       the device(s) in question, and should be considered undefined.

       This struct should be freed with synce_info_destroy(3).

	      typedef struct _SynceInfo {
		  pid_t dccm_pid;	/* process id of dccm daemon */
		  char* device_ip;	/* device ip address */
		  char* local_iface_ip; /* local interface ip address */
		  char* password;	/* device password */
		  int key;		/* device pass key */
		  int os_major; 	/* device OS major version */
		  int os_minor; 	/* device OS minor version */
		  int build_number;	/* OS build number */
		  int processor_type;	/* device processor */
		  int partner_id_1;	/* first sync partner id number */
		  int partner_id_2;	/* second sync partner id number */
		  char* name;		/* device name */
		  char* os_name;	/* device OS name eg. PocketPC */
		  char* model;		/* device hardware name */
		  char* transport;	/* interface type */
		  char* object_path;	/* path to device's information */
	      } SynceInfo;

       These fields must be accessed with the synce_info_get_ functions. The particular fields populated depend on the flavour of dccm	daemon	in
       use.

       The  use  of dccm(1) is deprecated. When using vdccm(1) all fields are populated except for local_iface_ip and os_minor.  With odccm(1) and
       synce-hal, dccm_pid, password,  key,  build_number,  partner_id_1  and  partner_id_2  are  not  used.   odccm(1)  also  does  not  populate
       local_iface_ip.

RETURN VALUE

       The synce_info_new() function returns a pointer to the allocated SynceInfo struct, or NULL if an error occured.

SEE ALSO

       synce(7), odccm(1), vdccm(1)

The SynCE Project						    2007-08-26							 SYNCE_INFO_NEW(3)

Check Out this Related Man Page

EditorInfo(3U)						    InterViews Reference Manual 					    EditorInfo(3U)

NAME

       EditorInfo - stores information about an editor's contents

SYNOPSIS

       #include <Unidraw/editorinfo.h>

DESCRIPTION

       An  EditorInfo  object is a UMap that stores a list of strings and/or string tuples.  Application-specific editors can use these objects to
       store information about what components, commands, and tools they incorporate in their interface.  The programmer can write out this infor-
       mation with a catalog object and read it back in later.	The application can then let the user change the editor's configuration by editing
       the catalog-generated file.  For example, an EditorInfo object could have a list of names for tools in the  editor's  interface	that  have
       been  saved  with  the catalog. When the application is restarted, the EditorInfo object can be read first, and then the catalog can recon-
       struct the tools given their names.

PUBLIC OPERATIONS

       EditorInfo()
	      Construct an EditorInfo instance.

       void Register(const char* name, const char* info = ``'')
       void UnregisterName(const char*)
       void UnregisterInfo(const char*)
       boolean Registered(const char* name)
	      Register enters a name or name-info tuple into the EditorInfo object.  UnregisterName removes an entry whose name string matches the
	      given  one,  while UnregisterInfo removes an entry whose info string matches the given one. The Registered operation returns whether
	      or not an entry with a matching name exists.

       const char* GetName(const char* info)
       const char* GetInfo(const char* name)
	      Name-info tuple lookup operations. The GetName operation returns the name corresponding to a given info string,  while  the  GetInfo
	      operation returns the info string for a given name.

       const char* GetName(int index)
       const char* GetInfo(int index)
	      Name or info strings can be accessed by an index that reflects the order in which they were registered.  These operations return the
	      name or info string for a given index.

SEE ALSO

       Catalog(3U), Editor(3U), UMap(3U)

Unidraw 							   30 July 1990 						    EditorInfo(3U)

Linux and UNIX Man Pages

synce_info_new(3) [debian man page]

Check Out this Related Man Page