Starting client while already running sometimes doesn't show settings window

[lazawan]

steps to reproduce :
after client-configuration and client runs properly :

• go to tray-icon in taskbar and quit owncloud
• doppel-click on owncloud-icon on Desktop >> nothing opens just owncloud-client is started in background and tray-icon in taskbar appears again
• again doppel-click >> nothing happens
• again doppel-click >> now owncloud-window opens

regards

windows 10 client 2.5.3rc1

[ckamm]

It's intentional that starting the client usually doesn't lead to a window popping up. We don't want the settings window to be shown every windows startup.

What's odd is that the second time you start the client nothing happens. The intended behavior is that starting the client while it's already running will lead to the settings window popping up.

[guruz]

Maybe some windows popup protection?
Moving to 2.6.1 though

[ogoffart]

There is a 10 second delay from startup for which we won't show the settings:

client/src/gui/application.cpp

Lines 523 to 529 in e82dc14

	qCInfo(lcApplication) << "Running for" << _startedAt.elapsed() / 1000.0 << "sec";
	if (_startedAt.elapsed() < 10 * 1000) {
	// This call is mirrored with the one in int main()
	qCWarning(lcApplication) << "Ignoring MSG_SHOWSETTINGS, possibly double-invocation of client via session restore and auto start";
	return;
	}
	showSettingsDialog();

The reason is that some auto-start script tends to start the application twice :-/

[guruz]

session restore and auto start

That's a linux thing though?
Or I heard that Windows might do this too?

In general, our auto start setting could in theory launch the client with something like --from-autostart and then adjust behaviour somehow?
But maybe this is all not worth the trouble.

[HanaGemela]

@TheOneRing is this issue fixed? There isn't ReadyToTest label
If it is fixed, could you specify the expected result here? When should settings dialog open?

[TheOneRing]

I don't think so it would probably require changes to the installer to invoke the client with a -s

[TheOneRing]

Adopt desktop files and windows shortcuts to pass -s to the client.

[TheOneRing]

@ogoffart @guruz 641dece so the code was introduced to fix the issue on linux.
Do you know whether this was also an issue on mac?
I'd like to make the elapsed code linux only, as passing a -s if a user invoked it is easy.
As far as I can tell it is not possible to pass an argument on mac.

[jnweiger]

PR #7784 fixes this issue for me.
It nicely implements the general UX-rule that every user interaction should have an immediate reaction.
Regarding Windows and Mac: do we do the same there?

[HanaGemela]

What is the expected results for macOS?

Current behaviour:
Windows - setting window opens on every double click
macOS - setting window never opens on double click
Linux - setting window opens on every double click

[michaelstingl]

macOS - setting window never opens on double click

Okay for now 👍