https://bugs.kde.org/show_bug.cgi?id=366621
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|ImageEditor |ImageEditor-Tool-Resize
--
You are
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #21 from Maik Qualmann ---
Git commit 8c2a48759c3b7ef16e14458d423ef7041481e501 by Maik Qualmann.
Committed on 17/08/2016 at 17:56.
Pushed by mqualmann into branch 'master'.
fix CR #1369583
M +1-1
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #20 from caulier.gil...@gmail.com ---
Maik,
Coverity scan report a problem with your last patch. See below :
** CID 1369583: Integer handling issues (CONSTANT_EXPRESSION_RESULT)
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #19 from Maik Qualmann ---
Git commit 65fa04ca097d4ff695690886a9f2be459b4279a9 by Maik Qualmann.
Committed on 12/08/2016 at 19:29.
Pushed by mqualmann into branch 'master'.
fix crash by big memory allocation for DImg
https://bugs.kde.org/show_bug.cgi?id=366621
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||5.2.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=366621
Thomas Rother changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #17 from Maik Qualmann ---
Git commit 6ecfecf1f46970bfbd509fba50e9fa7c6b324309 by Maik Qualmann.
Committed on 11/08/2016 at 21:13.
Pushed by mqualmann into branch 'master'.
new value is accepted with tab key in
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #16 from Maik Qualmann ---
Git commit 90f31456779f4aeb9ac06a385f398827fd35c985 by Maik Qualmann.
Committed on 11/08/2016 at 19:43.
Pushed by mqualmann into branch 'master'.
fix check of maximum addressable memory on
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #15 from caulier.gil...@gmail.com ---
and this will explain why the allocation error do not appear...
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #14 from Maik Qualmann ---
Found a bug in checkAllocation()
std::numeric_limits::max() //else on 64bit only 32bit max value
right is:
std::numeric_limits::max()
Maik
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #13 from caulier.gil...@gmail.com ---
Maik,
If you test with standard QSlider and QSpinBox solution, The tab key valide the
edited value.
If Thomas as used the ration in % instead the real size in pixels to adjust
image size, it's normal
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #12 from Maik Qualmann ---
I think they have 900% and 480% entered in the bottom two sliders? That's about
right with the requested memory.
Maik
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #11 from Maik Qualmann ---
I can not really reproduce the problem. Should Tab key accept new value? Only a
click with the left mouse button is critical because of the slider to a high
value can jump to the mouse
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #10 from caulier.gil...@gmail.com ---
For point 1/ i understand the dysfunction: When we enter a value by a right
mouse click over slider, if we press tab to switch to next value to enter, the
new value is not set. Enter key must be pressed
https://bugs.kde.org/show_bug.cgi?id=366621
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #9
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #8 from Thomas Rother ---
Original size is 6000 x 4000 (comes from the camera in jpeg "basic" quality)
with 300 dpi resolution.
I tried to resize it to 900 width and 480 width (for web publishing)
--
You are
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #7 from caulier.gil...@gmail.com ---
>digikam.general: Final "Bildgröße ändern" started...
Want mean that you have used resize tool. Which new image sizes do you set
exactly ?
Gilles Caulier
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #6 from Thomas Rother ---
... half an hour later, same situation:
...
digikam.dimg: "/mnt/nas/public/Fotos/Nikon D7200/DSC_0234.JPG" : JPEG file
identified
digikam.metaengine: Loading image history ""
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #5 from Thomas Rother ---
Hmmm, after some testing, I can not see this crash anymore and I don't know why
...
Now I get the following lines:
digikam.metaengine: Cannot set Iptc tag string into image using Exiv2
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #4 from caulier.gil...@gmail.com ---
Can you share the edited image somewhere on the cloud to test here ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #3 from Thomas Rother ---
Maybe there is not enough RAM? But when I do the same resize operation on the
same image with GIMP, there are no problems
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=366621
--- Comment #2 from Thomas Rother ---
It is an OpenSUSE Leap 42.1 x64 with Kernel 4.1.27-27-default #1 SMP PREEMPT
Fri Jul 15 12:46:41 UTC 2016 (84ae57e) x86_64 x86_64 x86_64 and 32 GB RAM
Any idea how to debug without drkonqi?
https://bugs.kde.org/show_bug.cgi?id=366621
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
23 matches
Mail list logo