view src/cs/services/fcbm/fcbm_messages.c @ 265:e57bfdadf49a

mmiIcons.c: fix bogus icnType in incoming_call_animate[] The incoming call animation icons are actually drawn in 256-color format, but they were incorrectly declared as BMP_FORMAT_32BIT_COLOUR in the incoming_call_animate[] array. Why were they still getting displayed correctly despite this bogosity? Answer: because the mmi_dialogs_animation_new_CB() function overrides the icon bitmap type to 0x02, which means 256-color format. Needless to say, the icon format should be made correct at the source of the data, and at some later point we may need to remove the override from the animation display function.
author Mychaela Falconia <falcon@freecalypso.org>
date Mon, 17 May 2021 07:18:36 +0000
parents a5b00817a60f
children
line wrap: on
line source

/*
 * Incoming message dispatch for the FCBM task is implemented here.
 */

#include "fcbm/fcbm_func_i.h"
#include "fcbm/fcbm_messages.h"
#include "kpd/kpd_api.h"
#include "rv/rv_general.h"
#include "rvf/rvf_api.h"
#include "rvm/rvm_use_id_list.h"

void fcbm_process_message(T_RV_HDR *msg_ptr)
{
	switch (msg_ptr->msg_id) {
	case FCBM_START_CHG_MODE:
		fcbm_process_msg_chg_mode();
		return;
	case FCBM_START_RESET_MODE:
		fcbm_process_msg_reset_mode();
		return;
	case FCBM_START_PHONE:
		fcbm_process_msg_phone_on();
		return;
	case KPD_KEY_EVENT_MSG:
		fcbm_process_kpd_msg((T_KPD_KEY_EVENT_MSG *) msg_ptr);
		return;
	default:
		rvf_send_trace("FCBM task: Received an unknown message", 38,
				NULL_PARAM, RV_TRACE_LEVEL_DEBUG_HIGH,
				FCBM_USE_ID);
	}
}