When creating a directory, CfCreatePlaceholders: the directory is also marked as MARK_IN_SYNC and DISABLE_ON_DEMAND_POPULATION. If it exists locally, it is converted through CfConvertToPlaceholder, and the tag is set with CF_CONVERT_FLAG_MARK_IN_SYNC.
- In a folder with relatively few sub-files, the folder can automatically display the aggregated status based on the files inside. If there are spinning circles inside, the folder will display spinning circles; if there are clouds, it will display clouds; if all are checked, it will display a checkmark. However, when there are many files inside, I tested with 1000 files for verification, and there was a problem with the folder aggregation. It seems that it can only aggregate the status of the first part of the files, but not the later part, which is somewhat like exceeding the cache.
- I would like to know how to handle the status of folders, especially in the case of large folders. It's impossible for us to control it explicitly. Wouldn't that be very cumbersome? We would have to change the status every time a file is moved, and once we set not_in_sync, we would have to explicitly control all subsequent statuses. This shouldn't be the way to handle it. I would like to inquire about how to handle the status of such folders?