cmd.h

嵌入式LINUX的智能家居系统源码

/********************************************************
 **ker_cmd.h
 **
 **author:YslayerY
 ***********************************************************/


#include<qtimer.h>
#include"cmd_config.h"
#include"can_conf.h"
class ker_cmd : public QObject
{
	Q_OBJECT
public:
	ker_cmd();
	~ker_cmd();
//center cmd part
public slots:
//so every button pushed signals that need service should pass an integer as cmd
	void center_cmd_proxy(int cmd_t);//that can call different executable models,and these modules should have proxy
								//themself //other means temperatures
								//this will treat blue tooth cmds also
								//this is called by button signals and by can and blue tooth readers
signals:
	void sig_cmd_door(int cmd_t,char to);		//should connect to class can's write cmd
	void sig_cmd_home(int cmd_t,char to);		//should connect to class can's write cmd
	void sig_cmd_pda(int cmd_t);				//should connect to class blue tooth

//this is the kernel cmd part
public slots:
	void ker_cmd_proxy(int);
signals: //this is emitted by cmd_proxy to signal different modules
	void sig_cmd_local_audio(int cmd_t);//dispatche cmds to different part of the system
	void sig_cmd_local_video(int cmd_t);
	void sig_cmd_local_ui(int);//ker or pda requests when finished should signal ui and pda their states
 	void sig_cmd_local_bt(int);
	void sig_log(int);

	
//properties
private:
//connect state
	bool DOOR_connected;
	bool HOME_connected;
	bool PDA_connected;
//and all cmd modules should be connected up by KER cmd module


public:
	void try_connect_door();//should never return connect state,because they returns when connect_request
	void try_connect_home();//cmd writes to can bus
	void try_connect_pda();
	void try_connect_all();
public:
	void door_connected();//when there is a connect confirm cmd from all these parts
	void home_connected();//these functions will be called to treat this
	void pda_connected();		
};