jadedctrl/Chat-O-Matic
jadedctrl/ Chat-O-Matic
1
0
Disbranĉigi 0
Fontkodo Issues 20 Tirpetoj Actions Packages Projects Eldonoj 2 Wiki Activity
Chat-O-Matic/application/DefaultItems.h

23 lines
579 B
C
Raw Normal View History

Basis for custom userlist pop-up menu items
2021-06-15 21:05:21 -05:00
/*
* Copyright 2021, Jaidyn Levesque <jadedctrl@teknik.io>
* All rights reserved. Distributed under the terms of the MIT license.
*/
#ifndef DEFAULTITEMS_H
#define DEFAULTITEMS_H
#include <ObjectList.h>
Register commands & pop-up items through messages Use IM_MESSAGEs, IM_REGISTER_COMMAND and IM_REGISTER_USER_ITEM, for registering commands and user-list pop-up items. The former replaces CayaProtocol::Commands(), which was a real bad idea in the first place. Just awful. No idea why I did that instead of this, which is nicer and significantly easier anyway.
2021-06-15 23:29:38 -05:00
class BMessage;
Basis for custom userlist pop-up menu items
2021-06-15 21:05:21 -05:00
Move command/menu-item registration to call Registration of custom chat commands and menu-items for protocols was done by the IM_REGISTER_* messages, and is now done through direct calls to the CayaProtocol object. The new model for call/message for protocols is this: Temporary information (chat messages, roster members, etc.) should be accessed through messages. Relatively static data (protocol name, commands) should be accessed through direct calls to the protocol object.
2021-06-20 01:24:34 -05:00
BObjectList<BMessage> DefaultCommands();
BObjectList<BMessage> DefaultChatPopUpItems();
BObjectList<BMessage> DefaultUserPopUpItems();
Basis for custom userlist pop-up menu items
2021-06-15 21:05:21 -05:00
BMessage* _UserMenuItem(const char* label, BMessage* msg,
int32 user_perms, int32 target_perms,
int32 target_lacks, bool ignorePriority,
bool toProtocol);
#endif // DEFAULTITEMS_H