[Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds

2007-12-03 Thread Stig Bjørlykke
Hi. We currently have a problem drawing advanced time graphs when the time value is greater than ~429 seconds. This is because we handle seconds and microseconds in one guint32, which will wrap at this point. Do all platforms support guint64 or should we stay with this limit? Or maybe

Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds

2007-12-03 Thread Jeff Morriss
Stig Bjørlykke wrote: Hi. We currently have a problem drawing advanced time graphs when the time value is greater than ~429 seconds. This is because we handle seconds and microseconds in one guint32, which will wrap at this point. Do all platforms support guint64 or should we stay

Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds

2007-12-03 Thread Stig Bjørlykke
On 3. des.. 2007, at 21.16, Jeff Morriss wrote: Wireshark has required the support of guint64 for a while now-- that's a safe way to go. And then the next question: What to do with this GUINT_TO_POINTER when yscale_max changes to guint64? OBJECT_SET_DATA(menu_item, yscale_max,

Re: [Wireshark-dev] Problems in IO Graphs with time values greater than ~429 seconds

2007-12-03 Thread Guy Harris
Stig Bjørlykke wrote: And then the next question: What to do with this GUINT_TO_POINTER when yscale_max changes to guint64? OBJECT_SET_DATA(menu_item, yscale_max, GUINT_TO_POINTER(yscale_max[i])); OBJECT_SET_DATA(menu_item, yscale_max, (void *)yscale_max[i])); and the