QEverCloud
6.1.0
Unofficial Evernote Cloud API for Qt
|
#include <Types.h>
Public Member Functions | |
virtual void | print (QTextStream &strm) const override |
bool | operator== (const Identity &other) const |
bool | operator!= (const Identity &other) const |
![]() | |
Printable ()=default | |
virtual | ~Printable ()=default |
virtual QString | toString () const |
Public Attributes | |
EverCloudLocalData | localData |
IdentityID | id |
Optional< Contact > | contact |
Optional< UserID > | userId |
Optional< bool > | deactivated |
Optional< bool > | sameBusiness |
Optional< bool > | blocked |
Optional< bool > | userConnected |
Optional< MessageEventID > | eventId |
An object that represents the relationship between a Contact that possibly belongs to an Evernote User.
|
inline |
|
inline |
|
overridevirtual |
Implements qevercloud::Printable.
Optional< bool > qevercloud::Identity::blocked |
Has the caller blocked the Evernote user this Identity represents?
Optional< bool > qevercloud::Identity::deactivated |
Indicates that the contact for this identity is no longer active and should not be used when creating new threads using Destination.recipients, unless you know of another Identity instance with the same contact information that is active. If you are connected to the user (see userConnected), you can still create threads using their Evernote-type contact.
Optional< MessageEventID > qevercloud::Identity::eventId |
A server-assigned sequence number for the events in the messages subsystem.
IdentityID qevercloud::Identity::id |
The unique identifier for this mapping.
EverCloudLocalData qevercloud::Identity::localData |
See the declaration of EverCloudLocalData for details
Optional< bool > qevercloud::Identity::sameBusiness |
Does this Identity belong to someone who is in the same business as the caller?
Optional< bool > qevercloud::Identity::userConnected |
Indicates that the caller is "connected" to the user of this identity via this identity. When you have a connection via an identity, you should always create new threads using the Evernote-type contact (see ContactType) using the userId field from a connected Identity. On the Evernote service, the Evernote-type contact is the most durable. Phone numbers and e-mail addresses can get re-assigned but your Evernote account user ID will remain the same. A connection exists when both of you are in the same business or the user has replied to a thread that you are on. When connected, you will also get to see more information about the user who has claimed the identity. Note that you are never connected to yourself since you won't be sending messages to yourself, but you will obviously see your own profile information.