Hi Sandra

Have you opened a new ticket, or is it the same number you gave me earlier?

Regards
Florian

Hallo Sandra Well, with this simple example it works fine, but in real-use we normally have an array of DateTime, often spread over several days... so just multiplying them is not that easy. But how about you would change your conversion in the Utils class ( double DateTime(DateTime value) and DateT...

Good Morning Sandra

Thanks for this news. Let's hope it will make it in the next maintenance releases!

What about the labels? Are they included in the same whish-list item, or is it going to be another one?

Regards
Florian

Hi Sandra

How are you coming along with the solution to my problems? Any preview on what to expect and when?

Thanks
Florian

Hi Sandra Yes, we could do something like that, but we probably would end up implementing the whole "positioning" (whether to show or not etc.) logic all over... On your part, it probably is "just" substituting the DateTime.ToOADate() method with a custom one... (I now, there is no such thing as jus...

Did you mean this thread?

Hello Sandra

I'm sorry, but this isn't a viable way for us. True, the labels show the microseconds, but we would have to do the "positioning" of the labels ourselves. Otherwise, we get something like this.

Regards
Florian

Hello Sandra

Do you have any new information about my requests?

Regards
Florian

Hello Sandra I don't think that it has anything to do with that, beaus the "ffffff" custom format specifier in itself works just fine. var formattedDateTime = string.Format("{0:dd.MM.yyyy HH:mm:ss.ffffff}", new DateTime(799998999912354811L)); With this you get a result something like 05.02.2536 18:2...

Hello Sandra It's not completely true. The .Net DateTime type has a precision of 100 ns, which is just about enough for my purposes. As far as I can tell, the problem lies within the OADate and mainly the default conversion from DateTime to OADate and vice versa. Unfortunately, none of this informat...

Hello Sandra I looked at this thread. Unfortunately, I don't see much resemblance. I did as in demo All Features\Welcome !\Axes\Labels\Showing milliseconds instructed (I even used it as base for my sample-application). I believe the problem for not displaying the microseconds at the bottom axis to b...

Hi We have some customers who have some data with a resolution of one microsecond, and we d'like to create diagrams for them. But there, the problems started: When we use the Series.Add(DateTime, double) method, the microseconds are rounded to the next millisecond. There would be the workaround to m...