Andreas Reich
Andreas Reich
Hmm actually I guess for what you want you want to specifically link the `VisibleTimeRange` property. So maybe it is "just" about it having a UUID or even better an...
> first we need a new property archetype that defines what's actually visible on screen left/right This _could_ look something like this: ```rust table TimeAxis ( "attr.rerun.scope": "blueprint", "attr.rust.derive": "Default"...
it could work with some more hacks and custom ui. But really I'd like that to be a configurable uuid of an existing view and not a made-up one. I'm...
Thanks for being so understanding and patient on this, especially given that I clearly don't quite know yet exactly how to solve this myself apart from some vague future plans...
I pondered this a lil bit more and synced with @jleibs to coordinate what solution we'd like to have medium term. Leading to the writeup of this related issue documenting...
> What do you mean by "global"? Can you maybe draw an outline where in the blueprint debug pannel these entries would live? Global was a bit of a misnomer:...
> Would this data still be saved in a blueprint? If so, how can data be loaded and stored without a fbs? yes. Those fbs files are strictly just for...
I was really hoping to get to that sooner, but other things keep cropping up, so no timeline unfortunately
we moved all the image conversion to re_renderer now since some of those are gpu driven (see #7700) we should try to make this gpu driven as well: This is...
putting this on draft for now until I resurrect it (hopefully later this week, maybe early next)