<< GooCanvas uses the Cairo graphics library to render canvas items. For performance reasons Cairo uses 32-bit fixed point integers internally when rendering graphics, with 24 bits used for the integer part of values and 8 bits used for the fractional part. This means that values are limited to roughly +/- 8,388,608. >>
Since there is also a decimal part on 8 bits, which encompasses the range from 00 to 99 (but not to 999), Goocanvas can work with coordinates ranging from -8,388,608.00 to +8,388,607.99 . Assuming that a desired time-line precision would be 1/100 sec, Goocanvas should be able to accommodate a time-line of 16,777,216 seconds, which is ... 4660 hours (and a handful of additional minutes, around 20)!!
And even if one wanted to go for a 1/1000 sec precision, Goocanvas would accommodate a time-line of 466 hours.
The 2-hour video projects that we are speaking about should fit in, couldn't they?
Follow-up on #11 -- Goocanvas issue? ======= ======= ======= ==
=======
http:// developer. gnome.org/ goocanvas/ unstable/ goocanvas- coordinates. html -- Coordinate Limits
<< GooCanvas uses the Cairo graphics library to render canvas items. For performance reasons Cairo uses 32-bit fixed point integers internally when rendering graphics, with 24 bits used for the integer part of values and 8 bits used for the fractional part. This means that values are limited to roughly +/- 8,388,608. >>
Since there is also a decimal part on 8 bits, which encompasses the range from 00 to 99 (but not to 999), Goocanvas can work with coordinates ranging from -8,388,608.00 to +8,388,607.99 . Assuming that a desired time-line precision would be 1/100 sec, Goocanvas should be able to accommodate a time-line of 16,777,216 seconds, which is ... 4660 hours (and a handful of additional minutes, around 20)!!
And even if one wanted to go for a 1/1000 sec precision, Goocanvas would accommodate a time-line of 466 hours.
The 2-hour video projects that we are speaking about should fit in, couldn't they?