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
In my head, I plan this to be part of the later (hopefully Christmas) update, switching from the initia bvv-playground integration iteration to the new BVBrowser (with additional extra features).
The reason is that (in my opinion) it is hard to come up with a universal clipping interface while working with a general case of multiple sources with multiple scales, arbitrary transforms, etc.
I need to think about it a bit, how to wrap things around in a reasonable and flexible UI.
Actually, using/experiencing Mobie (and what you did with it) gave me a lot of new ideas and a wider overview.
Sorry to disagree, but I am not sure that simple keyboard shortcuts would be a suitable (or ideal) implementation.
These last couple of weeks I've been thinking about it.
I have some ideas that should be reasonably quickly implemented in the ugly BVBrowser prototype v1.
And then we can iterate together to make something useful out of it.
I am already very pleased with this collaboration, for me, so many new thoughts on bvv improvement from the navigation to the rendering.
So that late night Milano's birreria visit pays off already :)
If we can make that BVBrowser as a convenient standalone and part of Mobie, I want to re-write BigTrace based on it.
Then using Mobie I can browse this recent preprint data (for example), render illustration movies and then launch BigTrace to trace microtubules straight from the cloud, all in one go.
This all sounds super amazing and exciting! Just for this I2K 2024 was totally worth it!
Regarding the clipping planes: I suggested keyboard shortcuts because I thought it would be the easiest. If you have other ideas that's of course, probably, even more exciting.
Hi,
Do you have clipping planes in BVV, ideally with some keyboard shortcuts to move the plane along the X/Y/Z axis?
The text was updated successfully, but these errors were encountered: