Bug 502706

Summary: Paste of column(s) consisting of integers to a Spreadsheet always inserts extra zeros into the cells below the last data
Product: [Applications] LabPlot2 Reporter: Yoshinobu Shimamura <shimamura.yoshinobu>
Component: frontendAssignee: Alexander Semke <alexander.semke>
Status: REPORTED ---    
Severity: minor    
Priority: NOR    
Version First Reported In: 2.11.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: A spread sheet including a column of integers

Description Yoshinobu Shimamura 2025-04-12 11:48:55 UTC 
Created attachment 180196 [details]
A spread sheet including a column of integers

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
When I try to paste column(s) consisting of integers to a Spreadsheet by Ctl+V,  extra zeros are always inserted into the cells below the last data. The problem doesnot happen if column(s) including at least one real number. 

STEPS TO REPRODUCE
It occurs when pasting column(s) consisting of only integers to a Spreadsheet.

OBSERVED RESULT

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Windows: Windows 11 Home 24H2

ADDITIONAL INFORMATION
Comment 1 Yoshinobu Shimamura 2025-04-13 08:00:50 UTC 
I found that filling extra zeros does not occur if the first row is a real number, but it occurs if the first row is integer, where filling extra zeros occurs below the last row including an integer.
Comment 2 Alexander Semke 2025-04-13 09:02:46 UTC 
(In reply to Yoshinobu Shimamura from comment #1)
> I found that filling extra zeros does not occur if the first row is a real
> number, but it occurs if the first row is integer, where filling extra zeros
> occurs below the last row including an integer.

Your findings are correct. We don't support "empty/non-existing value"  for integer columns yet and show zero instead. We plan to fix this problem in the major release 3.0 after the next release 2.12.
Comment 3 Yoshinobu Shimamura 2025-04-14 01:00:01 UTC 
Thank you very much for your quick response and I understand the plan for correction. Thanks again!