AlembicObjectPath (see DNA_cachefile_types.h) has a fixed-size char[] buffer.
I think that's a good idea, and that's what this task is for.
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Confirmed | DESIGN | Sybren A. Stüvel (sybren) | T69058 Alembic integration improvements | ||
| Confirmed | TO DO | None | T51321 AlembicObjectPath has a fixed-size char[] |
Event Timeline
Comment Actions
Doesn't belong in the bug tracker I think, so changed type. Not sure paths longer than 4096 are supported by any commonly used OS even.
Comment Actions
it's an internal path inside an alembic file, we should not impose any OS related restrictions to that in the first place?
Comment Actions
I agree such hardcoded limits are not helpful, just saying that this might not actually affect anyone in practice. Mainly it's a waste of memory usage.
Comment Actions
The "object path" is not a filesystem path, so it isn't affected by OS related restrictions. This is something we should address at some point, even though in practice I have yet to see Alembic files with such long "object paths" in them.