[liquidshell] [Bug 464052] Easier closing of notifications

2023-01-12 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=464052

--- Comment #2 from Mikko Merikivi  ---
Hmm, after further thinking, I feel like this could be because I've installed
Discord as a Flatpak. It's probably messed up some inter-process communication
pipeline or another.

-- 
You are receiving this mail because:
You are watching all bug changes.

[liquidshell] [Bug 464052] New: Easier closing of notifications

2023-01-09 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=464052

Bug ID: 464052
   Summary: Easier closing of notifications
Classification: Miscellaneous
   Product: liquidshell
   Version: 1.8.1
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kol...@aon.at
  Reporter: mikko...@gmail.com
  Target Milestone: ---

Discord's notifications at least have that View button, but clicking on it
still has the notification pop-up remain on the screen. You'd think that taking
actions with the notification's buttons means it's been acknowledged and in
many cases those buttons lead to a more elaborate view of the information that
is in the pop-up. I suggest making interacting with the notification also close
it.

Also maybe a setting for the display time of notifications; it seems a tad long
for my liking currently.

-- 
You are receiving this mail because:
You are watching all bug changes.

[liquidshell] [Bug 452286] Option to disable panel

2022-04-10 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=452286

Mikko Merikivi  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #6 from Mikko Merikivi  ---
I think marking this as resolved is in order (though I'm not sure which of the
subcategories is the most fitting). Also I don't think those other things I
mentioned in the first post are actual issues, the one in the attachment I'm
thinking is an aberration of having two panels open in the same place. And I
might have been just stupid in the last paragraph, but I said it was just
something potential even then.

-- 
You are receiving this mail because:
You are watching all bug changes.

[liquidshell] [Bug 452286] Option to disable panel

2022-04-10 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=452286

--- Comment #4 from Mikko Merikivi  ---
That seems to be working. Can I put it into config somehow or something so I
can just select a Liquidshell session or whatever it was called? I guess I
could create some autostart script if there's no built-in option.

-- 
You are receiving this mail because:
You are watching all bug changes.

[liquidshell] [Bug 452286] Option to disable panel

2022-04-10 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=452286

--- Comment #2 from Mikko Merikivi  ---
I'll try explaining again.

The default desktop shell, Plasmashell, has memory leaks. Therefore using it is
not a favored option. However, going shell-less seems not very great either,
since when if I quit Plasmashell with "kquitapp5 plasmashell", then the desktop
goes into this kind of mode when a single open window is being dragged:
https://i.stack.imgur.com/4RQDU.jpg
This sort of scenario can happen when I am using two monitors and there's no
current need to be showing any window on the secondary monitor so I drag the
last one away from it.

So, an alternative shell seems to be what I'd like to find. Liquidshell indeed
looks dead simple without the panel, but that's enough to fit my very limited
requirements. Just something that shouldn't be causing problems and fixes the
glitchy background on an empty screen. I don't know if there's a list of shells
to be found; maybe there are yet others indeed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[liquidshell] [Bug 452286] New: Option to disable panel

2022-04-05 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=452286

Bug ID: 452286
   Summary: Option to disable panel
   Product: liquidshell
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kol...@aon.at
  Reporter: mikko...@gmail.com
  Target Milestone: ---

Created attachment 147976
  --> https://bugs.kde.org/attachment.cgi?id=147976=edit
Desktop showing from between panel and a maximized window

I tried switching to Liquidshell when I got frustrated enough with the
intractable memory leaks in Plasmashell that only sometimes happen after waking
from hibernation. Because I don't know of the clear cause, it seems fruitless
to try submitting bug reports when there are already over a dozen unsolved ones
about memory consumption.

I'm amazed that KDE has alternatives to pretty basic components, and I mostly
just needed something to make it so desktops don't become "glitchy" when
there's no window open on a screen. I think. Maybe there's more functionality
that Plasmashell had whose disappearance would become apparent after a while,
but at first glance Liquidshell seemed "good enough".

Anyways, a couple of problems that dissuaded me from making the switch are:
* I'd like to use Latte Dock instead of the panel provided by Liquidshell, so
an option to disable the built-in panel would be nice
* See the attachment for a visual glitch I had with the desktop showing between
a panel and a maximized window. A real eyesore. I don't know if there was some
kind of a conflict because I had Latte also open and that might have messed it
up. So testing where the problem is lying might also benefit from being able to
disable Liquidshell's own panel.

There's potentially some problem with a two monitor setup acting strangely,
too, but I'll investigate after Latte doesn't conflict too much with
Liquidshell.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 447882] New: Windows go under an Always Visible panel on dual monitors

2022-01-03 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=447882

Bug ID: 447882
   Summary: Windows go under an Always Visible panel on dual
monitors
   Product: lattedock
   Version: 0.10.6
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: mikko...@gmail.com
  Target Milestone: ---

SUMMARY
***
Something changed in a problematic way between latte-dock 0.10.4 and 0.10.6. I
sometimes use a secondary monitor, and when I do, the panel covers maximized
windows on latte-dock 0.10.6. However, this does not happen when using only a
single monitor, nor in latte-dock 0.10.4 (I've downgraded to it for now).
***


STEPS TO REPRODUCE
1. Have two monitors on
2. Have Latte Dock in Always Visible mode
3. Open some maximized application

OBSERVED RESULT
The bottom of the maximized window goes under Latte Dock.

EXPECTED RESULT
The window will not be covered by the panel.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: Please have a command line command how to get these also
listed.
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[krunner] [Bug 386513] Krunner memory leak

2021-11-20 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=386513

Mikko Merikivi  changed:

   What|Removed |Added

 CC||mikko...@gmail.com

--- Comment #12 from Mikko Merikivi  ---
There's still some kind of memory leaking in 5.23.2. The memory usage climbed
up to gigabytes over time. I haven't been tracking what might cause it;
normally it seems to not do it all too much after all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 445532] [feature] - allow OnDemand panels to reserve space when unhidden

2021-11-15 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=445532

--- Comment #3 from Mikko Merikivi  ---
I suppose, since complexity is a consideration that you probably have in mind
in your questioning attitude toward the necessity of the suggested feature, why
do we even have a separate On Demand Sidebar? Why just not have a dbus toggle
that works with any type of dock or panel? I noted that it would work for me to
have the dbus toggle available for an Always Visible one, and I imagine some
combination of options would be able to replace the current On Demand Sidebar
functionality when used with that dbus toggle method (called from a Sidebar
Button somewhere).

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 445532] [feature] - allow OnDemand panels to reserve space when unhidden

2021-11-15 Thread Mikko Merikivi
https://bugs.kde.org/show_bug.cgi?id=445532

--- Comment #2 from Mikko Merikivi  ---
> 1. What are the benefits compared to the current provided visibility modes?
> 3. Why not use an AutoHide panel?
I've not seen an option where the panel can get hidden but when visible it
resizes overlapping windows. Also with auto-hiding panels there's some amount
of annoyance with the panel popping up when the cursor goes on the screen
border of the panel's side.

This is an option that could be added to AutoHide as well, by the way. My
personal use case just is the On Demand Sidebar.


> 2. Why not use an AlwaysVisible panel with borderless maximized windows in 
> combination?
The panel takes up space on the screen in this case. Some programs are designed
for very specific aspect ratios and/or resolutions, and thus I have to
compromise either on using a smaller resolution for the program.


I... suppose yet another option is to kill Latte Dock for the time of using a
borderless full screen program, and start it back again when quitting. However,
I am not always 100% focused on just a windowed full screen application, so I
might want to use Latte regardless occasionally.


> 5. OnDemand Sidebar are triggering their showing through the Latte Sidebar 
> Button, are you proposing something different?
Not really. It's an option that probably works for some people. For me, I
managed to find a command to do it from wherever I think is suitable: 
qdbus org.kde.lattedock /Latte org.kde.LatteDock.toggleHiddenState "" "" "" "0"


> 4. What is the end goal for this? maybe a screenshot with the workflow you 
> are trying to achieve it will provide more arguments for supporting it?
It's mostly for gaming purposes. Without naming any specific one, some games on
wine don't handle alt+tabbing all that well when using a proper full screen
mode. So, windowed full screen is a workaround that gets used. But then come
the issues of how to allocate screen space, especially when the game in
question wants to run at, let's say, 2560x1440 exactly. With an always visible
panel, the effective screen space is more like 2560x1388 so some of the pixels
on some border have to be sacrificed or a smaller resolution to be used. Let's
say the next smallest available resolution is 1920x1080. It's a substantial
loss in the area the window can take on the screen, just to have it all there.

And let's say the game is heavy on mouse-use and doesn't lock it into the
center of the screen. Then even an auto-hiding panel hardly does the job since
your mouse will go over the revealing screen edge, let's say for moving the
camera purposes. In other situations I prefer to have the panel always visible,
so an easy way to hide and unhide it without taking up screen estate is what
seems to be what would work best.


I did think that, despite the premise of the On Demand Sidebar, it would also
work for me to add a dbus method to toggle the hidden state of an always
visible bar. But then it would be so hidden of a thing nobody is going to even
find it other than those already in the know.

-- 
You are receiving this mail because:
You are watching all bug changes.