| Summary: | The blue icon to extend the partition needs it's area of influence expanded | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | jimbo <loudsquid> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | greenscarf005, lueck |
| Priority: | NOR | ||
| Version: | 21.12.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | partresizer_widget | ||
|
Description
jimbo
2022-01-21 16:10:20 UTC
That might be nice but it's not so trivial to properly implement. First, there is partition widget that only has red move icon. And then there is handle widget with a size taken from Qt style (QStyle::PM_SplitterWidth). I think to achieve what you want, we can make handle widget wider. Then area of influence will be larger. But it makes widget look somewhat ugly with white spaces around (see screenshot) which would be confusing as people might think that partition does not span all the way to the left or right. Created attachment 145730 [details]
partresizer_widget
partresizer widget with wider handles
Yeah that does look like it would cause confusion. Is there be a way to overlap some other blank 'panel' UI so you could hide the white edges? (In reply to jimbo from comment #3) > Yeah that does look like it would cause confusion. Is there be a way to > overlap some other blank 'panel' UI so you could hide the white edges? Maybe, but I can't give you definite answer right now. After all, other widgets are already on top of QMainWindow, so it should be possible to overlap widgets. But you also want handles to be on top of the main widget (so that you get stretch cursor, not move) but also invisible. So probably doable but would need non-trivial code changes. No worries, I just wanted to point it out (as no previous bug report seemed to point it out) and give an idea of how to 'fudge' it. (In reply to jimbo from comment #5) > No worries, I just wanted to point it out (as no previous bug report seemed > to point it out) and give an idea of how to 'fudge' it. It was actually mentioned in #388650 but that bug has a mix of different issues and rest of issues there are resolved, so maybe I'll close that bug for this one. Anyway, we have now discussed some ideas how to fix it, although I can't promise that it will be done soon since there are other bugs that need solving too. But patches are always welcome. *** Bug 388650 has been marked as a duplicate of this bug. *** *** Bug 465021 has been marked as a duplicate of this bug. *** |