always_open_in_new_window doesn't work on linux(?)

[PorkingMane]

Reproduced on latest main

• I have reproduced this on the latest main branch.

Searched existing issues

• I have searched existing issues for duplicates.

Custom configuration used

• I am using custom configuration.

Custom configuration

I added always_open_in_new_window=false in my config.toml file on CachyOS, but instead of every file opening in the same window its just creating a new Lektra instance if I open files directly, one by one, through file manager and not console.

I tried to change .desktop file and associations to manually route them into one window, but it doesn't work either

I may misunderstood how this flag works, but I think this should be a native feature if this config option is present, so no matter how user opens files - they should be in the same launched instance.

Willing to contribute

• I am willing to submit a pull request for this.

OS

CachyOS 7.0.1 | Plasma 6.6.4

Qt version

6.11

Steps to reproduce

1. Make Lektra default image viewer with always_open_in_new_window=false config option
2. Open first file through file manager or console, it opens a singular Lektra instance
3. Open second file through file manager or console, it opens another Lektra instance instead of grouping them into one

Expected behavior

Every image/file should be open in a singular instance

Actual behavior

Opens a new window each time

Logs / screenshots

[dheerajshenoy]

Thanks for reporting this issue.
Unfortunately, that flag was designed for when you try to open files from within LEKTRA that would then open up in a new window instead of being added as a new tab. Which means it's not related to what we think it is. That flag is unnecessary, so I think it's best to remove it.

With regards to what actually should've been the behavior, I am working on implementing an Interprocess Communication (IPC) mechanism so that when opening new files, it would detect the running instance and open it there instead of in a new window.

TL;DR; It's not implemented yet, that flag is deprecated and was supposed to be used for something else entirely.