What steps will reproduce the problem? 1. Insert an item in the timeline that has its displayTime and/or notification.deliveryTime attributes set for some time in the future.

What is the expected output? What do you see instead? Expected would be one of the following: 1. Delivery is delayed until the time specified and notification happens at the same time OR 2. Insert is rejected

Actual is that delivery is done immediately, with notification being done at the time specified in the notification field, which can be confusing.

Furthermore, the timestamp on the card displays the, correct but confusing, "in X timeunits" (where "timeunits" is the correct time unit - minutes, days, etc). The card also sits at the beginning of the timeline, which could serve as a block against other cards and create a poor user interface experience.

What version of the product are you using? On what operating system? XE6

Please provide any additional information below. I'm trying to figure out any practical (or even fun) use of this feature as it is currently implemented, and I can't think of one. I can see some reasons to stick cards further in the past, but not ones that show up on the timeline for future events before the event happens.

Unless the lottery can send me tomorrow's numbers today. Then I'd love this feature.

I have to plus one this- I need to be able to exactly defer my cards for an almost exact amount of time. It seems that the field is ignored.

Thanks for the feedback. One thing that helps us prioritize is use cases.

What are you trying to implement which require this feature?

Comment deleted

I am creating a pomodoro timer, and its much more optimal if the glass can decide when to display- vs a cron job or worker process on my end. especially if the user ends up offline, etc.

delivery time is of more interest than displayTime, I actually found it a little confusing you could set the displayTime and the card could get lost in the timeline. the user has no real indication that occurred- unless you pushed two cards. i can see why it could be useful in some cases. but, its weird to me for the most part.

Comment deleted

Comment deleted

I also need this feature. Here is my use case: 1. User receives a card with "Ryan's lovely cat" as the title, and picture of the cat. (Let's call it Cat Card) 2. User taps on the card and selects "Get Map" menu item, which would show where the picture is taken 3. User receives a new card with a map (Map Card) shows the location of the picture taken.

Right now the Map Card would go before the Cat Card in the timeline, and setting the displayTime of either one doesn't take effect at all.