Hi,

I am not able to reproduce this with the latest release. Can you send me or attach here a save file (created with Calendar.SaveTo or Schedule.SaveTo) with the schedule that is causing this problem to occur? Also, what version of the component are you using?

Regards,
Meppy

Ok, so I downloaded the latest trial version from your website and tested on this version. I still get the same result. Appointments are split into several lines, as though the are colliding. Attached is an image of what I get. The BottomTimeline is now set to show in minutes with 20 minute intervals (setting to hours just creates even more lines).

Each appointment represents a worker clock, i.e. he clocked with a coin on delivering fruit that was picked. Depending on what type of work, clocks are closer or farther apart, but should never collide. On processing the information, the user wants to view all clocks on ONE line only, and not as it is currently displaying.

On the right hand of the image, you will see a list of all clocks ordered from start to finished. I have highlighted the clocks that form a cluster between 9:00 and 10:00 of the specific employee.

Thanks for any advice.

Ok thanks. You're right about the appointments being instants in time. Workers get paid for each clocking they make, but employers are concerned that they over clock, so we need the exact time of clocking to determine valid clock counts.

I was not aware of the ResourceLengthMethod. I set it to Exact and duplicates are gone. Your suggestion is good. I was wondering if it would be possible to have the same type of property as in TimeTable, so maybe this is your opportunity to do it.

I'll have to show the display rendered by the Exact method with the client to see if that will work for them (which I think will be the case).

Thanks for the help and advice on this.