[kwin] [Bug 445587] New: Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Bug ID: 445587 Summary: Response to mouse clicks broken Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Since today's kde/qt updates, the Overview effect does not respond to mouse clicks anymore. (This used to work correctly prior to the update.) STEPS TO REPRODUCE 1. Trigger the Overview effect (e. g. using active corner or shortcut) 2. (Left-)click on the area of a window OBSERVED RESULT Nothing happens. EXPECTED RESULT The effect should be closed and the clicked window should be shown. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Might be Wayland-only. I haven't used X since a longer time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Manuel Geißer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #1 from Manuel Geißer --- Created attachment 143622 --> https://bugs.kde.org/attachment.cgi?id=143622&action=edit Screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #2 from Manuel Geißer --- Same problem on X - I have made you a screencast. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #3 from Manuel Geißer --- By the way, the purple description background is really strange. That's only on X, not on Wayland, though. Is this on purpose, or should I file a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #4 from Manuel Geißer --- Created attachment 143624 --> https://bugs.kde.org/attachment.cgi?id=143624&action=edit Update log -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] New: Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027
Bug ID: 442027
Summary: Variables inside f-strings are not highlighted and not
recognised for renaming
Product: kdev-python
Version: 5.6.2
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: geisse...@gmail.com
Target Milestone: ---
SUMMARY
In Python 3.6 f-strings got introduced. They're a simple and well-readable way
to include variables in messages. If a string is preceded with an f character,
variables can be stated inside curly brackets and will automatically get
formatted as a string.
Example:
```python3
x0 = 5
y0 = 20
multiplied = x0 * y0
message = f"Position: ({x0}, {y0}); multiplied {multiplied}"
```
There are lots of nice guides concerning f-string, e. g.
https://www.geeksforgeeks.org/formatted-string-literals-f-strings-python/
Variables inside the f-string curly brackets are apparently not recognised by
KDevelop. There is no syntax highlighting for these variables and they are also
not considered for renaming operations. Renaming either of `x0` or `y0` in the
above example would ignore the occurrence inside the f-string.
This is a likely cause for UnboundLocalErrors: The user renames the variable,
clicks on KDevelop's auto-rename feature and thinks all variables are replaced,
but suddenly the code crashes at f-string formatting becaues the old variable
name is still there.
STEPS TO REPRODUCE
1. Paste any f-string code into KDevelop, for instance the above example. Save
the file for highligthing and semantic analysis to get active.
2. Rename a variable, e. g. `x0` to `xpos`
3. Use the auto-rename feature
OBSERVED RESULT
- Variables inside f-strings are not highlighted
- While all occurrences of a variable outside f-string are replaced properly,
the occurrences inside f-string curly brackets are ignored.
EXPECTED RESULT
- Variables should always be highlighted, also inside f-strings
- Renaming operations should also replace occurrences of the variable in
f-strings
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
/
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #1 from Manuel Geißer --- outside f-string*s -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] New: [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Bug ID: 442029 Summary: [Feature request] Add file exclude options for quick open Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: QuickOpen Assignee: kdevelop-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Quick open is a useful feature. However, I am missing an option to exclude certain directories or file extensions. For example, my repository contains Sphinx documentation, and quick open also shows all documentation build artifacts. This can be quite problematic: If I have a file named `api.rst`, building the docs would also generate an artifact named `api.rst.txt`. Now it could happen that you accidentally open and edit the `.txt` file which has the same content as the `.rst` equivalent, but it will be overwritten with the next build cycle and all changes are lost. So it would be quite helpful to be able to exclude the build directory from quick open, not only to prevent inadvertently opening the wrong file, but also to get a cleaner overview. My quick open panel is often spammed with compiled objects. STEPS TO REPRODUCE 1. Clone a repository that contains Sphinx documentation 2. Import it into KDevelop 3. Build the documentation (`make html`) 4. Trigger quick open OBSERVED RESULT All documentation build artifacts will show up. EXPECTED RESULT Only relevant project files should be displayed. Therefore, an option in the settings would be required to exclude certain file types or directories. (Alternatively, though more complex, it could also be possible to read the .gitignore file and not show objects that aren't part of the revision control, but as KDevelop also supports versioning systems other than git this might not be a straightforward solution.) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Since KDevelop is a large application, the option I am requesting might already exist at some hidden place. If so, please point me at it and forgive the false issue :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #3 from Manuel Geißer --- Thanks for the response. Unfortunately I can't contribute to KDevelop myself, as I only know Python an no C++. I'm currently learning PySide2 but my Qt skills are still very limited. I also don't have the time to get my feet wet on a new software project at the moment... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #2 from Manuel Geißer --- Aha, thank you! I only searched the settings and the plugin, but overlooked the project configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #4 from Manuel Geißer --- Thanks for the help! I'm rather new to KDevelop and haven't unraveled its full capabilities yet. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] New: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Bug ID: 442226 Summary: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions Product: kate Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 141422 --> https://bugs.kde.org/attachment.cgi?id=141422&action=edit Pop-up window SUMMARY When typing in a string into either of the "Search" or "Replace" fields, there are sometimes strange floating windows instead of a dropdown menu for completition propositions. These windows are rather annoying, because they steal focus from the text input field. Then I usually press ESC with the intention to get rid of the pop-up, but instead it closes the search/replace plugin... I think this issue affects Wayland only. STEPS TO REPRODUCE 1. Open Kate 2. Open the "Search and Replace" plugin 3. Type in a string into the "Search" or "Replace" field 4. Keep editing the text until the bug occurs. OBSERVED RESULT Sometimes a separate, centered pop-up window appears instead of a dropdown menu. EXPECTED RESULT There should never be pop-ups for this. It should always be a dropdown menu. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-34-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added Keywords||regression, wayland CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #2 from Manuel Geißer --- It is "regression from earlier on wayland". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] New: Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
Bug ID: 442280
Summary: Okular does not take /UserUnit into account (page size
incorrect)
Product: okular
Version: 21.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: PDF backend
Assignee: okular-de...@kde.org
Reporter: geisse...@gmail.com
Target Milestone: ---
Created attachment 141453
--> https://bugs.kde.org/attachment.cgi?id=141453&action=edit
userunit_10.pdf
SUMMARY
[PDF background]
In the PDF format, coordinates are given in PDF points, where by default 1
point is equivalent to 1/72 of an inch (1in -> 2.54cm). However, PDFs can
define custom units on a per-page basis, using the /UserUnit key.
/UserUnit is a float or decimal that scales the default conversion fraction of
1/72, so for a /UserUnit of 10, 1pt would mean 10/72in.
[What Okular does]
It seems that Okular (like many other open-source PDF software) does not take
/UserUnit into account for the displayed page size.
The attached test document `userunit_10.pdf` defines a /UserUnit of 10.
The document's /MediaBox looks like this:
```python3
[ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'), Decimal('1785.6')
```
Now the default conversion with 1pt -> 1/72in returns 630x630mm, which is what
Okular displays. However, this is incorrect. In reality, the size is 6300mm, 10
times larger!
(In particular, /UserUnit is used by Adobe Illustrator and possibly other PDF
software to circumvent the maximum number of 14400pt imposed by Adobe Reader
and some other PDF renderers.)
STEPS TO REPRODUCE
1. Open the attached file in Okular
2. Go to File -> Properties
3. See the displayed page size
4. Inspect the document with the pikepdf python library, or and other PDF
library of your choice
5. Print the /MediaBox and /UserUnit of page 0
OBSERVED RESULT
Displayed page size is too small by factor 10.
EXPECTED RESULT
Displayed page size should always reflect the real page size and take /UserUnit
into account.
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-34-generic (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC||aa...@kde.org, ||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 --- Comment #1 from Manuel Geißer --- Ping. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #1 from Manuel Geißer ---
Python shell code to reproduce (replace TestFiles.userunit_10 with the path
string where you saved the file, and skip the first import which depends on
custom test infrastructure of the lib I am developing):
```python3
Python 3.8.10 (default, Jun 2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from tests_pdfnodegraph.testfiles import TestFiles
>>> import pikepdf
>>> pdf = pikepdf.Pdf.open(TestFiles.userunit_10)
>>> page = pdf.pages[0]
>>> page.MediaBox
pikepdf.Array([ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'),
Decimal('1785.6') ])
>>> page.UserUnit
Decimal('10.0')
>>> 1785.6 * 1/72 * 25.4
629.91998
>>> 1785.6*10 * 1/72 * 25.4
6299.2
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #2 from Manuel Geißer --- Created attachment 141454 --> https://bugs.kde.org/attachment.cgi?id=141454&action=edit userunit_screenshot -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #3 from Manuel Geißer --- To clarify, I think it is not only the displayed size number that is incorrect, but also the space reserved for rendering the actual page: The screenshot I just added illustrates it better: The first page is from the userunit_10 file. The other 2 pages are ANSI A and A4 size, which is very roughly 200mm width - put one of the smaller pages three times next to each other, and it approximately matches the width of the larger page, although in fact it should be a lot larger - roughly thirty times the width of the smaller page! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #4 from Manuel Geißer --- > the space reserved for rendering the actual page or better formulated: the proportions of different pages to each other -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #5 from Manuel Geißer ---
Created attachment 141455
--> https://bugs.kde.org/attachment.cgi?id=141455&action=edit
Proportions pdf
For you to confirm the UserUnit is set on the first page of the document in the
screenshot, but not on the other pages.
```python3
>>> from tests_pdfnodegraph.pathtools import TestOutput
>>> pdf = pikepdf.open(join(TestOutput,'out_14.pdf'))
>>> page = pdf.pages[0]
>>> page.UserUnit
Decimal('10.0')
>>> page_2 = pdf.pages[1]
>>> page_2.UserUnit
Traceback (most recent call last):
File "", line 1, in
File "/home/manuel/.local/lib/python3.8/site-packages/pikepdf/_methods.py",
line 1143, in __getattr__
return getattr(self.obj, name)
AttributeError: /UserUnit
>>>
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added Summary|Okular does not take|Okular does not take |/UserUnit into account |/UserUnit into account |(page size incorrect) |(page size incorrect for ||certain files) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #6 from Manuel Geißer --- List of other affected PDF software: * Chromium integrated PDF viewer (uses PDFium) * Firefox integrated PDF viewer (uses pdf.js) * Inkscape PDF importer (uses Poppler) * Scribus PDF importer * PDFStitcher (uses pikepdf) * PDF Arranger (uses pikepdf) * even the proprietary Master PDF Editor 4 and 5 Probably more ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #7 from Manuel Geißer --- Created attachment 141456 --> https://bugs.kde.org/attachment.cgi?id=141456&action=edit adobe_reader ... only Adobe Reader gets the proportions right -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #9 from Manuel Geißer --- Sorry. I just thought you'd be the maintainer of Okular, and wondered why you are not in the CC list, but apparently this has its reason. Sorry, really. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #11 from Manuel Geißer --- Pdfinfo from poppler-utils does not show regular units like centimetres or inches, but it keeps the PDF points. Pdfinfo is a low-level tool that does not perform unit conversion on its own. However, it does not display the UserUnit value, so you could say it's somewhat wrong in the sense that it withholds information. So to judge who is at fault, it would be relevant to know how Okular obtains the displayed page size. Does it inspect CropBox/MediaBox and convert to units itself, or does it retrieve finished unit values from Poppler? In the first case, the source of the bug would be in Okular, in the second case it would be in Poppler. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #12 from Manuel Geißer --- I've searched a bit in the code, and at least the rendering proportions issue is Okular's fault I think: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L721 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #13 from Manuel Geißer --- Another possibly relevant code passage: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L1303 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #15 from Manuel Geißer --- >From the referenced code we can see that Okular uses the Poppler::Page::pageSizeF() function to obtain the page size: https://poppler.freedesktop.org/api/qt5/classPoppler_1_1Page.html#a598c287971839a113552176fc387ab30 This function is based on CropBox and returns points. What about the following solution: - the pageSize() and pageSizeF() functions should be changed to take /UserUnit into account, as the docs suggest the returned value is always given in 1/72in units - Additionally there should be some way to obtain the /UserUnit value with poppler. I couldn't find any such option in the documentation, though I only skimmed it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #16 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. Be careful - there are considerable differences between these libraries. I don't really know about pdf.js and PDFium, but pikepdf is quite low-level and does not provide a function to obtain page size on its own - this needs to be done downstream using CropBox/MediaBox, UserUnit, and Rotate. > There is also a muPDF backend for Okular. Did you try that? `mutool info > userunit_10.pdf` reports `[ 0 0 17856 17856 ]`. Yes, I am aware that MuPDF directly takes /UserUnit into account. I noticed this during the tests for my lib (which also has a (Py)MuPDF rendering backend). How do I obtain the MuPDF backend for Okular, though? Is it possible that KDE Neon does not provide it? (I already have the okular-extra-backends package installed...) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #17 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. I think it might be better if the Okular developers would report to Poppler, since I never used the Poppler library interface myself and thus don't have the required background. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #18 from Manuel Geißer --- > I think it might be better if the Okular developers would report to Poppler, > since I never used the Poppler library interface myself and thus don't have > the > required background. I now filed an issue at Poppler nevertheless, as nobody else seems to have felt any responsibility to do so. The report essentially just references this thread, as it should contain all relevant information. https://gitlab.freedesktop.org/poppler/poppler/-/issues/1139 @OkularDevelopers: Please verify/confirm whether changing pageSize() and pageSizeF() would really be sufficient to fix the UserUnit issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #19 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? The Ubuntu Focal mupdf package currently fails to open the file (https://bugs.launchpad.net/ubuntu/+source/mupdf/+bug/1943366). This likely is fixed in newer versions of mupdf or affects the MuPDF GUI only, though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442900] New: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation
https://bugs.kde.org/show_bug.cgi?id=442900 Bug ID: 442900 Summary: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation Product: frameworks-syntax-highlighting Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- SUMMARY Many Python projects use inline code documentation with sphinx-autodoc, since this is a lot less maintenance work than separate code documentation. This way, it is much easier to keep code and docs consistent, especially as method parameter headers are generated automatically. STEPS TO REPRODUCE 1. Open a Python file with inline Sphinx reStructuredText documentation in Kate OBSERVED RESULT The Python code is syntax-highlighted. The inline rst markup is not highlighted, however. EXPECTED RESULT It would be nice to have optional rst syntax highlighting for inline code documentation indicated with `""" documentation text here """`. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-36-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Perhaps this idea is a bit far-fetched and/or hard to implement, so this is really just a suggestion. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #19 from Manuel Geißer --- Not sure whether the driver really is the cause. Yes, it may be possible, but I think you shouldn't rule out a cause in Plasma or Qt without further investigation. I'd rather not consider this issue resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #21 from Manuel Geißer --- Switching the compositing method does not affect the bug in any way. I already tried that long ago... I rather thought in the direction of a damaged configuration file issue. I've already had that a few times. If it were random rendering glitches, I would also suspect the graphics driver, but the issue with transparent instead of black background is so systematic that this seems kind of unlikely to me. However, I will file a bug with the graphics developer when I have time. I also thought of reinstalling the system at some point and see whether that fixes some of my impossible-to-reproduce issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #23 from Manuel Geißer --- > Present Windows effect is what is causing the issue here. Disabled it and I > can > see the background once again. Wow, good catch! Disabling Present Windows indeed solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #20 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? Is this at all still current? I checked out okular from https://invent.kde.org/graphics/okular.git and built with CMake, but couldn't find any hints on a MuPDF backend. `ls generators/` only shows ``` chm CMakeLists.txt comicbook djvu dvi epub fax fictionbook kimgio markdown mobipocket plucker poppler spectre tiff txt xps ``` -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #21 from Manuel Geißer --- `grep -r mupdf` on the Okular source tree doesn't find anything, either -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #23 from Manuel Geißer --- I guess you are referring to https://invent.kde.org/sandsmark/okular-mupdf-backend ? The thing is, there are multiple unofficial Okular MuPDF generators around... Moreover, why is this not officially part of Okular and not packaged in Debian, Ubuntu, and KDE Neon? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #24 from Manuel Geißer --- So I installed the dependencies and tried to build okular-mupdf-backend (from git master), but it fails with some "Variable not declared in this scope" error. Also there have been no commits to the repository since a year. Is this backend still functional? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #25 from Manuel Geißer --- Created attachment 142205 --> https://bugs.kde.org/attachment.cgi?id=142205&action=edit (unrelated) okular-mupdf-backend build error -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #27 from Manuel Geißer --- Sure. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #4 from Manuel Geißer --- I think this is perhaps rather an issue with Qt(-Wayland) than with Kate -- A question: Is it possible to deactivate completition, or dismiss the completition history as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #91 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Yeah, if developers had acknowledged what an annoyance this dimming is, they could just have commented out the problematic line and release an updated package nine years ago, or they could have merged PR 885 five months ago... It appears that fixing usability issues is just regarded as an unimportant side-effect of the Present Windows replacement; primarily it's just the move to a different underlying technology. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #93 from Manuel Geißer --- > What do you mean? Nate said the effect is being shipped with Plasma 5.23 > though > it "may" (which I guess is now "will") not replace it until later. Is this > wrong? The problem we're talking about is that it will take even longer for this usability issue to be fixed, due to Plasma 5.23 getting additional months of polishing and QA. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #95 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Well, actually that turns out to be wrong. It got released today (that is, in KDE Neon). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423551] Regression in some XWayland popups
https://bugs.kde.org/show_bug.cgi?id=423551 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #3 from Manuel Geißer --- Well, I sometimes experienced this issue with xwayland Firefox on current KDE Neon User, for instance with the popup for creating new bookmarks. If it happens, the only thing that helps is to terminate the whole program, otherwise the popup is still visible on top of all other applications. I'm now using native wayland firefox which doesn't have those problems. Are you sure this issue regarding xwayland popups is fixed in newer versions? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423551] Regression in some XWayland popups
https://bugs.kde.org/show_bug.cgi?id=423551 --- Comment #4 from Manuel Geißer --- This issue didn't occur always for me, it's rather seldom; I couldn't figure out yet under which cirucumstances it happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #396 from Manuel Geißer --- This discussion/dispute is fairly overwhelming, it somehow reminds me of the alt/meta key trouble (https://bugs.kde.org/show_bug.cgi?id=399375). That being said, I'd really like different wallpapers for virtual desktops. If I understand this thread correctly, then that is also what most users would prefer. One reason why activities are not a replacement for virtual desktops is indeed the 'desktop grid / parachute' functionality. I personally don't think activities and virtual desktops should be merged - they have different purposes and can well coexist and be used together (that is at least my impression). Could you maybe explain clearly what makes it so difficult to have different wallpapers for virtual desktops? I guess this thread has become such a controversy mostly because some users think this is a trifle to add. As a long-term goal, it would be nice if something like Parachute or the Win10 windows overview page could be added to plasmashell natively, combining activities and virtual desktops in a nice and coherent UI (and supporting Wayland well), but that wish is probably far away... I'd be interested in opinions from the Visual Desktop Group (@VDG) on this topic. Maybe that has already been considered, but I find it difficult to overview the vast landscape of design discussions, issues and feature requests. See also: https://github.com/tcorreabr/Parachute/discussions/29 https://phabricator.kde.org/T13037 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #21 from Manuel Geißer --- Johann Höchtel's fix works for me, many many thanks ;) ! Since I'm pretty reliant on compose and dead key input methods, I wouldn't be able to use Wayland otherwise. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #2 from Manuel Geißer --- Yeah, I can confim that - It even seems to depend on the python-is-python2 symlink regulation package... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] New: Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 Bug ID: 433056 Summary: Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates) Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: geisse...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Before the updates from 16th Feb afternoon, when holding down a key for a longer time, it got correctly interpreted as repeated key presses, so that holding down a key would repeat that character or action with a fixed speed as long as the key is pressed. This is very useful for del/backspace in particular and definetely the desired behaviour. Yesterday's updates to Plasma 5.21 broke that. Holding down a key only triggers the action one time, and does not recognise that it should actually be repeated. I personally find this behaviour rather disturbing for my workflow. STEPS TO REPRODUCE 1. Use up-to-date KDE Neon User 2. hold down a key (space or backspace, for instance) -> the action won't be repeated as it should OBSERVED RESULT When holding down a key, it gets interpreted as one single key press and is not repeated EXPECTED RESULT While a key is held down, its actions should be repeated. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Graphics Platform: Wayland ADDITIONAL INFORMATION Both Wayland and X11 are affected My input method is set to ibus as described in https://bugs.kde.org/show_bug.cgi?id=411729#c4 (but reverting the environment variables related to ibus didn't change anything) Since I have no clue which of the many packages updated with the move to Plasma 5.21 is causing this bug, I decided to report this here in Neon issues. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] New: No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 Bug ID: 433071 Summary: No background Wallpapers in Desktop Grid on Wayland Product: kwin Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 135762 --> https://bugs.kde.org/attachment.cgi?id=135762&action=edit no wallpapers shown SUMMARY Wallpapers are black/invisible in the Show Desktop Grid effect (on Wayland only, Screenshot attached) STEPS TO REPRODUCE 1. Login to a Wayland session 2. Trigger the "Show Desktop Grid" effect (via button or keyboard shortcut) -> the open windows of the various virtual desktops are visible, but not the backgrounds/wallpapers, they're just black. OBSERVED RESULT black/no Wallappers in Show Desktop Grid effect on Wayland EXPECTED RESULT Wallpapers should show up correctly for all virtual desktops, as they do in X11 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Graphics Platform: Wayland ADDITIONAL INFORMATION The Present Windows effect correctly shows the wallpaper -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 --- Comment #5 from Manuel Geißer --- Indeed, it had already been fixed. Sorry I failed to notice the update because I uninstalled it as I saw it depends on python-is-python2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 --- Comment #2 from Manuel Geißer --- Hmm, then maybe this is related to ibus nevertheless - I guess I forgot to reboot after taking out the environment variables. I'll investigate that again. Did the updates modify anything regarding ibus or keyboard input in general? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 --- Comment #3 from Manuel Geißer --- I did some tests, here are the results: - the issue seems unrelated to ibus - after commenting out the environment variables and rebooting, there is no change - I created a new user and tried holding down a key, and it works correctly, which means this problem must have something to do with my configuration -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 --- Comment #4 from Manuel Geißer --- That is very very weird... Maybe I should just migrate to a new user, but still I'd like to know what is the cause of this. I think I don't have any unusual configuration... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 Manuel Geißer changed: What|Removed |Added Component|effects-window-management |effects-desktop-grid -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #1 from Manuel Geißer --- I created a new user account and tested it there - the bug doesn't happen, so this must probably be a configuration issue, although I have no clue why... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 --- Comment #5 from Manuel Geißer --- I am noticing now that something more general must have gone wrong yesterday - It almost seems like large parts of my configuration became invalid or something similar: The present windows button, the digital clock, and the virtual desktops widget have dramatically decreased and got unsharp. Moreover, on the attempt to switch users, I had two freezes today (which I never experienced before). Also, I do not have this bug https://bugs.kde.org/show_bug.cgi?id=433071 in the new testing user. After yesterday's update, I changed some preferences and tweaked my task bar etc., but without logging out and in again. Maybe this is the cause of all the trouble? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 Manuel Geißer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #10 from Manuel Geißer --- I can confirm that the issue is still present in Lokalize 20.12.2 (Qt 5.15.2, KDE Neon User). This unfortunately makes Lokalize basically unusable on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #2 from Manuel Geißer --- How strange. For me these strings are localised correctly (Plasma 5.22.4 / KDE Neon). When you installed your distribution, did you already choose German, or have you changed the system language afterwards? If the latter is the case, it might be caused by a missing locale package, perhaps. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 --- Comment #3 from Manuel Geißer --- The peculiar thing is that only the simple strings like undo/redo/cut/paste/... are not translated. Looks somehow like missing QtBase locale to me. Could you check whether more Qt-based programs than just Dolphin and KFind are affected, please? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 --- Comment #4 from Manuel Geißer --- Would you paste or attach the ouput of `ls /usr/share/qt5/translations`, please? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 --- Comment #5 from Manuel Geißer --- *output If `qtbase_de.qm` is missing, then we may have found the cause. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 --- Comment #8 from Manuel Geißer --- Nice! I think on KDE Neon the package is named `qttranslations5-l10n`. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 439040] Some strings in right click menus of input fields are not localized (Undo/Redo/Cut/Copy/Paste/Delete)
https://bugs.kde.org/show_bug.cgi?id=439040 Manuel Geißer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #13 from Manuel Geißer --- The issue still persists after today's kde software updates. I don't have the remotest idea what could be the cause :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 Manuel Geißer changed: What|Removed |Added Resolution|WAITINGFORINFO |LATER -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #15 from Manuel Geißer --- Created attachment 140711 --> https://bugs.kde.org/attachment.cgi?id=140711&action=edit Even the popup background is transparent (Discover) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #86 from Manuel Geißer --- Wow, thanks! When approximately will the QML present windows land in Neon User, and how does one activate it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #1 from Manuel Geißer --- No, please don't do this. I already argued about it on Present Windows (Bug 438905). Overlaying icons makes it harder to distinguish multiple instances of the same application. Reading texts takes too long and defeats the purpose of quickly getting an overview by what the windows look like. Users who recognise windows by title or icon can use the classical task bar (which is planned to be be interactive in the new Overview effect, right?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441314] Differentiating overview contents from desktop background
https://bugs.kde.org/show_bug.cgi?id=441314 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #1 from Manuel Geißer --- Most users may want to see their wallpaper for the Overview to be more pleasant and less dull. If using a dark theme, dimming the background will decrease the contrast to windows, thereby making it harder to identify the window you want to choose, or to get a quick overview. Using the panel background colour would also make it more difficult to distinguish the windows from the background, since the panel colour is similar to the widget/window background colour with most themes. So this would do exactly the contrary of what you want. After what happened to Present Windows, I'd be very reluctant to add any kind of dimming (Bug 303438). We don't want that flop again, really. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441314] Differentiating overview contents from desktop background
https://bugs.kde.org/show_bug.cgi?id=441314 Manuel Geißer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441314] Differentiating overview contents from desktop background
https://bugs.kde.org/show_bug.cgi?id=441314 Manuel Geißer changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 Manuel Geißer changed: What|Removed |Added CC||rula...@wp.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441314] Differentiating overview contents from desktop background
https://bugs.kde.org/show_bug.cgi?id=441314 Manuel Geißer changed: What|Removed |Added CC||rula...@wp.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #3 from Manuel Geißer --- > Yes, you can use the Task Manager for that, but you could use the Task > Manager > for everything. No, contrary to the Overview effect, window previews in the task manager are too small, and you don't have the overview of all applications' contents at once. Task manager -> icon-based app management Overview -> *quick* identification of apps by content There is no other possibility to quickly distinguish windows by content except for the Overview effect. Please don't make it unusable with icon overlays. As a side-node, no other operating system or desktop environment that I know of uses icon overlays in their overview effect. Moreover, icons are already visible in the top-right corner of the application, which should be enough. > The point is to make the Overview effect usable for as many people with as > many use cases as possible. Destroying the primary use case and purpose of **identifying windows by content and getting an overview** doesn't make it more usable to anyone, frankly. One component should do one thing, and do it well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441314] Differentiating overview contents from desktop background
https://bugs.kde.org/show_bug.cgi?id=441314 --- Comment #3 from Manuel Geißer --- > though it will cause issues in cases where a user has disabled blur or > hardware > doesn't support it Blur, provided it is only applied to the wallpaper and not to windows, seems a better approach to me. It could be configurable in the effect's settings, rather than using the global setting. I expect graphics hardware not supporting blur is a very improbable scenario? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #4 from Manuel Geißer --- > top-right Whoops, top-left of course. Apparently I've got a right-left weakness :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #6 from Manuel Geißer --- > Titles can be under windows and icons in windows corner so that they don't > cover window preview. That's a good suggestion. What I just want to prevent is that icons/titles are made as obtrusive as they were in Present Windows lately. The content of small windows was basically not visible due to being covered by an over-large icon+text, with the rest of the window strongly dimmed, which was annoying... > Take into account that there are users who still use relatively small screens > and as a consequence preview windows become small. Yep, I'm using such an old, smaller monitor with awkward 5:4 aspect ratio. In spite of this, its stability and visual quality are excellent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #7 from Manuel Geißer --- > [...] and as a consequence preview windows become small. That's exactly why I dislike overlays on top of windows so much. They hide content of previews which are rather small already, making it even harder to identify the window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #8 from Manuel Geißer --- Created attachment 141003 --> https://bugs.kde.org/attachment.cgi?id=141003&action=edit Too large overlays Here's an example from the old Present Windows that should illustrate the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #10 from Manuel Geißer --- Oh, indeed it's optional in Present Windows! I never noticed that. What a blunder. Did that option get added recently, or did I just overlook it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 441540] New: [python3]`yield from` expression not recognised
https://bugs.kde.org/show_bug.cgi?id=441540 Bug ID: 441540 Summary: [python3]`yield from` expression not recognised Product: frameworks-syntax-highlighting Version: 5.85.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- SUMMARY The `yield from` expression got introduced with Python 3.3, but Kate syntax highlighting does not recognise it properly. `from` is marked in the same way as the from expression of imports, altough it should rather be the colour and style of `yield`. Example: ```python3 from concurrent.futures import ThreadPoolExecutor def potentise(base): return base**3 bases = [i for i in range(1, 1000)] def run(): with ThreadPoolExecutor(4) as pool: yield from pool.map(potentise, bases) if __name__ == '__main__': for n in run(): print(n) ``` More extensive information can be found in this article: http://simeonvisser.com/posts/python-3-using-yield-from-in-generators-part-1.html STEPS TO REPRODUCE 1. Copy the above code snippet to Kate 2. Set Programming Language to Python OBSERVED RESULT The from of `yield from` has the same colour and style as the from of the import. EXPECTED RESULT The from of `yield from` should look the same as `yield`. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland Other information Not sure whether I chose the right component -- You are receiving this mail because: You are watching all bug changes.
