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
Is there any reason why ofPath::hasChanged and ofPath::flagShapeChanged are private? ofPath::flagShapeChanged() could be really useful when paths are changed externally (I'm currently working around it by calling ofPath::getCommands() only so that ofPath::flagShapeChanged is called), and ofPath::hasChanged doesn't get called at all anywhere in OF... so it makes 0 sense that it is private. If it were public it would mirror the behavior of ofMesh::hasChanged, which would make the library more consistent.
c.
The text was updated successfully, but these errors were encountered:
Is there any reason why
ofPath::hasChanged
andofPath::flagShapeChanged
are private?ofPath::flagShapeChanged()
could be really useful when paths are changed externally (I'm currently working around it by callingofPath::getCommands()
only so thatofPath::flagShapeChanged
is called), andofPath::hasChanged
doesn't get called at all anywhere in OF... so it makes 0 sense that it is private. If it were public it would mirror the behavior ofofMesh::hasChanged
, which would make the library more consistent.c.
The text was updated successfully, but these errors were encountered: