[plasmashell] [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it

2023-04-08 Thread Stuff
https://bugs.kde.org/show_bug.cgi?id=349785

Stuff  changed:

   What|Removed |Added

 CC|b67z58+bugs.kde@pm.me   |

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

[krita] [Bug 485689] New: Vector layer incorrect transform result when both scaled and sheared

2024-04-17 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=485689

Bug ID: 485689
   Summary: Vector layer incorrect transform result when both
scaled and sheared
Classification: Applications
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Transform
  Assignee: krita-bugs-n...@kde.org
  Reporter: seitr...@gmail.com
  Target Milestone: ---

Created attachment 168625
  --> https://bugs.kde.org/attachment.cgi?id=168625&action=edit
Using krita-5.3.0-prealpha-13fe82adbb-x86_64.appimage

SUMMARY

If you both shear and scale a vector layer with the free transform tool, the
end result will either change (potentially significantly) from the preview, or
the the preview itself will also be wrong and visibly break out of its bounding
box.  If the preview looks right, changing preview mode will show the wrong
result for a split second.

STEPS TO REPRODUCE
1. Make a new *vector* layer
2. Add some shape, like a rectangle or polyline
3. Activate the transform tool
4. Shear both edges to approximate an overall 45 degree rotation
5. Scale out along what was the top edge

OBSERVED RESULT

Either the preview will break out of the handle bounding box, or once you apply
the transform you will get a very different result from the preview.

EXPECTED RESULT

The preview should stay within the bounding box, and the end result should
match the preview.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 23.10
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version:  5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Affects master, krita-5.3.0-prealpha-13fe82adbb-x86_64.appimage, and 5.2.2

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

[krita] [Bug 485689] Vector layer incorrect transform result when both scaled and sheared

2024-04-17 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=485689

--- Comment #1 from stuff  ---
I looked into this: KisTransformWorker::transform() reports its supposed
transform, though never uses this function itself.  This reported transform is
used for the vector layer's shape transforms and looks like:

return TS.inverted() * S * TS * SC * R * T;

Whereas KisTransformUtils::MatricesPack::finalTransform() looks like:

return TS * SC * S * projectedP * T;

Notice that SC and S are in a reverse order!

There are three different transforms in play
1) the bounding box during free transform (uses MatricesPack)
2) the rasterized result of KisTransformWorker, using its mathy inner
workings
3) the vector layer result using KisTransformWorker::transform()
I think 1 and 2 currently agree, but 3 doesn't, so I suspect maybe
KisTransformWorker is just reporting its own transform wrong?

Through trial and error I've found this function, a slight modification from
the current one, seems to fix this problem.
QTransform KisTransformWorker::transform() const
{
QTransform TS = QTransform::fromTranslate(m_xshearOrigin * m_xscale,
m_yshearOrigin * m_yscale);
QTransform S; S.shear(0, m_yshear); S.shear(m_xshear, 0);
QTransform SC = QTransform::fromScale(m_xscale, m_yscale);
QTransform R; R.rotateRadians(m_rotation);
QTransform T = QTransform::fromTranslate(m_xtranslate, m_ytranslate);

return SC * TS.inverted() * S * TS * R * T;
}
where I've swapped the order of scale and shear and compensated for that in the
translation

Also, with this modified version, at the end of
KisTransformUtils::createTransformWorker, MatricesPack(args).finalTransform()
tends to be equal or nearly equal (within 1e-5 component-wise) to
transformWorker.transform(), where it definitely wasn't before.  There's a
comment explaining KisTransformWorker::transform that does match the current
code, though, so I'm not sure what's going on.

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

[Marknote] [Bug 493472] New: [Feature Request] Insert images from drag-and-drop, paste

2024-09-22 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=493472

Bug ID: 493472
   Summary: [Feature Request] Insert images from drag-and-drop,
paste
Classification: Applications
   Product: Marknote
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@kaidan.im
  Reporter: seitr...@gmail.com
CC: c...@carlschwan.eu, m...@kaidan.im
  Target Milestone: ---

I'd like to be able to screenshot with spectacle and simply drag and drop the
image into Marknote.  Or copy an image from e.g. firefox, spectacle, krita, and
paste it into a note.  I assume it would automatically save the image alongside
the note like the quick sketch feature.

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

[Marknote] [Bug 490423] Cannot click and drag to highlight text

2024-09-22 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=490423

stuff  changed:

   What|Removed |Added

 CC||seitr...@gmail.com

--- Comment #1 from stuff  ---
I've found if I click and hold for a few seconds before dragging it never works
(it doesn't even move the caret).  Also initially dragging vertically never
works.  And, rarely, clicking and dragging scrolls a few pixels instead.

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

[krita] [Bug 502157] Krita Next Nightlies SAFE ASSERT Internal Errors and Crash when using Tablet

2025-03-30 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=502157

stuff  changed:

   What|Removed |Added

 CC||seitr...@gmail.com

--- Comment #1 from stuff  ---
It seems to happen the first time the stylus (not mouse) is moved over the
canvas, but it depends on what tool is active.  If the brush tool is active for
the first stylus motion(?) over the canvas, it triggers the assert.  But if
instead another tool (e.g. the move tool) is active, then there is no failed
assert, and then you can switch to the brush tool and it's fine.

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

[krita] [Bug 502157] Krita Next Nightlies SAFE ASSERT Internal Errors and Crash when using Tablet

2025-03-30 Thread stuff
https://bugs.kde.org/show_bug.cgi?id=502157

--- Comment #2 from stuff  ---
Opening a second image also triggers the line 266 assert, immediately

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