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
Especially for Brush&Link operations, it is desired to change the color or size of many objetcs such as points at once (like desaturating them or making them translucent).
Currently classes like PointDetails have the coloring and scaling information stored as primitive types, so that each point instance has its own memory for these attributes.
It may be desired to have a single coloring information object for all PointDetails objects in a Points object or across Points objects, in order to save memory and in order to be able to change color of all points with a single operation without the need to loop through the PointDetails objects.
By using a reference to some kind of ColorInformation object within a Details object, sharing can be made possible.
The API can also be simplified by only requiring positional data in the add methods, which can return the PointDetails object so that further appearance attributes can be set (like ColorInformation). This will break chainable add calls, but should be worth it since adding these graphical primitives is seldomly done this way.
Of course this also applies to SegmentDetails and TriangleDetails.
The text was updated successfully, but these errors were encountered:
Especially for Brush&Link operations, it is desired to change the color or size of many objetcs such as points at once (like desaturating them or making them translucent).
Currently classes like
PointDetails
have the coloring and scaling information stored as primitive types, so that each point instance has its own memory for these attributes.It may be desired to have a single coloring information object for all
PointDetails
objects in aPoints
object or acrossPoints
objects, in order to save memory and in order to be able to change color of all points with a single operation without the need to loop through thePointDetails
objects.By using a reference to some kind of ColorInformation object within a Details object, sharing can be made possible.
The API can also be simplified by only requiring positional data in the
add
methods, which can return thePointDetails
object so that further appearance attributes can be set (like ColorInformation). This will break chainableadd
calls, but should be worth it since adding these graphical primitives is seldomly done this way.Of course this also applies to
SegmentDetails
andTriangleDetails
.The text was updated successfully, but these errors were encountered: