After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699647 - bold style does not update correctly in conditional formatting
bold style does not update correctly in conditional formatting
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-05-03 22:55 UTC by Adam Dingle
Modified: 2013-05-05 23:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Sample file (1.86 KB, application/x-gnumeric)
2013-05-05 21:08 UTC, Morten Welinder
Details

Description Adam Dingle 2013-05-03 22:55:00 UTC
To see the problem:

1. Start Gnumeric.
2. Enter the values 1, 2, 3, 4, 5 in cells A1-E1.
3. Select A1:E1, with A1 being the primary selected cell.
4. Choose Format->Cells->Conditional Formatting.
5. In the dialog, select the condition "Expression x evaluates to TRUE" with x: "$A$1 > 0".
6. Under Applicable Style Components, select Font and deselect Background.
7. Press Edit Style.  In the Format Cells dialog, choose Style: Bold and press OK.
8. Press the Add button to add the conditional formatting to the selected cells.
9. Close the dialog.  All cells will now appear bold.
10. In cell A1, type 0 and press Enter.  All cells should be unbolded, but only some will be.
11. In cell A1, type 1 and press Enter.  All cells should now be bold, but only some will be.
Comment 1 Morten Welinder 2013-05-05 21:08:00 UTC
Created attachment 243358 [details]
Sample file

Confirmed.  This sample file is ready for anyone to enter a new value in A1.
1 should caused A1:E1 to become bold; 0 should cause regular style.
Comment 2 Morten Welinder 2013-05-05 23:46:59 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.


All this is actually fairly new code, so I am not that surprised there are
a few kinks to work out.