| Age | Commit message (Collapse) | Author |
|---|
|
This is a flimsy implementation without proper RoomPowerLevelEvent
definition, just to enable upgrades without causing noise to each and
every user of a room on an unstable version.
|
|
Closes #236.
|
|
Don't use distinct items for each type of event; only for repeated/
combinable ones.
|
|
Initial (sans power levels checking) implementation of the check that
room should be upgraded. Closes most of #236.
|
|
A signal emitted when the room receives a tombstone event from the
server.
|
|
This concludes the mandatory part of #235.
|
|
Use RoomCreateEvent and RoomTombstoneEvent in the backend, covering most
of #235.
|
|
|
|
Mirroring Connection::loadedRoomState but for each single room (will be
used as a NOTIFY signal for one-time-set events).
|
|
Closes #273, in particular.
|
|
So that the room has at least some display name before any events come
to it.
|
|
non-Omittable values
|
|
|
|
|
|
|
|
Also: const'ified other methods related to file urls.
|
|
Also: use constructors instead of list-based initialisation in FileTransferPrivateInfo to enable a case of "invalid/empty" FileTransferPrivateInfo with status == None.
|
|
|
|
It actually introduces an off-by-one error; the original code was
correct. #qmatrixclient:matrix.org is used instead of #test:matrix.org
to check lazy-loading (see https://github.com/matrix-org/synapse/issues/4300)
|
|
|
|
|
|
Closes #253.
|
|
...instead of the entire function body wrapped in an if block.
|
|
This concludes beta-version of lazy-loading support in libQMatrixClient (#253).
|
|
Commit fd52459 introduced a regression rendering the cache unusable
after a client restart (an empty state overwrites whatever state was in
the cache). This commit contains the fix, along with more room change
tracking.
|
|
The members of the summary can be omitted in the payload; this change fixes calculation
of the roomname from hero names passed in room summary. Also: RoomSummary can be dumped to QDebug now.
|
|
|
|
|
|
|
|
|
|
Closes #257.
|
|
This allows to batch updates into signals being emitted only once per
sync. Also supercedes emitNamesChanged flag used in a few places.
|
|
SyncData now resides in its own pair of files and is capable to load either from file or from JSON. There is also (yet untested) capability to load rooms from files if a file name stands is the value for a given room id. This allows to store the master cache file separately from cache files for each room, massively easing the problem of bulky accounts that can overflow the poor capacity of Qt's JSON engine.
|
|
These two are intermingled in Room::addHistoricalMessageEvents because
processing empty events found in a historical batch is no different from
discovering (not lazy-loaded) members.
|
|
This was one more cause of #257 - the case when a redaction on a state
event arrives in the same batch as the redacted event.
|
|
|
|
|
|
|
|
Closes #258.
|
|
Also: use Matrix type instead of internal type id in StateEventKey
(Because internal type id maps to the library type system which will not
discern between Unknown events and therefore will mix together events of
different types in Room::Private::baseState/currentState. The Room code
is updated accordingly (bonus: more asserts there).)
Closes #255.
|
|
Also: make moveEventsToTimeline() always put historical events from
position -1 rather than 0 so that Private::baseState could always
correspond to the before-0 position.
|
|
- registerEventType(): comment the cryptic _ variable
- Room::postEvent: document the return value
- Room::Private: upgrade comments to doc-comments - even though in Private, they still are helpful to show hints in IDEs.
- General cleanup
|
|
|
|
Synced events always have their event ids, so checking those for event id renders most of the function useless (and returns an incorrect result). Closes #248.
|
|
|
|
Closes #194.
|
|
|
|
No-order is already modelled with the other overload, and Omittable<>
breaks interfacing with QML.
|
|
|
|
Call events no more store deserialised values; instead they deserialise
values on the fly, same as all other events. They are no more treated as
state events (The Spec doesn't define them as state events in the first
place). A common base class, CallEventBase, is introduced that defines
data pieces common to all call events (call id and version).
|
