Visitar URL original
Drag & drop models / templates from asset to scene should add them to scene root · Issue #257 · playcanvas/editor · GitHub
Skip to content

Drag & drop models / templates from asset to scene should add them to scene root #257

Description

@mvaligursky

When model / template is dragged into 3d scene, it should be added as a child of the scene's root.
Currently it's added as a child of selected entity. This makes it inconvenient to populate world with entities, as when one is added, it's selected, and next one is added as it's child.

Activity

  1. Maksims commented on Dec 17, 2020

    @Maksims
    Collaborator

    It is very convenient to select for which child it should be first.
    Perhaps consider some behaviour, either storing temporarily a flag that entity were created and no action was done, so that next entity creation will not be child but alongside.

    Or simply do not select entity when it is placed into scene. Force selecting is not always desirable. And this is case as you described. Just do not auto-select dragged entity.

  2. mvaligursky commented on Dec 17, 2020

    @mvaligursky
    ContributorAuthor

    That sounds like a good solution (to not select dragged entity)

  3. added theissue type on Feb 12, 2026
  4. adjetey0 commented on Oct 18, 2026

    @adjetey0

    Hi, I would love to work on this issue if it is still available!

  5. adjetey0 commented on Oct 21, 2026

    @adjetey0

    10. Hi, I would love to work on this issue if it is still available!

    Hi! The automated check is failing because it requires a release label. I don't have the permissions to add one—could a maintainer please add the release: next patch label for me? Thank you!

  6. Maksims commented on Oct 21, 2026

    @Maksims
    Collaborator

    Changing existing UX behaviors to something else - should be avoided by all means, with exceptions if current UX is 99% worse than proposed.

    In this case, users already know and expect current behavior to apply: dropped template to viewport is created under selected entity's parent. Changing that behavior will lead to many users loose their muscle memory. I personally find it really rare when something needs to be created under parent - it is always under some specific entity, which is easy to pre-select as user action for indicating where entity needs to be created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions