1
0
mirror of https://github.com/qTox/qTox.git synced 2024-03-22 14:00:36 +08:00
Commit Graph

14 Commits

Author SHA1 Message Date
tWido
3257770bfa feat(chatform): Highlight chat history
Calendar dates with chat history highlighted with bold
Fixes #2296
2017-06-25 21:23:04 +02:00
Diadlo
365d703e8a
perf: Pass std::function by reference 2017-06-12 13:46:38 +03:00
Zetok Zalbavar
80f5de31b3
style: reformat current C++ codebase using clang-format 2017-02-26 11:52:45 +00:00
sudden6
38cecdc780
refactor(history): remove deprecated historykeeper
This commit removes historykeeper and code only used by it.

BREAKING CHANGE:
qTox can't open old historykeeper chatlogs after this commit. Use
previous versions to migrate to the new database.
2017-02-05 22:20:12 +01:00
Zetok Zalbavar
7b60a5dd36
chore: explicitly mention that copyright belongs to qTox contributors 2016-11-29 11:12:06 +00:00
Diadlo
b522da5bed
refactor(history): Moved creaton of RawDatabase from History constuctor 2016-11-06 12:37:39 +03:00
Diadlo
902828fcc2
docs(persistence): Added leading stars 2016-08-19 00:20:23 +03:00
Diadlo
1c547fc73f
docs(persistence): Change comment style 2016-07-27 23:39:22 +03:00
initramfs
1dabbca94c
feat(profile): show warning on failure to delete profile
Adds a few qWarning() statements when files fail to delete.
2016-04-29 13:07:27 +08:00
tux3
a0645d5cba
Fix #2700 2015-12-19 16:51:15 +01:00
tux3
489016f358
Fix #2439 2015-12-19 05:00:23 +01:00
tux3
9b9fa13636
Change column order when filling peer cache
A minor detail, but worth it.
2015-12-19 04:42:55 +01:00
tux3
9762839b78
Fix batches bigger than limit on import 2015-12-19 04:40:31 +01:00
tux3
b5cdfb3dce
Implement new SQLCipher based database and history
qTox will automatically import the old history on startup.

This new database code is much more robust.
It is very resilient and will not corrupt or disappear after a crash or
power failure, unlike the old code.
The on-disk database format is also much more compact now.

The database sync option in the advanced settings has been removed,
we know run many database operations asynchronously so performance
should not be a problem anymore, but we always ensure resiliency
in case of abrupt termination, so there is no tradeoff anymore.
2015-12-19 04:17:28 +01:00