https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #15 from Maurizio Paolini ---
Opened a qt bug report:
https://bugreports.qt.io/browse/QTBUG-52312
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #14 from Maurizio Paolini ---
A standalone minimal C++ program using Qt5 and drawEllipse shows that the
precision
loss with circles having large radius is actually a Qt problem!
I will try to file a qt bug report about this problem.
However
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #13 from Maurizio Paolini ---
Created attachment 98047
--> https://bugs.kde.org/attachment.cgi?id=98047&action=edit
same as previous, but with unmodified kig
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #12 from Maurizio Paolini ---
Created attachment 98046
--> https://bugs.kde.org/attachment.cgi?id=98046&action=edit
png showing a (different) problem when drawing circles/arcs
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #11 from Maurizio Paolini ---
Anyway, there are still problems when drawing arcs and circles; apparently of a
different
nature: it becomes apparent when the radius of circle/arc is much larger then
the size
for the displayed canvas. I will
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #10 from Maurizio Paolini ---
An identical problem is present when drawing circular arcs! Since the
correction is minimal and perfectly similar to what was done for circular arcs
I took the liberty of pushing it into
origin/master.
The comm
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #9 from Maurizio Paolini ---
solved via reviewboard:
https://git.reviewboard.kde.org/r/127354/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #8 from Maurizio Paolini ---
(In reply to Rex Dieter from comment #7)
> I'd recommend submitting your patch to reviewboard.kde.org, that's the ideal
> way.
Done... but no comments so far. Now I am not sure what to do. Should I push
my com
https://bugs.kde.org/show_bug.cgi?id=359805
Rex Dieter changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |
https://bugs.kde.org/show_bug.cgi?id=359805
Maurizio Paolini changed:
What|Removed |Added
Attachment #97700|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #5 from Maurizio Paolini ---
Created attachment 97700
--> https://bugs.kde.org/attachment.cgi?id=97700&action=edit
patch proposal
This patch adds toScreenF methods alongside toScreen and uses it to create a
QRectF instead of a QRect in Ci
https://bugs.kde.org/show_bug.cgi?id=359805
Rex Dieter changed:
What|Removed |Added
CC||rdie...@math.unl.edu
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=359805
--- Comment #4 from Maurizio Paolini ---
A simple workaround to the problem consists in commenting the
method "CircleImp::draw" in both objects/circle_imp.cc and
objects/circle_imp.h.
In this way kig falls back to the generic method for drawing conics,
https://bugs.kde.org/show_bug.cgi?id=359805
Maurizio Paolini changed:
What|Removed |Added
Summary|strange loss of drawing |strange loss of drawing
|p
14 matches
Mail list logo