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 153347 - Click repeat rate in calendar view too fast
Click repeat rate in calendar view too fast
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: clock
git master
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-09-22 00:07 UTC by David Stanaway
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Stanaway 2004-09-22 00:07:43 UTC 
Click on one of the arrows in the calendar view to move to prev or nexr moth or
year, and keep it depressed for a second, and wait while about 100 clicks are
processed.
Comment 1 Vincent Noel 2004-09-22 15:25:51 UTC 
And what happens when you do that ?
Comment 2 Vincent Noel 2004-09-24 14:23:04 UTC 
Damn ! You're right.
What actually happens is that if you keep the mouse button down for a second on
"next month" for example, the calendar will keep changing months for a long time
even if you release the mouse button (I just kept the mouse button down for a
second or two and my calendar forwarded to february 2029).
This is not good. I'm surprised no one found this earlier.
Comment 3 Vincent Noel 2004-09-24 15:05:21 UTC 
The calendar in the clock applet is actually a regular gtk-calendar widget,
which is not affected by this problem. I'm guessing the overhead introduced
checking appointments/tasks/etc with e-d-s creates the delay.
Comment 4 Vincent Untz 2004-12-18 17:35:17 UTC 
It seems to be fixed here. Does it still happen for you?
Comment 5 Mark McLoughlin 2004-12-20 14:36:14 UTC 
See also Fedora Core bug:

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140852
Comment 6 Vincent Noel 2004-12-21 15:09:12 UTC 
Yes, this is fixed for me too (using gnome-panel 2.9.4).
I'm closing the bug, anyone please feel free to reopen if you think that's not
right.