You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue collects the rough edges I've run against while adapting the synthesizer.
There's some confusion with coordinate types, the old code uses f32 as that's most natural for Windows, yet kurbo tends to use f64. Some of this can be made smoother by adding more into conversions in kurbo taking f32 as well. I'm a little uncertain what we should use as the default. One possibility is the Coord associated type from piet. Basically, there's no compute-time cost for using f64, but it does potentially use more memory if not needed.
This adds a RoundFrom conversion from f32 to f64, which is especially
convenient when adapting existing code to use Cairo.
This is part of linebender/druid#14
This issue collects the rough edges I've run against while adapting the synthesizer.
There's some confusion with coordinate types, the old code uses
f32
as that's most natural for Windows, yet kurbo tends to usef64
. Some of this can be made smoother by adding moreinto
conversions in kurbo takingf32
as well. I'm a little uncertain what we should use as the default. One possibility is theCoord
associated type from piet. Basically, there's no compute-time cost for usingf64
, but it does potentially use more memory if not needed.We should probably merge piet-common: Add type aliases for the associated types piet#37.
I am also more inclined to do Deferred errors? piet#34. All the error possibilities are annoying, and not very useful.
I missed having a circle shape. This belongs in kurbo, but I'm faking it by using the "circle" from piet-test's picture_1.
The text was updated successfully, but these errors were encountered: