Share

Hourglass

Tracker: Bugs

5 Timespan Boundary Error 1 when using Start/Stop - ID: 1603494
Last Update: Comment added ( sf-robot )

Condition:
Have two timespans already entered in Today's Activity such as:
Lower TS = 3:19-3:21
Upper TS = 3:22-3:24

Input:
Use Start/Stop button to enter the following time after the above times are
entered:
TS = 3:21-3:22

Expected Output:
Record time in Today’s Activity. No Errors

Actual Output:
Recorded time but threw error on console. Brought app down and then back
up and data was lost. Not recorded

Error Message on console:

Exception in thread "AWT-EventQueue-0"
net.sourceforge.hourglass.framework.TimeS
panOverlapException: TimeSpan(Wed Nov 01 15:37:46 EST 2006, Wed Nov 01
15:38:02
EST 2006)overlaps another TimeSpan.
at
net.sourceforge.hourglass.framework.local.LocalProject.checkForLeftOv
erlap(LocalProject.java:125)
at
net.sourceforge.hourglass.framework.local.LocalProject.checkForOverla
p(LocalProject.java:99)
at
net.sourceforge.hourglass.framework.local.LocalProject.addTimeSpan(Lo
calProject.java:77)
at
net.sourceforge.hourglass.framework.local.LocalProjectGroup.addTimeSp
an(LocalProjectGroup.java:129)
at
net.sourceforge.hourglass.swingui.ClientState.stopCurrentTimeSpan(Cli
entState.java:262)
at
net.sourceforge.hourglass.swingui.ClientState.stopCurrentTimeSpan(Cli
entState.java:250)
at
net.sourceforge.hourglass.swingui.ClientState.toggleTimer(ClientState
.java:300)
at
net.sourceforge.hourglass.swingui.SummaryFrame$3.actionPerformed(Summ
aryFrame.java:317)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown
Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown
Sour
ce)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown
Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown
Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)


Nobody/Anonymous ( nobody ) - 2006-11-27 04:00

5

Closed

Works For Me

Eric L.

Other

None

Public


Comments ( 2 )

Date: 2009-03-18 18:45
Sender: sf-robotSourceForge.net Site Admin

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).


Date: 2008-12-29 16:03
Sender: ewlProject Admin

I can't reproduce your bug report with version 0.7.0: Hourglass complains
about overlapping timespans and rightly so because Hourglass uses
internally time entries down to the millisecond, i.e. 3:22 entered by hand
is actually 3:22:00.000 whereas 3:22 entered by stopping the clock is more
probably something like 3:22:04.371, which is greater than the first value,
hence overlaps...

The bug will close without further intervention automatically in a few
weeks.

Eric


Attached File

No Files Currently Attached

Changes ( 7 )

Field Old Value Date By
status_id Pending 2009-03-18 18:45 sf-robot
allow_comments 1 2009-03-18 18:45 sf-robot
close_date 2008-12-29 16:03 2009-03-18 18:45 sf-robot
status_id Open 2008-12-29 16:03 ewl
close_date - 2008-12-29 16:03 ewl
resolution_id None 2008-12-29 16:03 ewl
assigned_to nobody 2008-12-29 16:03 ewl