Hi, Sorry to hear you are having problems with snapping. When you are moving an event to snap to another, it is not the cursor position that determines where to snap to - it is the long dotted line that appears when you move the event. If we used the cursor for this, then if you don't click on the exact spot of the event when moving the cursor will jump immediately, which would be confusing. So, when you start to move an event, are you seeing the long dotted line, with a message saying Shift Event by... ? Then if you try to align this line up with the start or end date of the event the line should change to be shortened and the message to "Snap to start/end of..." This shortened line might sometimes disappear if it is trying to snap to an event that is outside the current view, but the message should still remain. However if you were trying to snap an event using the cursor position, it would potentially look like it wasn't working, since the cursor will often be at an offset to this line. Let us know if you still have problems with it. Jess
Jess, thank you for your reply. Confusion over the dotted line versus the cursor position was not the problem. If I take Event B and drag it slowly so that the long dotted line passes over either the beginning or end of Event A, the line never switches to a short dotted line, and the "Snap to" message never appeared. Rather, the behavior is as if there is no Event A in the timeline. Here's a quirk that might help you troubleshoot it: I found that if I embedded both Events A and B in a new parent event, THEN the snapping worked between the two as expected. If I then undo the "embed in new parent" command, then the snapping again doesn't work at all. This next thought is pure conjecture, but it seems like this problem occurred more and more frequently (to the point of becoming the default behavior of the whole timeline) the more complex my timeline became. If I create a new empty timeline, and create just two events, the snapping works as expected. It's in my 70-or-more-event timeline that this issue is happening. Thanks again. Jon
I have set up Aeon Timeline on Mac OS X (10.11) as well, and loaded the same timeline file from a cloud drive. Unfortunately, the snapping issue here is the same as described above. I thought it might be a Windows-specific issue, but this indicates it is a cross-platform issue. The Scrivener integration remains a major selling point for Aeon Timeline, but this glitch is a big bummer. I might try grouping events into parent events, or breaking down the timeline into several smaller timeline files, to see if either of those things help restore the snapping behavior. If I get around to that, I'll let you know. Thanks, Jon
Hi, Are you able to send through the timeline that is causing problems for you to email@example.com with a description of the events you try to snap that aren't working? That would be helpful for us to recreate the problem. We keep all timelines confidential. Have you tried the Murder on the Orient Express example timeline? (you can open this on the welcome screen by clicking the Examples tab). This timeline also has >70 events, so I was wondering if you still see the problem with this timeline. Jess
I have emailed you my timeline with several screenshots. The Example timeline snaps much more like expected, but I've several times tested and reproduced my issue on multiple platforms.
I'm not sure what the intended behavior is, but with the Example (Murder) timeline, with several close events such as #61-68, with the zoom showing four days, the snapping seems hard to control, where a horizontal movement of the mouse (when dragging an event) even just a few pixels can cause the snap suggestion to cycle through several events. The vertical position of the cursor seems to have no influence as to what events should be snap-suggested. I wonder, when dragging an event, if the vertical position of the cursor should be taken into account for snap suggestions, so that in an event-dense area, the user has more control what they're snapping to?
Hi, Thanks for sending through your timeline, we will use it to look into the problem. Jess