IEventReceiver.h

本文介绍了Irrlicht引擎中的事件处理机制,包括GUI事件、鼠标事件、键盘事件等类型。详细解释了不同类型的事件如何在系统中传递,并提供了各种事件的具体结构说明。

/*

* IEventReceiver.h

*

* Created on: 2010-10-11

* Author: Mido

* 事件接收器

* - GUI控件事件、鼠标事件、按键事件、日志事件、用户自定义事件

* - 来自于大哥irrlicht

*/

 

#ifndef IEVENTRECEIVER_H_

#define IEVENTRECEIVER_H_

 

#include "ILogger.h"

#include "KeyCodes.h"

 

namespace irrlight

{

 

//! Enumeration for all event types there are.

enum EEVENT_TYPE

{

//! An event of the graphical user interface.

/** GUI events are created by the GUI environment or the GUI elements in response

to mouse or keyboard events. When a GUI element receives an event it will either

process it and return true, or pass the event to its parent. If an event is not absorbed

before it reaches the root element then it will then be passed to the user receiver. */

EET_GUI_EVENT = 0,

 

//! A mouse input event.

/** Mouse events are created by the device and passed to IrrLightDevice::postEventFromUser

in response to mouse input received from the operating system.

Mouse events are first passed to the user receiver, then to the GUI environment and its elements,

then finally the input receiving scene manager where it is passed to the active camera.

*/

EET_MOUSE_INPUT_EVENT,

 

//! A key input event.

/** Like mouse events, keyboard events are created by the device and passed to

IrrLightDevice::postEventFromUser. They take the same path as mouse events. */

EET_KEY_INPUT_EVENT,

 

//! A joystick (joypad, gamepad) input event.

/** Joystick events are created by polling all connected joysticks once per

device run() and then passing the events to IrrLightDevice::postEventFromUser.

They take the same path as mouse events.

Windows, SDL: Implemented.

Linux: Implemented, with POV hat issues.

MacOS / Other: Not yet implemented.

*/

//EET_JOYSTICK_INPUT_EVENT,

 

//! A log event

/** Log events are only passed to the user receiver if there is one. If they are absorbed by the

user receiver then no text will be sent to the console. */

EET_LOG_TEXT_EVENT,

 

//! A user event with user data.

/** This is not used by IrrLight and can be used to send user

specific data though the system. The IrrLight 'window handle'

can be obtained from IrrLightDevice::getExposedVideoData()

The usage and behaviour depends on the operating system:

Windows: send a WM_USER message to the IrrLight Window; the

wParam and lParam will be used to populate the

UserData1 and UserData2 members of the SUserEvent.

Linux: send a ClientMessage via XSendEvent to the IrrLight

Window; the data.l[0] and data.l[1] members will be

casted to s32 and used as UserData1 and UserData2.

MacOS: Not yet implemented

*/

EET_USER_EVENT,

 

//! This enum is never used, it only forces the compiler to

//! compile these enumeration values to 32 bit.

EGUIET_FOIRRE_32_BIT = 0x7fffffff

 

};

 

//! Enumeration for all mouse input events

enum EMOUSE_INPUT_EVENT

{

//! Left mouse button was pressed down.

EMIE_LMOUSE_PRESSED_DOWN = 0,

 

//! Right mouse button was pressed down.

EMIE_RMOUSE_PRESSED_DOWN,

 

//! Middle mouse button was pressed down.

EMIE_MMOUSE_PRESSED_DOWN,

 

//! Left mouse button was left up.

EMIE_LMOUSE_LEFT_UP,

 

//! Right mouse button was left up.

EMIE_RMOUSE_LEFT_UP,

 

//! Middle mouse button was left up.

EMIE_MMOUSE_LEFT_UP,

 

//! The mouse cursor changed its position.

EMIE_MOUSE_MOVED,

 

//! The mouse wheel was moved. Use Wheel value in event data to find out

//! in what direction and how fast.

EMIE_MOUSE_WHEEL,

 

//! No real event. Just for convenience to get number of events

EMIE_COUNT

};

 

namespace gui

{

 

class IGUIElement;

 

//! Enumeration for all events which are sendable by the gui system

enum EGUI_EVENT_TYPE

{

//! A gui element has lost its focus.

/** GUIEvent.Caller is losing the focus to GUIEvent.Element.

If the event is absorbed then the focus will not be changed. */

EGET_ELEMENT_FOCUS_LOST = 0,

 

//! A gui element has got the focus.

/** If the event is absorbed then the focus will not be changed. */

EGET_ELEMENT_FOCUSED,

 

//! The mouse cursor hovered over a gui element.

EGET_ELEMENT_HOVERED,

 

//! The mouse cursor left the hovered element.

EGET_ELEMENT_LEFT,

 

//! An element would like to close.

/** Windows and context menus use this event when they would like to close,

this can be cancelled by absorbing the event. */

EGET_ELEMENT_CLOSED,

 

//! A button was clicked.

EGET_BUTTON_CLICKED,

 

//! A scrollbar has changed its position.

EGET_SCROLL_BAR_CHANGED,

 

//! A checkbox has changed its check state.

EGET_CHECKBOX_CHANGED,

 

//! A new item in a listbox was seleted.

EGET_LISTBOX_CHANGED,

 

//! An item in the listbox was selected, which was already selected.

EGET_LISTBOX_SELECTED_AGAIN,

 

//! A file has been selected in the file dialog

EGET_FILE_SELECTED,

 

//! A file open dialog has been closed without choosing a file

EGET_FILE_CHOOSE_DIALOG_CANCELLED,

 

//! 'Yes' was clicked on a messagebox

EGET_MESSAGEBOX_YES,

 

//! 'No' was clicked on a messagebox

EGET_MESSAGEBOX_NO,

 

//! 'OK' was clicked on a messagebox

EGET_MESSAGEBOX_OK,

 

//! 'Cancel' was clicked on a messagebox

EGET_MESSAGEBOX_CANCEL,

 

//! In an editbox was pressed 'ENTER'

EGET_EDITBOX_ENTER,

 

//! The tab was changed in an tab control

EGET_TAB_CHANGED,

 

//! A menu item was selected in a (context) menu

EGET_MENU_ITEM_SELECTED,

 

//! The selection in a combo box has been changed

EGET_COMBO_BOX_CHANGED,

 

//! The value of a spin box has changed

EGET_SPINBOX_CHANGED,

//! A table has changed

EGET_TABLE_CHANGED,

EGET_TABLE_HEADER_CHANGED,

EGET_TABLE_SELECTED_AGAIN,

 

//! .Mido.2010.9.28

//! The value of WaitDialog cancel

EGET_WAITDIALOG_CANCEL,

EGET_WAITDIALOG_TIMEOUT

};

 

} // end namespace gui

 

//! SEvents hold information about an event. See IrrLight::IEventReceiver for details on event handling.

struct SEvent

{

//! Any kind of GUI event.

struct SGUIEvent

{

//! IGUIElement who called the event

gui::IGUIElement* Caller;

 

//! If the event has something to do with another element, it will be held here.

gui::IGUIElement* Element;

 

//! Type of GUI Event

gui::EGUI_EVENT_TYPE EventType;

 

};

 

//! Any kind of mouse event.

struct SMouseInput

{

//! X position of mouse cursor

s32 X;

 

//! Y position of mouse cursor

s32 Y;

 

//! mouse wheel delta, usually 1.0 or -1.0.

/** Only valid if event was EMIE_MOUSE_WHEEL */

f32 Wheel;

 

//! Type of mouse event

EMOUSE_INPUT_EVENT Event;

};

 

//! Any kind of keyboard event.

struct SKeyInput

{

//! Character corresponding to the key (0, if not a character)

c16 Char;

 

//! Key which has been pressed or released

EKEY_CODE Key;

 

//! If not true, then the key was left up

b1 PressedDown;

 

//! True if shift was also pressed

b1 Shift;

 

//! True if ctrl was also pressed

b1 Control;

};

 

//! A joystick event.

/** Unlike other events, joystick events represent the result of polling

* each connected joystick once per run() of the device. Joystick events will

* not be generated by default. If joystick support is available for the

* active device, _IRR_COMPILE_WITH_JOYSTICK_EVENTS_ is defined, and

* @ref IrrLightDevice::activateJoysticks() has been called, an event of

* this type will be generated once per joystick per @ref IrrLightDevice::run()

* regardless of whether the state of the joystick has actually changed. */

struct SJoystickEvent

{

enum

{

NUMBER_OF_BUTTONS = 32,

 

AXIS_X = 0, // e.g. analog stick 1 left to right

AXIS_Y, // e.g. analog stick 1 top to bottom

AXIS_Z, // e.g. throttle, or analog 2 stick 2 left to right

AXIS_R, // e.g. rudder, or analog 2 stick 2 top to bottom

AXIS_U,

AXIS_V,

NUMBER_OF_AXES

};

 

/** A bitmap of button states. You can use IsButtonPressed() to

( check the state of each button from 0 to (NUMBER_OF_BUTTONS - 1) */

u32 ButtonStates;

 

/** For AXIS_X, AXIS_Y, AXIS_Z, AXIS_R, AXIS_U and AXIS_V

* Values are in the range -32768 to 32767, with 0 representing

* the center position. You will receive the raw value from the

* joystick, and so will usually want to implement a dead zone around

* the center of the range. Axes not supported by this joystick will

* always have a value of 0. On Linux, POV hats are represented as axes,

* usually the last two active axis.

*/

s16 Axis[NUMBER_OF_AXES];

 

/** The POV represents the angle of the POV hat in degrees * 100,

* from 0 to 35,900. A value of 65535 indicates that the POV hat

* is centered (or not present).

* This value is only supported on Windows. On Linux, the POV hat

* will be sent as 2 axes instead. */

u16 POV;

 

//! The ID of the joystick which generated this event.

/** This is an internal IrrLight index; it does not map directly

* to any particular hardware joystick. */

u8 Joystick;

 

//! A helper function to check if a button is pressed.

b1 IsButtonPressed(u32 button) const

{

if(button >= (u32)NUMBER_OF_BUTTONS)

return bf;

 

return (ButtonStates & (1 << button)) ? bt : bf;

}

};

 

 

//! Any kind of log event.

struct SLogEvent

{

//! Pointer to text which has been logged

const c8* Text;

 

//! Log level in which the text has been logged

ELOG_LEVEL Level;

};

 

//! Any kind of user event.

struct SUserEvent

{

//! Some user specified data as int

s32 UserData1;

 

//! Another user specified data as int

s32 UserData2;

};

 

EEVENT_TYPE EventType;

union

{

struct SGUIEvent GUIEvent;

struct SMouseInput MouseInput;

struct SKeyInput KeyInput;

struct SJoystickEvent JoystickEvent;

struct SLogEvent LogEvent;

struct SUserEvent UserEvent;

};

 

};

 

//! Interface of an object which can receive events.

/** Many of the engine's classes inherit IEventReceiver so they are able to

process events. Events usually start at a postEventFromUser function and are

passed down through a chain of event receivers until OnEvent returns true. See

IrrLight::EEVENT_TYPE for a description of where each type of event starts, and the

path it takes through the system. */

class IEventReceiver

{

public:

//! Constructor 

IEventReceiver(){}

 

//! Destructor

virtual ~IEventReceiver() {}

 

//! Called if an event happened.

/** /return True if the event was processed. */

virtual b1 OnEvent(const SEvent& e) = 0;

};

 

} // end namespace IrrLight

 

