Here are the classes, structs, unions and interfaces with brief descriptions:

[detail level 123]

▼Ncello
CIpcClient
CIpcClientProperties	Properties struct to monitor an IPC client. Created automatically when creating an IpcClient object, and will be named after the cello Object that's connected to the IpcClient, with the string "IpcClient" appended
CIpcServer
CIpcServerProperties
CObject
CPath	Class to navigate between subtrees that are all connected together
CQuery
CScopedForceUpdater	RAII class to restrict the 'forceUpdate` value to one scope
CSync	Permits thread-safe Object updates by using the juce::ValueTreeSynchroniser class to generate small binary patches that are used to pass updates from one copy of a ValueTree to another, each in separate threads. This sync is only performed in one direction, so you will need a pair of these objects to perform bidirectional syncs
CTest_cello_path
CUpdateQueue
CUpdateSource
▼CValue	A class to abstract away the issues around storing and retrieving a value from a ValueTree. Designed to make working with VT values more like working with regular class/struct members
CCached	A utility class to maintain the last known value of a cello::Value object – each call that fetches from a Value does two things that may be more costly than we like in some cases:
CValueBase
▼Njuce
CVariantConverter< cello::IpcServerStatus >
CVariantConverter< std::complex< float > >	A variant converter template specialization for std::complex<float> <--> & juce::var. VariantConverter structs need to be in the juce namespace for them to work properly
CTest_cello_ipc
CTest_cello_query
CTest_cello_sync
CTest_cello_value