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 732037 - display month name on 1st in month view
display month name on 1st in month view
Status: RESOLVED FIXED
Product: california
Classification: Other
Component: ux
master
Other Linux
: Normal normal
: 0.2.0
Assigned To: California Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-22 13:32 UTC by Adam Dingle
Modified: 2014-07-23 22:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Workaround signal misfires that led to crash (1.35 KB, patch)
2014-06-23 01:23 UTC, Michael Catanzaro 		none Details | Review

Description Adam Dingle 2014-06-22 13:32:59 UTC 
California's month view displays days from 2 or more months.  It's possible to get briefly confused about which month is which.  To clarify the display, I think that California should display a month name before the number "1" on the first day of each month in month view.  For example, the squares at the top of the month view for June would look like this:


Jun 1           2           3                 4

And further down we'd see

29                30         Jul 1           2        ...
Comment 1 Michael Catanzaro 2014-06-23 01:23:06 UTC 
Created attachment 278964 [details] [review]
Workaround signal misfires that led to crash

Even though the original ChessGame is always destroyed immediately after
the creation of a new one (no other reference to it exists), the signals
we connected to the original game may be nonetheless fired by the NEW
game object. This must be a bug in Vala signals.
Comment 2 Yosef Or Boczko 2014-06-23 01:28:41 UTC 
(In reply to comment #1)
> Created an attachment (id=278964) [details] [review]
> Workaround signal misfires that led to crash
> 
> Even though the original ChessGame is always destroyed immediately after
> the creation of a new one (no other reference to it exists), the signals
> we connected to the original game may be nonetheless fired by the NEW
> game object. This must be a bug in Vala signals.

Look like a wrong product.
Comment 3 Michael Catanzaro 2014-06-23 01:33:19 UTC 
Comment on attachment 278964 [details] [review]
Workaround signal misfires that led to crash

wrong bug, sorry
Comment 4 Jim Nelson 2014-07-23 22:23:57 UTC 
Pushed to master, commit 554841
Comment 5 Adam Dingle 2014-07-23 22:44:39 UTC 
Great to see this - thanks!