#endif /* IEVENTRECEIVER_H_ */

 

 

 

本文来自:鬼火神灯- irrlight.com

该数据集通过合成方式模拟了多种发动机在运行过程中的传感器监测数据,旨在构建一个用于机械系统故障检测的基准资源,特别适用于汽车领域的诊断分析。数据按固定时间间隔采集,涵盖了发动机性能指标、异常状态以及工作模式等多维度信息。 时间戳:数据类型为日期时间,记录了每个数据点的采集时刻。序列起始于2024年12月24日10:00,并以5分钟为间隔持续生成,体现了对发动机运行状态的连续监测。 温度(摄氏度):以浮点数形式记录发动机的温度读数。其数值范围通常处于60至120摄氏度之间,反映了发动机在常规工况下的典型温度区间。 转速(转/分钟):以浮点数表示发动机曲轴的旋转速度。该参数在1000至4000转/分钟的范围内随机生成,符合多数发动机在正常运转时的转速特征。 燃油效率(公里/升):浮点型变量,用于衡量发动机的燃料利用效能,即每升燃料所能支持的行驶里程。其取值范围设定在15至30公里/升之间。 振动_X、振动_Y、振动_Z:这三个浮点数列分别记录了发动机在三维空间坐标系中各轴向的振动强度。测量值标准化至0到1的标度,较高的数值通常暗示存在异常振动,可能与潜在的机械故障相关。 扭矩(牛·米):以浮点数表征发动机输出的旋转力矩,数值区间为50至200牛·米,体现了发动机的负载能力。 功率输出(千瓦):浮点型变量,描述发动机单位时间内做功的速率,取值范围为20至100千瓦。 故障状态:整型分类变量,用于标识发动机的异常程度,共分为四个等级:0代表正常状态,1表示轻微故障,2对应中等故障,3指示严重故障。该列作为分类任务的目标变量,支持基于传感器数据预测故障等级。 运行模式:字符串类型变量,描述发动机当前的工作状态,主要包括:怠速(发动机运转但无负载)、巡航(发动机在常规负载下平稳运行)、重载(发动机承受高负荷或高压工况)。 数据集整体包含1000条记录,每条记录对应特定时刻的发动机性能快照。其中故障状态涵盖从正常到严重故障的四级分类,有助于训练模型实现故障预测与诊断。所有数据均为合成生成,旨在模拟真实的发动机性能变化与典型故障场景,所包含的温度、转速、燃油效率、振动、扭矩及功率输出等关键传感指标,均为影响发动机故障判定的重要因素。 资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值