utlising media keys

本文介绍如何在S60第3版设备上使用RemoteControlAPI处理媒体按键事件,包括Play/Pause、Stop等按键。通常这些按键不会生成常规键盘事件,因此需要采用特定的方法来捕获它们。

Description

Key presses of media keys cannot be detected in the same way as other key events. Media keys, such as Play/Pause, Stop, Volume Up/Down, Rewind, and Forward keys featured on some S60 3rd Edition devices do not generate normal key events that could be handled within the application framework, for example, in HandleKeyEventL() or OfferKeyEventL().

Solution

Events from media keys can be handled with the Remote Control API. Below is a code snippet that demonstrates this.

Remote Control API requires ReadUserData capability.

#include <remconcoreapitargetobserver.h>    // link against RemConCoreApi.lib
#include <remconcoreapitarget.h> // and
#include <remconinterfaceselector.h> // RemConInterfaceBase.lib
 
class CMediaKeysTestUi : public CAknAppUi,
public MRemConCoreApiTargetObserver
{
...
// From MRemConCoreApiTargetObserver
 
void MrccatoCommand(TRemConCoreApiOperationId aOperationId,
TRemConCoreApiButtonAction aButtonAct);
// following functions from MRemConCoreApiTargetObserver are not needed
// in this case -> use empty implementations for these:
// MrccatoPlay
// MrccatoTuneFunction
// MrccatoSelectDiskFunction
// MrccatoSelectAvInputFunction
// MrccatoSelectAudioInputFunction
private:
CRemConInterfaceSelector* iInterfaceSelector;
CRemConCoreApiTarget* iCoreTarget;
};
 
void CMediaKeysTestUi::ConstructL()
{
...
iInterfaceSelector = CRemConInterfaceSelector::NewL();
iCoreTarget = CRemConCoreApiTarget::NewL(*iInterfaceSelector, *this);
iInterfaceSelector->OpenTargetL();
}
 
// ----------------------------------------------------------------------------
// MrccatoCommand()
// Receives events (press/click/release) from the following buttons:
// ’Play/Pause’, ’Volume Up’, ’Volume Down’, ’Stop’, ’Rewind’, ’Forward’
// ----------------------------------------------------------------------------
void CMediaKeysTestUi::MrccatoCommand(TRemConCoreApiOperationId aOperationId,
TRemConCoreApiButtonAction aButtonAct)
{
TRequestStatus status;
switch( aOperationId )
{
case ERemConCoreApiPausePlayFunction:
{
switch (aButtonAct)
{
case ERemConCoreApiButtonPress:
// Play/Pause button pressed
break;
case ERemConCoreApiButtonRelease:
// Play/Pause button released
break;
case ERemConCoreApiButtonClick:
// Play/Pause button clicked
break;
default:
// Play/Pause unknown action
break;
}
//Send the response back to Remcon server
iCoreTarget->PausePlayFunctionResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
 
case ERemConCoreApiStop:
{
switch (aButtonAct)
{
// see above (case ERemConCoreApiPausePlayFunction)
// for possible actions
}
iCoreTarget->StopResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiRewind:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->RewindResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiForward:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->ForwardResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiVolumeUp:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->VolumeUpResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiVolumeDown:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->VolumeDownResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiFastForward:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->FastForwardResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
case ERemConCoreApiBackward:
{
switch (aButtonAct)
{
// see above for possible actions
}
iCoreTarget->BackwardResponse(status, KErrNone);
User::WaitForRequest(status);
break;
}
default:
break;
}
}

Notes:

On most devices only volume keys can be used in 3rd party applications using this API.

Volume keys on accessories (for example, Nokia headsets) use different event types compared to keys on the device. Clients should handle ERemConCoreApiButtonClick,ERemConCoreApiButtonPress, and ERemConCoreApiButtonRelease events.

When pressed and held, media keys do not automatically repeat the commands. If repeat functionality is required, it has to be implemented with (CPeriodic) timers.

内容概要:本文提出了一种针对大规模电动汽车接入电网的双层优化调度策略,并基于IEEE33节点系统进行了建模与仿真分析,配套提供了完整的Matlab代码实现。该策略构建了上层电网运行优化与下层电动汽车充电调度的双层协同模型,综合考虑电网负荷削峰填谷、电压稳定性维持以及电动汽车用户充电需求满足等多重目标,采用先进的优化算法实现对电动汽车集群的智能有序调度。研究详细阐述了双层模型的构建逻辑、目标函数设计、约束条件设定及迭代求解流程,有效降低了电网峰谷差,提升了配电系统对可再生能源的消纳能力,兼具扎实的理论深度与明确的工程应用前景。; 适合人群:电气工程、电力系统及其自动化、能源系统优化等相关专业的研究生、科研人员以及从事智能电网、电动汽车调度、分布式能源管理等领域工作的工程师和技术人员。; 使用场景及目标:①深入研究高比例电动汽车接入对配电网运行特性的影响机制;②掌握电力系统双层优化建模方法及其在实际系统中的求解技巧;③实现电动汽车集群的协同调度与车网互动(V2G)优化控制;④作为撰写学术论文、开展课题研究或复现高水平期刊成果的技术参考与代码基础。; 阅读建议:建议读者结合所提供的Matlab代码逐行理解双层优化模型的数学表达与程序实现细节,重点剖析上下层模型之间的信息交互机制与收敛判据,可通过调整电动汽车渗透率、充电行为参数或引入分布式电源等场景进行拓展性仿真,以深化对智能调度策略适应性的认识。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值