Summary: | Open new files in tabs does not work in windows | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | ric <ric.richter86> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | 532032961, 594156193, aacid, acrylint, aj520418, asefshahriar75, bugzilla123, d0rf3n, heinz5634, jacques.doubell, justenjoy034, random1123581321, serkonda7, yhd1km, zhaolinlau |
Priority: | HI | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
ric
2019-05-15 05:57:32 UTC
same problem in windows 10 and flatpak installed okular in debian 10 Still same problem. Opening another/or same pdf in file explorer opens new instance. Opening through File -> Open... opens in new tab or switches to open file. Okular 20.12.2 Windows 10 Related to this issue on github, though I don't use flatpak: https://github.com/flathub/org.kde.okular/issues/36 *** Bug 435994 has been marked as a duplicate of this bug. *** *** Bug 436387 has been marked as a duplicate of this bug. *** SUMMARY `Open new files in tabs` works only from inside of Okular STEPS TO REPRODUCE 1. Double-click on .pdf file in File Manager OBSERVED RESULT it opens it in a new Okular Window EXPECTED RESULT it opens it in a new tab SOFTWARE/OS VERSIONS Windows: 11 (In reply to aj520418 from comment #5) > SUMMARY > `Open new files in tabs` works only from inside of Okular > > STEPS TO REPRODUCE > 1. Double-click on .pdf file in File Manager > > OBSERVED RESULT > it opens it in a new Okular Window > > EXPECTED RESULT > it opens it in a new tab > > SOFTWARE/OS VERSIONS > Windows: 11 Okular version 22.04.0 *** Bug 442763 has been marked as a duplicate of this bug. *** *** Bug 451826 has been marked as a duplicate of this bug. *** *** Bug 456480 has been marked as a duplicate of this bug. *** *** Bug 462704 has been marked as a duplicate of this bug. *** This still doesn't work. Why isn't it being fixed? Thanks (In reply to bugzilla123 from comment #11) > This still doesn't work. Why isn't it being fixed? > Thanks This is open source. It's fixed if someone volunteers to do it. *** Bug 466225 has been marked as a duplicate of this bug. *** Faced the exact same problem with all versions provided by the website namely: Windows store (23.08.1), nightly stable (23.08.04) and nightly experimental (24.01.80) build. I managed to build the newest version from source myself (24.07.70) and with that version the problem was not there. I followed a wiki entry for building KDE connect on Windows using Visual Studio and craft without modifying any settings or source code. (https://community.kde.org/KDEConnect/Build_Windows) I also build it with QT6, whereas the other versions used QT5. However, I don't know what resolved the matter (build settings, newer Okular version, newer QT version,...). (In reply to yhd1km from comment #14) > Faced the exact same problem with all versions provided by the website > namely: > Windows store (23.08.1), nightly stable (23.08.04) and nightly experimental > (24.01.80) build. > > I managed to build the newest version from source myself (24.07.70) and with > that version the problem was not there. I followed a wiki entry for > building KDE connect on Windows using Visual Studio and craft without > modifying any settings or source code. > (https://community.kde.org/KDEConnect/Build_Windows) I also build it with > QT6, whereas the other versions used QT5. > > However, I don't know what resolved the matter (build settings, newer Okular > version, newer QT version,...). Potentially you built and run dbus which would make it work, but we don't ship dbus with Okular because it's a bit messy. One potential solution is to use https://github.com/KDAB/KDSingleApplication instead of dbus stuff to make the "should i start myself or attach to another app" logic. |