[kcalc] [Bug 459708] Having to press Shift to see secondary functionality unnecessarily hides it
https://bugs.kde.org/show_bug.cgi?id=459708 --- Comment #4 from Mike H --- First of all, I'm not certain why my bug was closed as a duplicate of a much less detailed bug one year later. I believe that one should have been closed instead. Second, the resolution to promote square root still does not address the UX issue of not understanding what 'shift' implies. The shift button should have some special text styling or button background color that is different from every other button. Perhaps Italicized and a different color for example. At the very least a different color. Then, every single button that is affected by the shift should have superscript text, perhaps italicized, But definitely the same color as chosen for the shift button, that displays what the secondary feature of the button is. I linked a descriptive picture of a TI-36 calculator previously in this bug that denotes how its second function key has the different color and the text on the buttons denotes both features, one being the italicized feature. It does however appear that Casio calls their second function button the shift key like K-Calc. I have never owned a Casio calculator and only today decided to start looking at Texas instruments's competition. https://upload.wikimedia.org/wikipedia/commons/f/fc/Casio_algebra_fx_2.0_plus.PNG shows how Casio has a shift button that is orange and superscript text above every shiftable function button that shows its secondary function. Instead of hiding behind an opaque layer change for the button, or entire text replacement, I don't know how it is done, both values somehow need to be displayed on the button. Concurrently. While it does currently mimic casio's naming, I also still think that the naming of shift is ambiguous even with UX contextual clue improvements, so renaming to 'second function' '2nd func' something like that, might also be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 --- Comment #22 from Mike H --- Nope, its some sort of toggle... Space forward seems to work for a bit backspace always works space forward seems to stop working after backspacing... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 --- Comment #21 from Mike H --- God I wish I could edit my comments. In Konsole, SPACE REPEAT DOES NOT WORK ONLY backspace. SPACE AND BACKSPACE both work in Kate wtf -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 --- Comment #20 from Mike H --- And I should say, BACKSPACE REPEAT WORKS SPACE REPEAT WORKS Character repeat, like holding down - to get --- DOES NOT WORK -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443721] Keyboard repeat speed is ignored under wayland
https://bugs.kde.org/show_bug.cgi?id=443721 Mike H changed: What|Removed |Added CC||myst...@gmail.com --- Comment #19 from Mike H --- Is this bug really fixed? Today, on Ubuntu 23.10, Konsole 23.08.1, KDE Frameworks 5.110.0 QT 5.15.10 I cannot get key repeat to work at all inside of Konsole. It does not seem to work in any normal KDE app. It does work in Chrome It does not work in GTK apps (Geany) It does not work in Kate How do I make keys repeat with the newest (released) ubuntu Plasma/KDE release, using Wayland ? (Intel gfx) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476345] New: Unmovable button bars in full screen annotation mode
https://bugs.kde.org/show_bug.cgi?id=476345 Bug ID: 476345 Summary: Unmovable button bars in full screen annotation mode Classification: Applications Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: myst...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Button bars cannot move / Bad user experience for attempting to annotate screenshots in fullscreen mode. STEPS TO REPRODUCE 1. Load Annotation Window full screen 2. Notice the Stroke Fill and Shadow options are nearly hidden at the bottom left of the full screen window with everything else at the top or left side 3. Attempt to move button stroke fill shadow bar around OBSERVED RESULT I cannot move the button bars around to fit my window better. EXPECTED RESULT Movable Button Bars. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 23.04 23.04 (x86_64) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 6.4.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 465142] I need to be able to create a split view, from ALREADY EXTANT TABS.
https://bugs.kde.org/show_bug.cgi?id=465142 --- Comment #3 from Mike H --- I seriously swear I wish I went multiple years to college, and took C++ and actually got good at it, so I could flarning fork all your bad decisions and keep KDE working the way I liked. IVE USED KDE SINCE V1 ON RED HAT 6.2 Not RHEL, RED HAT version name "Zoot". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 465142] I need to be able to create a split view, from ALREADY EXTANT TABS.
https://bugs.kde.org/show_bug.cgi?id=465142 --- Comment #2 from Mike H --- Oh no, Im even wrong about how the stupidity acts. INSTEAD of having 2 tabs on the left to where i could switch my 2 open apps on the left, and a new terminal on the right ... my first application IS STILL FULLSCREEN on the first tab, and the second tab? second application AND A NEW BLANK TERMINAL I DO NOT NEED OR WANT It works even worse than i thought. Here's a thought. Please consider it for any new stupid breaking changes. Wen you BREAK THE WORKFLOW OF AN APPLICATION ENTIRELY, PUT IN AN _OPTION_ IN THE CONFIG SO PEOPLE WHO RELY ON THAT WORKFLOW CAN GO BACK TO THE UNBROKEN FORM -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 465142] I need to be able to create a split view, from ALREADY EXTANT TABS.
https://bugs.kde.org/show_bug.cgi?id=465142 --- Comment #1 from Mike H --- Meant to say everything after 2018... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 465142] New: I need to be able to create a split view, from ALREADY EXTANT TABS.
https://bugs.kde.org/show_bug.cgi?id=465142 Bug ID: 465142 Summary: I need to be able to create a split view, from ALREADY EXTANT TABS. Classification: Applications Product: konsole Version: 22.04.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: myst...@gmail.com Target Milestone: --- SUMMARY *** I have tabs open in my Konsole. I want to group them side by side after I've been working in them fullscreen separately. It cannot work anymore. *** STEPS TO REPRODUCE 1. create 2 tabs. 2. decide you want to then see the running program content from each tab into a split view, so 2 or maybe 3 tabs can be seen at once. Say I have 2 ssh sessions now open in the 2 tabs. (I login to mirrored VRRP routers...i need to execute the same on each, and COULD for almost 10 years with the old Konsole) 3. Turn Split mode on, and expect to now see the 2 extant tabs, side by side. OBSERVED RESULT 2 stupid tabs on the left of 2 ssh sessions, and a BRAND NEW USELESS TERMINAL on the right. EXPECTED RESULT MY ALREADY RUNNING APPLICATIONS ABLE TO BE VIEWED SIDE BY SIDE Versions: Apparently everything before I stopped upgrading my desktop computer in 2018 running Sabayon's last version forever until the install corrupted itself. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 459708] New: "Shift" functionality hidden, misleading, and wrong. Expose all buttons by default. Or expose the fact "secondary" features MAY exist. You don't now.
https://bugs.kde.org/show_bug.cgi?id=459708 Bug ID: 459708 Summary: "Shift" functionality hidden, misleading, and wrong. Expose all buttons by default. Or expose the fact "secondary" features MAY exist. You don't now. Classification: Applications Product: kcalc Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: myst...@gmail.com Target Milestone: --- SUMMARY *** There are no less than 5 diffrerent bug reports of people not being able to find a square root key. This is MY report of BAD UX because this should not over the course of the products lifetime contribute to ANY bug reports of a missing square root key. 75571 kcalc general eteran RESODUPLThere is no square root button 2014-10-15 78052 kcalc general eteran RESODUPLsquare root button required 2004-03-20 277674 kcalc general eteran RESOWORKThere is no square root button 2018-02-22 435951 kcalc general eteran RESONOT Square root √ button and function apparrently missing 2021-04-22 253542 kcalc general eteran RESONOT there is not sqrt button 2010-10-07 *** STEPS TO REPRODUCE 1. Open kcalc 2. switch to scientific mode 3. expect to see all the useful operations, and not have them be hidden behind an ambiguous "shift" button. OBSERVED RESULT 12 buttons change. The entire left column, and M+ now becomes M- EXPECTED RESULT SHOW ALL THE USEFUL FUNCTIONS AND NOT BEHIND A "SHIFT" BUTTON WHICH IS AMBIGUOUS AND DOES NOT EXPLAIN "EXTRA FEATURES" "EXTRA BUTTON FUNCTIONS" etc. its JUST SHIFT. Why do I need shift? I never have used shift on a calculator before. I've seen "2nd function" on a calculator. "2nd" not "SHIFT". Rename the button "2nd function" to imply there may be something "behind" the visible but not useful to me (trying to find sqrt) buttons present by default. ADD some sort of "extra text" 'around' the buttons, to imply a secondary feature, like Texas Instruments does: https://education.ti.com/en/products/calculators/scientific-calculators/ti-36x-pro Notice how every button with a "2nd function" has BLUE TEXT above it, and THE 2ND FUNCTION BUTTON IS BLUE TOO. THIS is an example of GOOD, INTUITIVE, AND HONESTLY IN 2022 THE EXPECTED WAY UX ON A CALCULATOR SHOULD BE. NOT a button that "can't be found"(missing sqrt by default) NOT a word (shift) that "means very little, and borderline does not mean what it does unless the context of 'buttons can do something else' is enumerated at ANY point, which it ISN'T". SOFTWARE/OS VERSIONS This has been a problem since 2004 apparently. It does not matter what version im using, since all bugs to closed as "not a bug/wontfix" so no fixes have ever been committed. But for what its worth, Ubuntu 22.04 Plasma 5.24.6 Frameworks 5.95.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] GTKHeaderBar is dark when nothing else in Breeze theme is
https://bugs.kde.org/show_bug.cgi?id=392104 --- Comment #3 from Mike H <myst...@gmail.com> --- Created attachment 111532 --> https://bugs.kde.org/attachment.cgi?id=111532=edit Same test-case with Adwaita theme; notice, its brighter -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] GTKHeaderBar is dark when nothing else in Breeze theme is
https://bugs.kde.org/show_bug.cgi?id=392104 Mike H <myst...@gmail.com> changed: What|Removed |Added Summary|Foreground Color is the |GTKHeaderBar is dark when |same as Text color |nothing else in Breeze ||theme is -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] Foreground Color is the same as Text color
https://bugs.kde.org/show_bug.cgi?id=392104 --- Comment #2 from Mike H <myst...@gmail.com> --- Created attachment 111529 --> https://bugs.kde.org/attachment.cgi?id=111529=edit Remmina with an unreadable + button ; it blends in -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] Foreground Color is the same as Text color
https://bugs.kde.org/show_bug.cgi?id=392104 --- Comment #1 from Mike H <myst...@gmail.com> --- Created attachment 111528 --> https://bugs.kde.org/attachment.cgi?id=111528=edit Headerbar widget without selection, for actual color - its at the bottom row by itself. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 392104] New: Foreground Color is the same as Text color
https://bugs.kde.org/show_bug.cgi?id=392104 Bug ID: 392104 Summary: Foreground Color is the same as Text color Product: Breeze Version: 5.12.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk theme Assignee: scionicspec...@gmail.com Reporter: myst...@gmail.com Target Milestone: --- Created attachment 111527 --> https://bugs.kde.org/attachment.cgi?id=111527=edit The headerbar selected (with slight transparent blue highlight) - still darker color. background-image: linear-gradient(to bottom, #556068, #475057); This makes things unreadable, and goes against the "light" colored "Breeze" theme being...light colored. Can we make the background color closer to white? I've enumerated a _lot_ of widgets with glade; this is the only one that seems 'wrong' out of the set. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366156] ksmserver crashes when switching from nvidia to intel profile/GPU on laptop with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=366156 Mike H. Bermel <bermelm...@gmail.com> changed: What|Removed |Added CC||bermelm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 360925] Default Dbus shortcut prevents multiple instances of Spectacle when continuing to press PrntScr
https://bugs.kde.org/show_bug.cgi?id=360925 Mike H <myst...@gmail.com> changed: What|Removed |Added Summary|Default Dbus shortcut |Default Dbus shortcut |prevents multiple instances |prevents multiple instances |of Spectacle by continuing |of Spectacle when |to press PrntScr|continuing to press PrntScr -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 360925] New: Default Dbus shortcut prevents multiple instances of Spectacle by continuing to press PrntScr
https://bugs.kde.org/show_bug.cgi?id=360925 Bug ID: 360925 Summary: Default Dbus shortcut prevents multiple instances of Spectacle by continuing to press PrntScr Product: Spectacle Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: myst...@gmail.com I've used ksnapshot for years with a simple custom shortcut: prntscrn = command "ksnapshot" I modified this now to run Spectacle and it runs as expected: multiple concurrent sessions of a screen capture program running, as I modify contents on my screen and want to take multiple shots in rapid succession to edit later. Click window - prntscrn; click option in window - prntscrn again; keep doing step by step workflow in my program - prntscrn each time, leaving me with sometimes >20 or more screenshot windows open. This is how I think it should work by default; the org.kde.Spectacle action is preventing this, and I consider this to be a bug or something that is definitely explained to people who expect their screenshot program to hold numerous copies of itself in memory waiting for the user to process the pic(s) further. Reproducible: Always Steps to Reproduce: 1. PrntScrn 2. PrntScrn Again 3. PrntScrn 20 more times because you expect 20 more windows to popup out of frustration Actual Results: One single window opens; if this one single window is no longer foreground, it does not even pop itself back up into foreground. It just sits there, behind the active window. Expected Results: Default action of keeping multiple screenshot windows in the background, and automatically starting a new one if the button is repeatedly pressed. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356831] cannot send image to clipboard in background mode
https://bugs.kde.org/show_bug.cgi?id=356831 Mike H <myst...@gmail.com> changed: What|Removed |Added CC||myst...@gmail.com --- Comment #9 from Mike H <myst...@gmail.com> --- This doesn't even require a clipboard manager... The semantics of X11 PRIMARY and CLIPBOARD selections are: the app must stay running -UNTIL THE DATA IS TRANSFERRED OUT INTO THE PROGRAM THAT PASTES. So..by extension, just keep a hidden copy of the program in the background, _UNTIL THE RECIPIENT PROGRAM ASKS FOR ITS CLIPBOARD_ and then exit. Or, if the CLIPBOARD changes and Spectacle is no longer the holder of the CLIPBOARD selection, then just quit the program and send a notification "another program has usurped the clipboard" Really guys, this seems so easy to me? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357687] New: Icons-Only Task Manager has button shapes
https://bugs.kde.org/show_bug.cgi?id=357687 Bug ID: 357687 Summary: Icons-Only Task Manager has button shapes Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: myst...@gmail.com CC: plasma-b...@kde.org I've recently updated to a git pull of KDE from a week ago, but never exited my plasma session and restarted. Upon restart, my nice looking task manager now has button shapes. This is supposed to be an 'icons only' task manager; and you've provided no option to 'remove button outline' so I believe this to be a categorical bug. I had previously used the regular task manager, which after a certain point of open windows, started to look like this. I dislike the button outline. In the history of making plasma5 youve removed a lot of the setting options of kde4's respective task managers. I am unhappy with this removal, because I cannot get my panel to look proper anymore, after quite a long time of using kde4 and being very happy with the "no button shape, no background color, with indicators" style. I would like it back. Reproducible: Always Steps to Reproduce: 1. Want icons Only Actual Results: Get Buttons Instead. Expected Results: Icons, no outline, no button shape, just icons that I can click on. -- You are receiving this mail because: You are watching all bug changes.
