Bug 100319 - At 3440x1440 resolution, numeric entries appear ONLY in entry bar and not simultaneously in cell for columns A-K
Summary: At 3440x1440 resolution, numeric entries appear ONLY in entry bar and not sim...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-11 04:07 UTC by xerkon
Modified: 2017-03-16 08:39 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description xerkon 2016-06-11 04:07:25 UTC
Open Calc 5.1.3.2 full screen at 3440x1440 resolution.  Click in cell A1 and enter any number.  Number will not appear simultaneously in BOTH cell and input bar before enter is pressed, instead appearing ONLY in input bar.  This behaviour continues from column A to column K, which is the first column where input behaviour is normal.  If Calc is windowed and window width is 3/4 or less of full screen, numeric entry starts working again.  Also, if screen resolution is changed to 2560x1440 or below, numeric entry works normally.  This bug doesn't seem to have any effect upon either alphabetic characters or symbols.
Comment 1 Xisco Faulí 2017-03-08 11:49:02 UTC Comment hidden (obsolete)
Comment 2 xerkon 2017-03-16 05:25:35 UTC
I uninstalled 5.1.3 and downloaded and installed 5.3.0 and after a little testing in Calc I can say that this bug is now fixed.
Comment 3 xerkon 2017-03-16 05:29:04 UTC
I changed the status to resolved / fixed but if that's wrong please change it for me.  I'm new at this (-*?
Comment 4 Xisco Faulí 2017-03-16 08:39:56 UTC
(In reply to xerkon from comment #3)
> I changed the status to resolved / fixed but if that's wrong please change
> it for me.  I'm new at this (-*?

Yes, the correct status is RESOLVED WORKSFORME as we don't know the commit that fixed this.