Bug 41918 - Using Ctrl+F8 affects setting in options giving confusion
Summary: Using Ctrl+F8 affects setting in options giving confusion
Status: RESOLVED DUPLICATE of bug 43786
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-18 01:29 UTC by Winfried Donkers
Modified: 2014-11-17 08:41 UTC (History)
3 users (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 Winfried Donkers 2011-10-18 01:29:48 UTC
When using Ctrl+F8 to enable/disable value highlighting, this setting is copied to the setting shown in options (Calc - Display...). However, the shown setting is not saved.
Users who want to configure LibO to enable/disable value highlighting but have used Ctrl+F8, may see an incorrect configuration setting in options. This results in not succeeding to enable/disable value highlighting as default behaviour.

Way to reproduce problem:
-enable value highlighting in options and save configuration;
-open (any) spreadsheet
-disable value high lighting with Ctrl+F8
-open options - calc - display... and see that value highlighting is unchecked
-save/close spreadsheet
-open (any) spreadsheet
-value highlighting is enabled

expected behaviour:
Ctrl+F8 enable/disable value highlighting for this session only, do not change configuration;
Options - Calc - Display - Value Highlighting check/uncheck to enable/disable value highlighting as default.
Comment 1 Winfried Donkers 2011-10-18 03:11:31 UTC
I used wrong terms (My UI is not in English):
for Calc - Display read Libreoffice Calc - View
Comment 2 ign_christian 2013-06-16 02:23:38 UTC
> expected behaviour:
> Ctrl+F8 enable/disable value highlighting for this session only, do not
> change configuration;
> Options - Calc - Display - Value Highlighting check/uncheck to
> enable/disable value highlighting as default.

Hi Winfried, that behavior applied on LO 4.0.4.2 (Win7 32bit). So should we mark it WFM?
Comment 3 Winfried Donkers 2013-06-17 06:46:16 UTC
(In reply to comment #2)
> > expected behaviour:
> > Ctrl+F8 enable/disable value highlighting for this session only, do not
> > change configuration;
> > Options - Calc - Display - Value Highlighting check/uncheck to
> > enable/disable value highlighting as default.
> 
> Hi Winfried, that behavior applied on LO 4.0.4.2 (Win7 32bit). So should we
> mark it WFM?

Hi ign_christian,

I just cheked with version 4.0.4.2:
1. default setting is on (Value Highlighting checked)
2. press Ctrl+F8 in a worksheet, value highlighting is switched of (expected), but the default settings shows no longer the check-mark. That is not expected and IMO not correct.
Pressing Ctrl+F8 should not affect the default setting (neither the actual setting, nor the presentation in Options-Calc-Display-Value Highlighting).

Therefore I have taken the liberty to reopen the bug...
Comment 4 ign_christian 2013-06-17 12:57:22 UTC
> 2. press Ctrl+F8 in a worksheet, value highlighting is switched of
> (expected), but the default settings shows no longer the check-mark. That is
> not expected and IMO not correct.
But after you close & reopen that file, that will be checked (default) again. 

> Pressing Ctrl+F8 should not affect the default setting (neither the actual
> setting, nor the presentation in Options-Calc-Display-Value Highlighting).
There is a glitch in the UI indeed.
 
> Therefore I have taken the liberty to reopen the bug...
Of course it's your right :)
Comment 5 Joel Madero 2014-11-06 22:01:18 UTC
Need QA to confirm - moving to UNCONFIRMED. Thanks
Comment 6 Buovjaga 2014-11-16 17:52:19 UTC
(In reply to Winfried Donkers from comment #3)
> I just cheked with version 4.0.4.2:
> 1. default setting is on (Value Highlighting checked)
> 2. press Ctrl+F8 in a worksheet, value highlighting is switched of
> (expected), but the default settings shows no longer the check-mark. That is
> not expected and IMO not correct.
> Pressing Ctrl+F8 should not affect the default setting (neither the actual
> setting, nor the presentation in Options-Calc-Display-Value Highlighting).

For me, the default was Off. I experienced no glitches or inconsistencies. Changing it to On only affects the current session, even if you have Options - Load/Save - Load user-specific settings with the document checked. Setting as WFM.

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Comment 7 Winfried Donkers 2014-11-17 06:48:44 UTC
(In reply to Beluga from comment #6)

Hi Beluga,
I hate to disappoint you, but:
-I started calc (4.4.0.0alpha1+) with a blank document
-I checked tools-options-calc-view-value highlighting: it was checked
-I entered =1 in a cell, it was highlighted as a formula; as expected
-I pressed Ctrl-F8, the highlighting disappeared; as expected
-I checked tools-options-calc-view-value highlighting: it was unchecked; now _this_ I find confusing. Value highlighting is unchecked for this document only, the global setting is not changed, but the options dialog seems to tell me that the global setting _has_ changed!
(-I opened another calc document and checked tools-options-calc-view-value highlighting: it was checked, as it should be)

So there is no malfunctioning, there is confusion about a global setting when the local setting differs.
I would like to set the status back to NEW, but first I'm interested in your opinion.
Comment 8 Buovjaga 2014-11-17 08:31:52 UTC
(In reply to Winfried Donkers from comment #7)
> I would like to set the status back to NEW, but first I'm interested in your
> opinion.

There is this enhancement request for clarifying document-specific vs. global options: bug 43786. Maybe this discussion can be continued there as the objective is basically the same.
Comment 9 Winfried Donkers 2014-11-17 08:41:50 UTC
Yes, bug 43786 covers the general problem, whereas this bug only covers one specific item.

*** This bug has been marked as a duplicate of bug 43786 ***