Repository navigation
Conversation
|
@shin1244 is attempting to deploy a commit to the playcanvas Team on Vercel. A member of the Team first needs to authorize it. |
|
@Maksims There is one case I would like your view on. The setup in the video is deliberately 2026-09-04.112008.webm
I think an explicit "active view" concept could help avoid this kind of ambiguity. That said, I'm not a UX expert, so I'd appreciate your perspective on whether this would be a good UX approach. |
To add to that — what I mean by an active view is one simple rule: everything happens I expect that means less code and a more intuitive result, with no special cases to |
The ternary fits within the 120 column limit, so prettier collapses it onto one line. Caught by the formatter step in CI. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
It is a complex UX indeed. In this case, it would be better if it would paste in the right panel, indeed. So for indirect pasting - active panel - is a needed concept. But here is a case where applying "active panel" to "auto-navigation", would be pretty annoying:
If we auto-navigate based on active panel, then case with multiple materials selected and texture folder navigations, will lead to ping-pong auto-navigations, and will require an extra deliberate focus of the left or right view by user to ensure "sticky" auto-navigation. Which is undesirable. So for auto-navigation - we want sticky one (on the main/left view), while for other actions (without direct interaction) - based on active, highlighted view. |
|
Understood, changed it that way. Auto-navigation is pinned back to the main view, while pasting and asset creation |
|
@kpal81xd Hi! Whenever you have a moment, could you take a look at this PR? Our team is currently running this build internally via Docker, so I merge and redeploy every time the editor is updated. Having it in main would make things much easier for us. Thanks! |
|
Hi @shin1244, thanks for all the work on this, and for going back and forth with @Maksims on the UX. The split between sticky auto-navigation and actions that follow the active view was carefully thought through, and the multi-window paste case you raised was really useful. Unfortunately we won't be merging this. The Editor is being redesigned, and the redesign includes a new, more flexible tab and panel layout. Split views like this one will be handled at that level instead of inside individual panels like Assets. Merging this now would give us a second layout system that we'd have to maintain and then migrate or remove soon after, so it's outside what we can take on at the moment. I know your team already runs this build, so I'm sorry this means more maintenance on your fork for now. Your work and the discussion here will feed into the redesign, especially:
I'll close this PR, but please keep #2232 open so the use case stays tracked. If you think the new layout misses any part of your workflow once it lands, please comment there. Thanks again for the contribution! 🙏 |
Fixes #2232
What's Changed
Checks