https://bugs.kde.org/show_bug.cgi?id=499064
--- Comment #5 from Andrius Štikonas <andr...@stikonas.eu> --- (In reply to Rafael Just from comment #4) > Could be, since It only looks like the cursor / partition manager doesn't > notice that there is an edge. Could it be perhaps worth to check out the > code about defining edges (maybe even border rounding)?(In reply to Andrius > Štikonas from comment #3) > > (In reply to Rafael Just from comment #2) > > > Could be, since It only looks like the cursor / partition manager doesn't > > > notice that there is an edge. Could it be perhaps worth to check out the > > > code about defining edges (maybe even border rounding)? > > > > Well, it's mostly here: > > https://invent.kde.org/system/kpmcore/-/blob/master/src/gui/ > > partresizerwidget.cpp?ref_type=heads#L117 and > > https://invent.kde.org/system/kpmcore/-/blob/master/src/gui/ > > partresizerwidget.cpp?ref_type=heads#L108 > > Well, my c++ is not very good (I am still a student and just finished > learning C) but I'll see what I can do :) You probably don't need very good C++ here. This is more of an investigation task. Anyway, I played a bit and found out that if I add 1 to this line https://invent.kde.org/system/kpmcore/-/blob/master/src/gui/partresizerwidget.cpp?ref_type=heads#L131 Then resizing mouse cursor reappears. So my current understanding is that handleWidth is 0. And something changed somewhere else in the stack (Qt or Frameworks) and now zero-width handles don't show that resize cursor. I'm not 100% sure how to fix that. We could set handleWidth to 1. That would a consequence that we would see a narrow grey rectangle at the boundary of the widget. But maybe that's fine. After all gparted has fairly big widget boundary indicators. -- You are receiving this mail because: You are watching all bug changes.
