| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- replaced "No filter" option text with "All", to avoid the "No filter
is not enabled" situation
- replace the "Filter" label on the button with "1 Filter"/"2 Filters"
when a filter is active, so a user can immediately see that without
having to open the filter pop-up
|
|
The `Models::addFilterMenuItems` method is used in 2 cases, once in the
`ActivityWidget`, and once in the `ProtocolWidget`. Both have their own
item model, so both need their own role passed in for filtering on.
The bug was that `ProtocolItemModel::ProtocolItemRole::Account` was used
forall cases, even when a `ActivityListModel::ActivityRole::Account`
should have been passed in.
Fixes: https://github.com/owncloud/client/issues/9425
|
|
Fixes: #9494
|
|
|
|
Fixes: #9000
|
|
|
|
https://sentry.io/organizations/owncloud/issues/2641160195/events/a0519fae20d74fdda4f696270a307bcd/
|
|
Issue: #9000
|
|
This removes the need to check for the existance of the pointers
Fixes: #8690
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We now hav proper headers and sortig capabilities
Fixes: #8158
|
|
|
|
|
|
|
|
boundingRect().width() should also fix the "bogus" warning, this is also
why it was deprecated
|
|
destination() now consistently points to the file after the successful
sync operation. _file might be the place the item was moved from.
|
|
|
|
This allows IssuesWidget to selectively wipe only the 'Up' ignores
during selective local discovery.
|
|
The struct makes it easy to pack data and should consume less memory
overall.
|
|
Conflicts:
shell_integration/nautilus/syncstate.py
|
|
Previously we were sorting by size string, where
"6 MB" < "3 KB".
|
|
|
|
|
|
To do this conveniently a bunch of functionality that's common to
IssueWidget and ProtocolWidget is moved to ProtocolItem.
Also the convenience function to asynchronously retrieve the private
link url is moved from the socket api to the network jobs.
|
|
The issues tab uses custom ordering where overall and summary sync
issues are displayed first. This ordering is preserved by creating
special sorting logic for the "time" column.
It needed special handling anyway, since sorting by time-string would
have yielded incorrect results.
|
|
This is motivated by the fact that QMetaObject::noralizeSignature takes 7.35%
CPU of the LargeSyncBench. (Mostly from ABstractNetworkJob::setupConnections and
PropagateUploadFileV1::startNextChunk). It could be fixed by using normalized
signature in the connection statement, but i tought it was a good oportunity
to modernize the code.
This commit only contains calls that were automatically converted with clazy.
|
|
It's quite different in regard to blacklist handling and overall
sync failure changes.
|
|
|
|
Now that csync builds as C++, this will avoid having to implement
functionalities needed by csync mandatorily in csync itself.
This library is built as part of libocsync and symbols exported
through it.
This requires a relicense of Utility as LGPL. All classes moved into
this library from src/libsync will need to be relicensed as well.
|
|
* Add a more functional error view #5516
* Allow filtering of ignores and warnings to see only important bits.
* Navigate from the folder view to the error view by clicking on the
error list with the red background.
* Move the error list into its own ui file to allow easier extension.
* Fix issue around tab id handling in ActivitySettings.
* Rename "Action" column to "Issue".
* Change mouse cursor to hand over button and new error list area
Several OSX fixes provided by guruz.
|
|
Before, blacklisted errors were set to FileIgnored status and hence
displayed as warnings. Now, they have their own BlacklistedError
category which allows them to appear as errors in the issues list and in
the shell integration icons.
|
|
|
|
This will allow us to keep a reference on the items in connected slots.
|
|
This was to catch duplicate emissions for PropagateDirectory but we
don't emit this signal anymore from there.
This fixes a warning about PropagatorJob not being a registered metatype.
This reverts commit fe42c1a818c3b1ccadb2e9557971b62a350573b4.
|
|
|
|
See #5180
|
|
During propagation, we create a line for each file, taking memory, but
we delete all lines passed 2000 right at the beginning of the next sync.
Since the user has little chances of being able to read past those 2000
lines in the log, we might as well keep it capped at 2000 also during
propagation to prevent it from eating memory.
|
|
|
|
Since the font metrics aren't reliable on windows, we add some
extra space there.
|
|
|
