Flow.Launcher icon indicating copy to clipboard operation
Flow.Launcher copied to clipboard

After a plugin is successfully installed, the FL's Setting dialog is not restored to the foreground.

Open raindropsfromsky opened this issue 2 years ago • 14 comments

Describe the bug/issue After a plugin is successfully installed, the FL's Setting dialog is not restored to the foreground. If I press ALT+TAB, I can see the Flow.Launcher task. But if I select it, the dialog does not appear even if I wait for a very long time.

To Reproduce Steps to reproduce the behavior:

  1. In Settings, select the Plugin Stores tab.
  2. Install a plugin.
  3. Let the download and installation notification pop up.
  4. After a decent interval, the FL's Settings window should be restored.
    but it does not re-appear even after a long time.
  5. Press ALT+TAB. You can see the FL task in the display. Press ALT+TAB sufficient times to switch to it.
    We expect the FL window to appear in the foreground. But it does not appear at all.

Screenshots image

Your System Windows 10 Home, 64 bits. Version 10.0.19044 Build 19044

Flow Launcher version: ver 1.10.0 portable

Flow Launcher Error Log

Since I am using a portable version, I looked for the UserData subfolder.
Unfortunately there is no such subfolder.
My path resolves to C:\Users\naray\AppData\Local\FlowLauncher\app-1.9.3
This path does not have any files or subfolders named "logs".

Drag and drop the log file below this comment. No log files are generated!

raindropsfromsky avatar May 07 '22 15:05 raindropsfromsky

Update: Since FL's window did not re-appear even after a long wait, I right-clicked on FL's icon in the system tray and selected settings.

This created a separate window of FL Settings. The original FL Settings window is still hung. If I press ALT+TAB, I see two FL windows: One is hung, and the other is active.

image

raindropsfromsky avatar May 07 '22 15:05 raindropsfromsky

When you install a plugin, Flow restarts which is why it doesn't go back to the settings window you had open.

deefrawley avatar May 09 '22 02:05 deefrawley

oh ok.

But then why does the older instance stay in the ALT+TAB thumbnails? BTW I just noticed that the FL's thumbnail is very wide as compared to the other thumbnails for other apps. Why is that?

raindropsfromsky avatar May 09 '22 07:05 raindropsfromsky

Do you have the hide after start up option enabled in Flow's settings? This means the search bar won't pop up after flow starts up or restarted. Also when flow is installing a plugin, it maybe that the download process took a while and then when it finally restarted it doesn't pop up?

If the setting is enabled to hide, can you switch to disabled and try installing a plugin, at least this way you will know when it exactly finishes installing plugin and restarted.

If still a problem, let me know what plugin you tested.

jjw24 avatar May 10 '22 09:05 jjw24

Yes, indeed! FL is supposed to start minimized in SysTray.

I found the error message in my notification tray: image


But this issue may not be related to this specific plugin, but how FL handles the restart workflow when a plugin fails to install (it is unable to handle an exception).

Reason: When the earlier instance is killed, the ALT+TAB thumbnails should stop showing its task. And since ALT+TAB does not show apps running in SysTray, the thumbnails should stop showing FL's thumbnail.

But this does not happen:
(a) FL's thumbnail does appear in the ALT+TAB ribbon (b) This thumbnail is blank. (c) If we select this thumbnail, the app does not come to the foreground.

So there are three separate issues, apparently with the restart logic (not related to a specific plugin).

raindropsfromsky avatar May 10 '22 13:05 raindropsfromsky

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Jun 15 '22 02:06 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Aug 01 '22 02:08 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Sep 16 '22 02:09 github-actions[bot]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] avatar Sep 24 '22 02:09 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Nov 11 '22 02:11 github-actions[bot]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] avatar Nov 19 '22 02:11 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Mar 22 '23 01:03 github-actions[bot]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Dec 14 '23 01:12 github-actions[bot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

github-actions[bot] avatar Feb 16 '24 01:02 github-actions[bot]