TimeSpanEditBox issues

Hi Ralph,

Thanks for writing... let me reply to your comments.

1) We were able to add some logic to help with this scenario so that custom time span formats should be parsed better.  Previously the TimeSpan.TryParse was used and that didn't work well with custom formats.  Our updates for this will be in the next build 662.

2) Sorry but I'm not seeing this happen in our samples.  The popup isn't closing when we click the +/- buttons.  Can you tell us how to reproduce it in our samples or provide some really simple XAML in a new project that shows it?

3) If I understand correctly, you'd like to only have certain parts editable on the popup.  Would it only be on the lower end (ms, s, etc.) or could it happen on the upper end too (days)?  How would you like the API for this kind of thing to work, purely base it on the format used?

1) Fantastic! Thank you.

2) Add the TimeSpanEditBox to a Ribbon.  It works separately.

3) The TimeSpanEditBox always knows which parts are in use.  I think the popup should read the currently used parts automatically, this way the edit box content and the popup header will be in sync.

Hi Ralph,

2) Thanks, I see it happen now and we were able to get a fix in for the next maintenance release (build 662).

3) We also have updated the picker to only show parts that are editable via the custom format.

Fantastic!

The best customer support ever!

Hello I am at version 17.2.661.0 and my Timespan no longer works. I also use custom format because we wanted a specific look:

Like: 

0d 1h 0m 0s with those spaces and those letters inserted in order to clarify for the user what unit he was changing. Then of course the spinner to the right.

To achieve that I used the following custom format:

private const string CustomDaysHoursMinutesSeconds = @" d'd ' h'h 'm'm 's's'";

But it stopped working with the upgrade to 17.2

So my questions are:

1) Is there a way to recover this functionality in 17.2.661?

2) If not will that custom string really work in 17.2.662?

Hello,

In the code above, it looks like you have a couple extra spaces that can cause issues.  It should probably be:  @"d'd 'h'h 'm'm 's's'".  But I did test that format with 2017.2 build 662 here and it seemed to work.  It won't work in 2017.1 since we made updates for build 662 to better handle custom formats in this control.

If you write our support address, we can send you a preview build to try.  We hope to launch the official build 662 sometime this month.