| Age | Commit message (Collapse) | Author |
|---|
|
This allows us to use resources in the cmd app and the unit tests.
Fixes: #8839
|
|
|
|
|
|
We also ensure that qApp is completely set up when we create the icon.
|
|
|
|
|
|
- introduce the Platform class, which can do RAII style set-up/tear-down
- macOS: move Finder integration into the Utility namespace
- move retrieve the socket path into the Utility namespace
|
|
Gnome users need to use the desktop file actions
|
|
On Windows and Linux this is the case if a used started ownCloud using a shortcut/desktop entry (we pass --showsettings)
On mac re receive a special event when the client bundle is launched by a user
|
|
* Replace custom argument parsing with QCommandLineParser
* Remove obsolete --logwindow option
* Translate all strings in commandline arguments parsing
* Use QCommandLineParser to display help and version information
This commit further eliminates the now-obsolete showHint function. QCommandLineParser does not show a hint to use --help, so we should no longer do this either in order to provide a unified UX.
* Parse arguments passed to method as parameter
* Ensure correct order of format string arguments
|
|
|
|
|
|
|
|
When owncloud is started during desktop startup the tray may not yet
be running when the client starts. This will make the client attempt
to create a tray icon again after 10 seconds if there's no tray
during initial startup.
|
|
Issue #6764
|
|
Now that we use Qt5, we should do that. It is slightly more efficient
and declares the intent.
(Modified using clazy)
|
|
|
|
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.
|
|
src/gui/main.cpp:112:9: warning: bool literal returned from 'main' [-Wmain]
Used 1 to keep previous behaviour. I supposed the code was meant
to return success (0), but it does not really matter anyway.
|
|
|
|
Use qCInfo for anything that has general value for support and
development. Use qCWarning for any recoverable error and qCCritical
for anything that could result in data loss or would identify a serious
issue with the code.
Issue #5647
|
|
This gives more insight about the logs and allow setting fine-tuned
logging rules. The categories are set to only output Info by default
so this allows us to provide more concise logging while keeping the
ability to extract more information for a specific category when
developping or debugging customer issues.
Issue #5647
|
|
Also don't use dynamic_cast
For enterprise/#689
|
|
This was removed in 0194ebb2229adc33f5b9790231a3384b46474bde
because it breaks on Linux. However, it looks like it is correct
for Windows. In the meantime the surrounding ifdef has changed
from !Q_OS_MAC to Q_OS_WIN, so reverting it makes sense.
|
|
Setting the Environment variable only for owncloud makes in inconsistant with
other Qt application running at the same time.
The users can still set it themself for the whole desktop if they wish.
Addresses #4840
|
|
This seems to be broken. Worst case users can still
set it manually
Addresses #4840
|
|
|
|
|
|
Use QT_DEVICE_PIXEL_RATIO=auto on Qt<=5.5 to enable automatic
scale factor settings on Windows. Also move the existing
Qt::AA_EnableHighDpiScaling logic to use the equivalent
QT_AUTO_SCREEN_SCALE_FACTOR=1 environment variable just to
keep the 5.5 and >=5.6 code at the same place.
|
|
For #3273 #3771 #3485
See also d503221b2e22109eb9f2a3d875dcd247dd8b4cf9
|
|
Conflicts:
src/gui/application.cpp
src/gui/owncloudsetupwizard.cpp
|
|
|
|
It simply prints the version of the client and exists.
|
|
This moves the crash handler installation during the OCC::Application
contruction. This still leaves a window where crashes wouldn't be
caught, leaving the QtSingleApplication and theme initialization
code unreported, but isn't requiring any refactoring for now.
Issue #2952
|
|
The config currently only disable the reporter, but still leaves
the crash handler installed on startup. This causes conflicts
when running those builds in lldb.
Work around the issue by requiring the crash reporter to be
disabled in the settings before owncloud can be run in lldb.
This has the negative side-effect of not covering the
initial ConfigFile loading with the crash handler.
Issue #2946
|
|
sendMessage would only be called if there were options to
be sent to the running application.
Fix the issue by having explicitly named messages and always
send the show settings message.
Issue #2374
|
|
Helps for tasks #1138, #2023, #2123
|
|
|
|
|
|
Conflicts:
CMakeLists.txt
src/gui/main.cpp
src/libsync/accessmanager.cpp
src/libsync/accessmanager.h
src/libsync/owncloudpropagator_p.h
|
|
Conflicts:
src/libsync/utility.cpp
src/libsync/utility.h
|
|
|
|
Conflicts:
src/CMakeLists.txt
src/cmd/cmd.cpp
src/gui/socketapi.h
src/libsync/syncengine.h
test/CMakeLists.txt
|
|
|
|
|
|
|
|
|
|
|
|
|
