On: 4/15/2009 4:07:37 PM
User Wrote:
We would like to use ActiveGantt to display some parallel processes in our real-time system. The display will happen after the timing data has been collected, not during the collection. We need to have the flexibility of defining the time axis, not in seconds/minutes/hours/days, but rather in microseconds/milliseconds/seconds with seconds being displayed over the entire timeline. For example, first process starts at 0.1 ms - 0.55ms .... last process is at 133.903 seconds - 133.994 seconds. Is it possible to extend the axis display to go below the second mark as it is currently?
On: 4/15/2009 7:25:36 PM
SCS Admin Answered:
We use date and time types straight out of the IDE. Checking out the Date and DateTime types of Visual Basic.Net the lowest order of magnitude is milliseconds. It does not handle microseconds, a class would have to be implemented to handle this and replace the standard date/time classes. It is not trivial however because a great deal of the functionality depends on dates.
On: 4/17/2009 5:41:30 AM
How about having a TimeSpan axis instead of a DateTime axis? Is there any way that you can think of that we can display a numeric as the axis. Even if it is seconds, as long as it shows total seconds, not seconds up to a minute and then start from 0 seconds again. Then, I would just fake out the axis so that 1 second corresponds to a microsecond. As long as I can get an axis to go from 0 seconds to 15,000,000 seconds, I can still active the same thing that I am after. It doesn't have to be a microsecond axis in that case. It would be a generic numeric axis from 0 -> N. Where N can be anything and not grouped in 60 seconds, 60 minutes, 24 hours, 30 days, 12 months. Instead, it will be 0 -> N.
On: 4/17/2009 5:43:18 AM
You've just given us a very good idea, because the reason that this has been delayed so much is that we have always had the notion of creating a new date/time class of this type: Class oDateTime Private Year As Integer Private Month As Integer Private Day As Integer Private Hour As Integer Private Minute As Integer Private Second As Integer Private Milisecond As Integer Private Nanosecond As Integer 'And so forth to a very small order of magnitude End Class But the problem with this approach would be that all the arithmetic date/time operations would have to be re-written, you know adding and subtracting dates formatting dates and so forth and the class would probably wind up being to big. But a class like the following could be easier to implement Class oDateTime Private oDateTime As DateTime 'Gets rounded to the second Private oSecondPart As Double 'Which handles every order of magnitude below one second End Class As you know Doubles aren't very exact and tend to miss out on certain significant digits, and the other difficulty we experience here is that any change we do on one control we have to do on all six of them (ActiveGanttVC, ActiveGanttVB, ActiveGanttVBN, etc.) plus the new six controls we will be publishing soon (Ajax, WPF and Silverlight). We will have an answer shortly.
Class oDateTime Private Year As Integer Private Month As Integer Private Day As Integer Private Hour As Integer Private Minute As Integer Private Second As Integer Private Milisecond As Integer Private Nanosecond As Integer 'And so forth to a very small order of magnitude End Class
Class oDateTime Private oDateTime As DateTime 'Gets rounded to the second Private oSecondPart As Double 'Which handles every order of magnitude below one second End Class
Home Contact us Site Map Online Store Products Downloads Documentation
Support About us
Terms And Conditions Privacy Policy Licensing Copyright
